Paul Menard

<p>Provide Versioning, Preview and Rollback ability on Pages and Posts.</p>
<p><a href="http://www.codehooligans.com/2008/04/18/versioning-your-blog-content/" title="Versioning Your Blog Content" rel="nofollow ugc">Plugin Homepage</a></p>
<h3>Version Histroy</h3>
<p>
1.0 – 2008-03-16: Initial release<br />
1.1 – 2008-03-21: Fixed slight error in INSERT SQL for the new Revision. Also fixed escape on inserted content.<br />
1.1b- 2008-04-04: Changed the ‘post_status’ value on the saved revision to ‘inherit’ as this was causing problems with some other plugins. <br />
1.1c- 2008-04-17: Added notation to indication current version.<br />
1.2 – 2008-04-18: Changes to Admin display section to make things work under WP 2.5<br />
1.8 – 2008-05-04: changes to enhance WP 2.5 design integration. Added ability to delete revisions, set a no revision ‘minor-edit’ option, set a no revisions for life checkbox. Display on last 5 revisions with link to reveal more. <br />
1.8.3 – 2008-05-23: Minor changes to display. Added link to reload most current version of content. </p>


Revisions

Provide Versioning, Preview and Rollback ability on Pages and Posts.

Steve Grunwell

Growella

<p>WordPress asset versioning can be a double-edged sword: on one-hand, it’s extremely effective for cache-busting, ensuring you aren’t sharing stale scripts or styles to your visitors. On the other hand, having to manually increment a version number is a pain (even <a href="https://10up.github.io/Engineering-Best-Practices/php/#asset-versioning" rel="nofollow ugc">as a constant</a>), often resulting in a version control history full of “bumping the version number” commits.</p>
<p>Dynamic Asset Versioning aims to simplify this process: if an enqueued asset doesn’t have an explicit version number, the plugin will get the timestamp of the last time the file was changed and use that as the version number. It’s easy: you touch the file, the version number is updated automatically.</p>
<h4>Usage</h4>
<p>Once Dynamic Asset Versioning is active, it will automatically determine version numbers based on file modification time for any [non-core] files that have been enqueued using <a href="https://developer.wordpress.org/reference/functions/wp_enqueue_style/" rel="nofollow ugc"><code>wp_enqueue_style()</code></a> or <a href="https://developer.wordpress.org/reference/functions/wp_enqueue_style/" rel="nofollow ugc"><code>wp_enqueue_script()</code></a>.</p>
<p><strong>Example</strong></p>
<pre><code>wp_enqueue_style(
    'my-theme-styles',
    get_template_directory_uri() . '/assets/css/my-styles.css',
    array( 'some-other-styles' ),
    false, // Don't worry about it, Dynamic Asset Versioning has you covered!
    'screen'
);
</code></pre>
<h4>Special thanks</h4>
<p>A special thanks goes out to <a href="http://10up.com" rel="nofollow ugc">10up</a>, who helped inspire the original concept of this plugin.</p>


Dynamic Asset Versioning

Exactly what I was looking for. Great stuff. Thanks guys

Amazing

Dynamically set asset version numbers based on file modification times, preventing stale caches.

Revisions vs Dynamic Asset Versioning