supriyassurve

Published content manager which creates a copy of updated content and keeps the current published copy intact. One must publish the new custom pending copy which will update the original post and you may view the updated content. This also works with the custom fields.

Future Revisions Manager

Published content manager which creates a copy of updated content and keeps the current published copy intact. One must publish the new custom pending …

Erick Hitter

WordPress 3.6 allows users to control how many revisions are stored for each supported post type. No longer must you rely on the <code>WP_POST_REVISIONS</code> constant, which applied universally. This plugin provides an interface for this new functionality.
With this plugin enabled, simply visit Settings > Writing to specify the number of revisions retained for each post type.
Why is this helpful? Revisions are stored in the database, and if many are stored, can cause bloat. This bloat may lead to slower queries, which can have a noticeable performance impact. The value of these revisions also depends on what is being tracked. For example, I may want to store every revision of the posts I write, but only desire to keep the latest five versions of each page on my site. Starting in WordPress 3.6, this control is available. WordPress doesn’t provide a native interface to specify revisions quantities, so I wrote this quick plugin to do so.
Thanks to Maria Ramos at <a href="http://www.webhostinghub.com/" rel="nofollow ugc">WebHostingHub</a>, the plugin is also available in Spanish. Many thanks to her for her efforts!
Development is at https://git.ethitter.com/wp-plugins/wp-revisions-control.

WP Revisions Control

Allows for setting the number of revisions per post type (which has revisions enabled) :D



Promises and Delivers

Control how many revisions are stored for each post type.

Future Revisions Manager vs WP Revisions Control