Steve Grunwell

<p>Unless post revisions are explicitly limited, WordPress will build up a hefty sum of revisions over time. While it’s great to have revision history for some recent content, the chances that old revisions will be necessary diminish the longer a post has been published. Revision Strike is designed to automatically remove these unneeded revisions on older, published posts.</p>
<h4>How does it work?</h4>
<p>First, a threshold is set, with a default of 30 days. Once a day, Revision Strike will run and find any post revisions in the database attached to published posts with a post date of at least 30 (or your custom threshold) days ago, and “strike” (tear-down and remove) them from the WordPress database.</p>
<h4>Contributing</h4>
<p>If you’d like to help build Revision Strike, please <a href="https://github.com/stevegrunwell/revision-strike" rel="nofollow ugc">visit the plugin’s GitHub page</a>. Contributors are welcome, and <a href="https://github.com/stevegrunwell/revision-strike#contributing" rel="nofollow ugc">details can be found in the repo’s README file</a>.</p>


Revision Strike

Periodically purge old post revisions via WP Cron.

slehner

<p>Revisions are a main part of every content management system.</p>
<p>Normal wordpress revisions only containing the title, content and excerpt. And WordPress by itself will only add a new revision, when one (or more) of these three fields were changed. This means, if someone only changes the permalink for example, then WordPress doesn’t add any revision. And if someone changes the content and maybe the author, then WordPress adds a revision, but only with the old content – the author change will be lost.</p>
<p>For small blogs this will be ok, but what’s about multi-author websites or blogs?</p>
<p>I wrote this small plugin for you – for a better revision management in multi-author blogs and sites, for better monitoring the changes of every site, post or custom-post-type and finally for better restoring older revisions.</p>
<p>So, this plugin adds following fields to the revision system:</p>
<ul>
<li>The Author</li>
<li>Post Date</li>
<li>Permalink</li>
<li>Post Status</li>
<li>Post Password</li>
<li>Comment Status</li>
<li>Ping Status</li>
<li>Post/Page Parent</li>
<li>Menu Order</li>
<li>more to come</li>
</ul>
<p>This Plugin also adds a new revision, if only one of the fields above were changed. And it works with automated post/page saves (to the server) too. But I have disabled the client side autosave – becaus on multi-author blogs/sites these function makes no sense and confuses authors more than it helps. But the autosave to the server works perfectly well with all of the fields above added.</p>
<p>If you want to restore a revision, the fields above will restored too. And in case of deleting a post/page, than all revision with all fields above will be deleted too – for a smaller and cleaner database.</p>
<p>No further configuration is needed, the plugin doesn’t add any database tables rather saves additional revision data to post-meta and works with custom-post-types too. It’s translation ready and allready translated into german.</p>
<h4>Gutenberg support was added</h4>
<p>Now it works with the new Block-Editoe (Gutenberg) and the old Classic-Editor (tinyMCE).</p>


Better Revisions

Extend your Revisions: Add important fields like "Permalink" or "Status" to the revisions for a better Content Management.

Revision Strike vs Better Revisions