Turn Off WordPress Post Revisions
WordPress 2.6 introduced an annoying feature called "Post Revisions", which saves each revision of every post when you edit it (after publishing). Since I practice link clustering, you can imagine how many post revisions are sitting in my database right now.
Lester Chan (aka GamerZ) published the solution with "How To Turn Off Post Revision In WordPress 2.6" as well as how to remove the existing post revisions from the database.
Just like the autosave feature, WordPress administrators should have the option in the settings somewhere to enable or disable the post revisions feature, or at least be able to adjust it.
Similar Posts:
This is kind of what happens when a "geek" software starts catering to the "mass". I preferred WordPress when it remained a geek blogging tool (when it was in version 1.5.x) and was simple, light and not too cluttered.
Now it seems that in order to cater to ever increasing user demands, the feature list is full of things we geeks don't want or care about.
My latest blog post: Combating inflation – the Papa Hari Way
Exactly. This may be a good time for me to start working on custom blog software (for myself).
I completely agree. Firefox is the same way, back when it was Firebird it was a heck of a lot smaller, yet still open source and easy to create plugins/extensions for. Now it is a bloated piece of software that has so many features it is ridiculous.
My latest blog post: The Kansas City Royals – Poem
Firefox is still open source.
As for Wordpress, yeah, it's bloated now! It's catering to the computer masses that really shouldn't be computing.
I don't think that you're going far enough back. I found that when Phoenix became Firebird, the bloat piled on.
Custom blog software sounds time consuming. A man of your talents could probably find thousands of valuable things to do with your time rather than invent a better mousetrap
Of course, as a rewarding personal project this one may have you eager to get started. The whole idea of coding doesn't fill most of us with anticipation.
My latest blog post: Looks Like We Finally Made It
I don't like the coding portion, but I do like the problem-solving portion. Even if start on a project like that, I won't let it interfere with my regular routines.
I'm pretty confident that I could put a custom package together in a day since it wouldn't have to support anyone but me.
Yeah that is a cheesy feature. Doesn't it come turned off. I don't remember if I had to turn it off or not.
It comes as turned on with no apparent way to turn it off.
I have a base for a custom blog software. But it's not too powerful and it's quite incomplete at the moment.
Also if I write a blog software, it will use SQLite and not MySQL.
Writing another blog software doesn't fill me with thrills. It's boring, involves writing more SQL statements and HTML markup than actual coding.
My latest blog post: Combating inflation – the Papa Hari Way
I would probably use a single text file schema for data such as page link, title, categories, tags, etc. The data for less than 100,000 posts would load in less than a second.
I would probably also have comments saved as individual files in the same location as each page.
I could use embedded PHP function calls and I don't think it would be nearly as slow as database queries.
i haven't upgraded yet. Should I? Are there alot of improvements?
You should always upgrade (but keep a backup) because upgrades include security fixes.
Hi RT, this is actually a test comment to see if I broke your comment program. It doesn't seem that new comment info (name/website) is being accepted? If this posts, ignore it. Thanks. ~ Steve
Okay, I'm ignoring it. By the way, by looking at my name here, can you guess what keyword I'm trying to rank for?
hi RT, I hadn't noticed your name change. Is that something new? Makes me think this blog must be about the Philippines. ~ Steve
Brand new. I had to run a database query to change all the old ones and update my user profile for the new one.
I can go in and change the links as I go to point to specific posts. Meh, I'll do that AFTER I get the majority of the clustering done.
Ok, I take that back. It is working and I didn't break it. Wheww…. So ignore this one too. ~ Steve
Thanks for this solution, while I love Wordpress in general this addition seemed frivolous and because I save me posts often I fear it will cause a huge increase in my database. It seems like at least someone needs to create a plugin to fix this.
My latest blog post: Do You Know Peter Answers?
When you need plugins to *disable* features rather than extend functionality, you know something is screwed up in the software design.
My latest blog post: Combating inflation – the Papa Hari Way
I hereby nominate hari for comment of the day for his comment:
"When you need plugins to disable features rather than extend functionality, you know something is screwed up in the software design."
LOL! ~ Steve
I didn't upgrade for fear of it changing my blog beyond recognition. I have read many comments on how this new upgrade messed up other people's blog so maybe it's best I leave it as is.
Sonni
My latest blog post: Is Your Life Out of Balance?
There are alway teething problems with upgrades. I was annoyed when they started using Google instead of Technorati to show incoming links, as it was less accurate.
Is there anything worth upgrading for – I like 2.5 though some of my blogs are still on 2.3. I certainly dont want every draft in the database – that's just stupid: anything longer than 200words I write off line anyway
My latest blog post: Where to publish your best content
Personnaly, I will wait to perform the upgrade. I don't find a lot of nice features in 2.6. This post revision sounds like crap for me, it will kill my database…
My latest blog post: Toujours aussi pourri
I have not upgraded to 2.6 yet, and I don't plan on doing it for awhile. I don't need any of the new features that 2.6 has, and in fact, as this post says, some of them are actually troublesome. So I'll just stick with what I have now, which I suppose is 2.5, although I'm not sure.
oooh no thanks, I'm NOT upgrading to Wordpress 2.6 until they fix the numerous problems being discussed about problems logging in after upgrading. Nope, not gonna do it.
For example, check out this post about the problems numerous people are having after upgrading to Wordpress 2.6.
http://www.snoskred.org/2008/07/wordpress-26-warning-do-not-upgrade.html
My latest blog post: Telling It Like It Is is on Staycation
My problems were minor, across 5 blogs. 2.6.1 should fix everything I should think.
[...] 2.6 isn't very different to 2.5 (well, unless you include the database bloat that is post revisions {Side note – I wonder how long it will be before people are getting warned by their hosts about [...]
Like many others here, im going to hold off on the upgrade, some things have been sorted out but seems like its better to wait a little more.
Thanks… i was postponing upgrading until i found something like this…
My latest blog post: Link Building Tip: Great backlinks from Searchles.
yea i bet thats a pain for you… having to deal with so many :/
[...] about The Philippines, he also provides excellent advice for bloggers on Monetization, Up-to-date Wordpress Optimisation Tips, Blog Reviews, and is an ardent advocate for using 'dofollow' on comments and provides [...]
There's a plugin which disables this for you. It's a good idea to save database space and its very useful.
My latest blog post: Learning about becoming a sheriff