Well, it looks like WPTavern has gotten off to a good and controversial start. Jeffro has question the implementation of the post revisions feature and it is certainly stirring up some healthy debate.
On the one hand there are people who just want a checkbox to turn the feature off, perhaps also the option to limit the number of revisions. On the other there are those who feel it is entirely reasonable to expect a WordPress user to edit the wp-config file directly in order to turn it off, or the use a little SQL to remove the old posts.
I’m in the middle. I don’t think it should ever have been applied to posts, only pages. Either that or which types it applies to should be optional. I think WordPress needs to either cater for the technically unaware, or not. And I think the publish button should delete all prior revisions of a post.
You can check out the conversation at WPTavern
(__)
`
[...] Post revisions: friend or foe? – WP FUN [...]
(__)
`
In its current implementation post revisions are definitely a foe. For starters, revisions should not be stored in the posts table. The way it works now, the only reason why this type of strict revisioning is needed is if you're running a wiki.
I agree that there should be options within WordPress to manage its use as opposed to mucking around with the config file.
(__)
`
Oh sure – take the easy way out. Plugin you want, plugin you get. http://wordpress.org/extend/plugins/delete-revi...
(__)
`
Thanks for the heads up on the mistype.
On the SQL front there are a lot of things I could do with SQL. I could write my posts entirely in SQL if I wanted to, but that would entirely defeat the purpose of WordPress wouldn't it?
(__)
`
freINDs can be friENDs in the end. I before E except after C. The Grammar Police commeth and want to know why you have spellcheck turned off.
Seriously though, there is a mySQL command you can use to delete prior versions of posts if you didn't already add the plugin as discussed on WPTavern.com