jkeyes

Revision History displays the revision history of a post or page, with links 
to the content of each revision.
The revision history is appended to the <code>content</code> of the post or page.
The following are configuration settings which can be changed in the Revision 
History submenu of ‘Settings’.
<ol>
<li>Display on pages.</li>
<li>Display on posts.</li>
<li>Show autosave revisions.</li>
<li>Show the revision timestamp in the post title.</li>
</ol>
By default the revision history is not shown on any posts or pages.
For control over where you place the revision history use the <code>rh_the_revision</code> function. 
It takes optional parameters, before and after. For example:
<pre><code><?php rh_the_revision('<h4>', '</h4>'); ?>
</code></pre>

Revision History

Revision History displays the revision history of a post or page, with links to the content of each revision.

slehner

Revisions are a main part of every content management system.
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.
For small blogs this will be ok, but what’s about multi-author websites or blogs?
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.
So, this plugin adds following fields to the revision system:
<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>
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.
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.
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.
<h4>Gutenberg support was added</h4>
Now it works with the new Block-Editoe (Gutenberg) and the old Classic-Editor (tinyMCE).

Better Revisions

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

Revision History vs Better Revisions