If you have a team of content contributors, users who are also posting content as authors, your WordPress post database will likely fill up with more records storing these revisions that will probably never see the light of day. I can see keeping the revisions for pages around, maybe up to 5 revisions back, but the auto save feature in WordPress is often a little too vigilant in my opinion.
That’s where the “Optimize Database After Deleting Revisions” plug-in comes in. It’s a great utility. There are plenty of useful options to automatically empty trashed items, schedule running this optimization at time intervals, and even keeping a specified number of revisions.
You know, sometimes I think WordPress should keep plug-ins separate from these type of utilities. Utilities like this may not be used everyday and are independent of your site’s functions of delivering content to the public.
Which leads me to a separate article: So, why not separate plug-ins and these type of utilities?
