Steve Grunwell

Growella

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.
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.
<h4>Usage</h4>
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>.
Example
<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>
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.

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.

KLicheR

A plugin inspired by Drupal’s modules (<a href="https://drupal.org/project/features" rel="nofollow ugc">Features</a> and <a href="https://drupal.org/project/strongarm" rel="nofollow ugc">Strongarm</a>) that enable the versioning of options in WordPress.
The general idea is to export a maximum amount of settings and structural content of the database to files to be able to deploy them through <a href="https://en.wikipedia.org/wiki/Revision_control" rel="nofollow ugc">VCS</a> (like SVN, GIT, Mercurial).
For now, the only exportable settings are the entries of the “wp-options” table.
<h4>Do you need this?</h4>
If you’re the only developer working on you’re website, you’re having only one development environment (production server) and you do not use <a href="https://en.wikipedia.org/wiki/Revision_control" rel="nofollow ugc">VCS</a>: no, the only things you need is to close your eyes, cross your fingers and hope that everything go fine.
<h4>How to use it?</h4>
In the admin, a new page called Features is accessible under the Tools menu. This page list all the settings contain in your features_options_data.php file. If one of the setting in your database has not the same value of the one in the file, the Revert button will be accessible to click and a text field will show you the value from the database.
<ul>
<li>If you want to replace what is in the database with the value from the file, click the Revert button.</li>
<li>If you want to replace what is in the file with the value from the database (for versioning), copy the content of the text field to the file.</li>
</ul>
<h4>Add a new option to the filter</h4>
To add a new option from the wp_options table, use the features_options filter to alter the options array: column value as the key and the option_value column value as the value.
<h4>What’s next?</h4>
This plugin is under development. If you know what your doing, you can use it and there will be an upgrade path, at least, a manuel one.
Like <a href="https://drupal.org/project/features" rel="nofollow ugc">Features</a>, the goal would be to have plugins generation for features instead of manually edit the features_options_data.php file of the plugin.

Features

A plugin inspired by Drupal's modules (Features and Strongarm) that enable the versioning of options in Wordpress.

Dynamic Asset Versioning vs Features