How To Turn Off Post Revision In WordPress 2.6 | Lester Chan’s WordPress Plugins

One of the irritating feature for me in WordPress 2.6 is the post revision. I am the only author of my blog and hence this feature is useless to me.

Just in case you are wondering how post revision works, whenever a post is edited, a new row will be created in wp_posts table. Hence if your posts or pages got edited 10 times, you will have 10 new rows in wp_posts table.

In no time your wp_posts table will be filled up and the post ID will be huge.

To turn off this feature, add this following code to wp-config.php:

define('WP_POST_REVISIONS', false);

You can also delete all post revisions by running this query in phpMyAdmin:

DELETE a,b,c
FROM wp_posts a
LEFT JOIN wp_term_relationships b ON (a.ID = b.object_id)
LEFT JOIN wp_postmeta c ON (a.ID = c.post_id)
WHERE a.post_type = 'revision'

Be sure to backup your database first before performing any queries in phpMyAdmin.

*UPDATE* Auto Saves does not create a revision of the post.

*UPDATE 2* Updated SQL query from Andrei Neculau as the previous query does not delete from wp_postmeta and wp_term_relationships tables.

150 thoughts on “How To Turn Off Post Revision In WordPress 2.6”

Pingback: ?????? Post Revision ?? WordPress 2.6 : XirBIT.Com

Pingback: Desactivar Revisiones en Wordpress 2.6 | Phylosoft

@Ryan Boren, @noname : Yea I confirm that auto save does not create a revision. My bad.

Just a heads up: I wrote a plugin which allows some control over the post revisions (Disabling in admin, Enabling on per post basis, limiting number of revisions, etc): http://dd32.id.au/wordpress-plugins/revision-control/

PS. @validation function: ‘ ‘ is a valid character in an email address

Oh.. It doesnt like the plus symbol at alll.. Lovely

@DD32: Nice! WordPress should have that in the core.

Pingback: WordPress 2.6 - jak wy??czy? system rewizji? | WPNinja

This ‘feature’ has been a terrible nuisance to me as well. Thank you very, very much for this helpful post. It’s brought a much needed smile to my hour of trying to figure out what’s going on.

Now on to clean out database tables. I’m a bit, actually quite, disappointed with the devs on this one and definitely agree such a feature should be accessible under Settings in admin.

After disabling Post Revisions, I did manage to get one post ID ‘skipped’ so far after about five test posts. Hopefully it’s not autosave causing this. There is still something that may be wrong and hopefully isn’t hastily overlooked (Ryan).

Pingback: Wordpress Revision History : Yuting Zhang’s Homepage

Don’t put it at the end of wp-config.php or it won’t work.

Can’t believe this bloody thing is a feature! Thanks for the help

This must be a sore spot at WordPress software central.

Comment from support: “First question: Why do you think that it matters how many posts/pages/revisions/whatever are in the database? Databases are fast and efficient, and text compresses easily, you know.”

http://wordpress.org/support/topic/191420?replies=1#post-812141

Pingback: Delete Wordpress 2.6 Revisions | Andrei Neculau

Pingback: Abschalten Post Revision in WordPress 2.6 - Beitrag - Heimpold.net

Thanks for fix!!! I cannot believe WP guys came up with this “feature” and did not announce how to fix it…

It appears there is another version of this fix out there.

Is it this:

define(‘WP_POST_REVISIONS’, false);

or this:

define (‘WP_POST_REVISIONS’, 0);

Pingback: bobpeers -> blog » Turn Off Post Revision In WordPress 2.6

@oldengine: Both is the same thing as false is equals to 0 as well.

thank you,
this was helpful!

Where do I put the snippet of code in the wp-config.php file??

Pingback: Undecided » Blog Archive » Wordpress 2.6 Revisioning & Auto Save features

After define('DB_COLLATE', ''); should be fine.

Thanks for this great post Lester! I installed your Revision Control plugin, and followed your directions for deleting all the revisions in my database. Awesome! I couldn’t believe how many entries were in the database for the revisions. No wonder my post #’s were getting so high. Sheesh. This is sloppy work from WordPress.

Hi Brian, thanks for the compliments. I think the Revision Control plugin is from dd32 and is inspired by this post =D

Pingback: Organize Series and WordPress 2.6 | Is there food?

Pingback: Weekend Links #2 | OMNINOGGIN

Is this what I need to clean up the old revisions?

DELETE b,c
FROM wp_posts a
LEFT JOIN wp_term_relationships b ON (a.ID = b.object_id)
LEFT JOIN wp_postmeta c ON (a.ID = c.post_id)
WHERE a.post_type = ‘revision’

@oldengine Yours is more detailed, as mine only cleans up wp_post table and not the term_relationships table and wp_postmeta table.

Did the code work for you?

It came from here:
http://andreineculau.com/blog/2008/07/delete-wordpress-26-revisions/

I was just looking to see if this was a recommended procedure. (My database is a mess of revisions and it needs a complete cleaning.)

Pingback: ?????? Post Revision ?? WordPress 2.6 : XirBIT.Com
Pingback: Desactivar Revisiones en Wordpress 2.6 | Phylosoft
Lester Chan on 23rd July 2008 at 14:30 said:

@Ryan Boren, @noname : Yea I confirm that auto save does not create a revision. My bad.
DD32 on 23rd July 2008 at 14:58 said:

Just a heads up: I wrote a plugin which allows some control over the post revisions (Disabling in admin, Enabling on per post basis, limiting number of revisions, etc): http://dd32.id.au/wordpress-plugins/revision-control/

PS. @validation function: ‘ ‘ is a valid character in an email address
DD32 on 23rd July 2008 at 14:59 said:

Oh.. It doesnt like the plus symbol at alll.. Lovely
Lester Chan on 23rd July 2008 at 15:25 said:

@DD32: Nice! WordPress should have that in the core.
Pingback: WordPress 2.6 - jak wy??czy? system rewizji? | WPNinja
Wakefield on 23rd July 2008 at 18:03 said:

This ‘feature’ has been a terrible nuisance to me as well. Thank you very, very much for this helpful post. It’s brought a much needed smile to my hour of trying to figure out what’s going on.

Now on to clean out database tables. I’m a bit, actually quite, disappointed with the devs on this one and definitely agree such a feature should be accessible under Settings in admin.
Wakefield on 23rd July 2008 at 18:39 said:

After disabling Post Revisions, I did manage to get one post ID ‘skipped’ so far after about five test posts. Hopefully it’s not autosave causing this. There is still something that may be wrong and hopefully isn’t hastily overlooked (Ryan).
Pingback: Wordpress Revision History : Yuting Zhang’s Homepage
Robert on 24th July 2008 at 16:06 said:

Don’t put it at the end of wp-config.php or it won’t work.
Rachel on 24th July 2008 at 22:58 said:

Can’t believe this bloody thing is a feature! Thanks for the help
oldengine on 25th July 2008 at 00:09 said:

This must be a sore spot at WordPress software central.

Comment from support: “First question: Why do you think that it matters how many posts/pages/revisions/whatever are in the database? Databases are fast and efficient, and text compresses easily, you know.”

http://wordpress.org/support/topic/191420?replies=1#post-812141
Pingback: Delete Wordpress 2.6 Revisions | Andrei Neculau
Pingback: Abschalten Post Revision in WordPress 2.6 - Beitrag - Heimpold.net
Max on 25th July 2008 at 04:11 said:

Thanks for fix!!! I cannot believe WP guys came up with this “feature” and did not announce how to fix it…
oldengine on 25th July 2008 at 10:22 said:

It appears there is another version of this fix out there.

Is it this:

define(‘WP_POST_REVISIONS’, false);

or this:

define (‘WP_POST_REVISIONS’, 0);
Pingback: bobpeers -> blog » Turn Off Post Revision In WordPress 2.6
Lester Chan on 25th July 2008 at 17:17 said:

@oldengine: Both is the same thing as false is equals to 0 as well.
drk on 26th July 2008 at 05:51 said:

thank you,
this was helpful!
Nate on 27th July 2008 at 20:51 said:

Where do I put the snippet of code in the wp-config.php file??
Pingback: Undecided » Blog Archive » Wordpress 2.6 Revisioning & Auto Save features
Lester Chan on 27th July 2008 at 21:58 said:

After define('DB_COLLATE', ''); should be fine.
Brian on 28th July 2008 at 21:46 said:

Thanks for this great post Lester! I installed your Revision Control plugin, and followed your directions for deleting all the revisions in my database. Awesome! I couldn’t believe how many entries were in the database for the revisions. No wonder my post #’s were getting so high. Sheesh. This is sloppy work from WordPress.
Lester Chan on 29th July 2008 at 01:18 said:

Hi Brian, thanks for the compliments. I think the Revision Control plugin is from dd32 and is inspired by this post =D
Pingback: Organize Series and WordPress 2.6 | Is there food?
Pingback: Weekend Links #2 | OMNINOGGIN
oldengine on 30th July 2008 at 11:37 said:

Is this what I need to clean up the old revisions?

DELETE b,c
FROM wp_posts a
LEFT JOIN wp_term_relationships b ON (a.ID = b.object_id)
LEFT JOIN wp_postmeta c ON (a.ID = c.post_id)
WHERE a.post_type = ‘revision’
Lester Chan on 30th July 2008 at 14:19 said:

@oldengine Yours is more detailed, as mine only cleans up wp_post table and not the term_relationships table and wp_postmeta table.

Did the code work for you?
oldengine on 30th July 2008 at 20:41 said:

It came from here:
http://andreineculau.com/blog/2008/07/delete-wordpress-26-revisions/

I was just looking to see if this was a recommended procedure. (My database is a mess of revisions and it needs a complete cleaning.)