Dominik Schilling

benlumley

<p>Filename based cache busting for WordPress scripts/styles using last modified date.</p>
<p>Stop telling clients or users to hard refresh / shift refresh. The url to all of the css/js files on your site will change automatically whenever the files are modified. You can set proper long cache lifetimes to help get top scores on Google Pagespeed without running into cached css/javascript problems.</p>
<p>Based on this gist https://gist.github.com/ocean90/1966227 from Dominik Schilling, I’ve enhanced it by automatically replacing the asset version with the files modification time and automatically editing htaccess – making it install + forget.</p>
<p>Includes querystring option as a fallback – which works in more scenarios.</p>
<h3>Webservers</h3>
<h4>Apache</h4>
<p>The plugin should add what it needs to your .htaccess file jsut like WP itself. But if for any reason that doesn’t work for you – here’s what it adds:</p>
<pre><code># FBACB
<IfModule mod_rewrite.c>
  RewriteEngine On
  RewriteBase /

  RewriteCond %{REQUEST_FILENAME} !-f
  RewriteCond %{REQUEST_FILENAME} !-d
  RewriteRule ^(.+)\.([0-9\.]+)\.(js|css)$ $1.$3 [L]
</IfModule>

# still fbacb
<IfModule mod_expires.c>
    ExpiresActive on
    ExpiresByType text/css                            "access plus 1 year"
    ExpiresByType application/javascript              "access plus 1 year"
</IfModule>
# END FBACB
</code></pre>
<h4>NGINX</h4>
<pre><code> location ~* ^(.+)\.(?:\d+)\.(min.js|min.css|js|css)($|\?.*$) {
   try_files $uri $1.$2;
 }
</code></pre>
<h3>Host specific notes</h3>
<p>Some webhosts need a bit of custom config to get the filename based urls working.</p>
<h4>WP Engine</h4>
<p>To work on WP-Engine, you’ll need the following redirect added via my.wpengine -> installname -> Redirect rules</p>
<pre><code> Source: ^(.+)\.([0-9\.]+)\.(js|css)$
 Dest: $1.$3
 Type: break (this is under advanced)
</code></pre>
<h4>CloudWays</h4>
<p>Just works.</p>
<h4>Flywheel</h4>
<p>Just works.</p>
<h4>PHP Fallback</h4>
<p>If your webserver is failing to serve assets using url rewriting, the plugin attempts to serve them itsef (ie: via PHP). Obviously this is slow/less than ideal in production (it’ll be much slower) – so you should configure your web server correctly to serve the files. If you see this HTTP header “FBACB-Php-Fallback: yes” on your assets, this applies to you.</p>
<p>Note that hosts are increasingly configured to serve css/js directly from disk and won’t fall back to PHP + WordPress error handling – this fallback then won’t work.</p>


Filename based asset cache busting

Filename based cache busting for WordPress scripts/styles using last modified date.

Jenn Lee

<p>Replace any plugin or theme asset source with your own desired source. Main purpose is to help WordPress users to change the slow third party scripts or styles which using by some plugins but slow load speed in certain countries.</p>
<p>Usually, you could use some coding skills to find the original enqueue method from the target plugin, then dequeue it, and enqueue your own version of asset file. But you need to take care and follow the same way how the original plugin enqueued and the dependency plus version. Otherwise, you might encounter some unexpected issues.</p>
<p>With the help of this plugin, you can easily replace the asset source file without coding skills.</p>
<p>This plugin is not meant to auto local host the third party asset file, but you could use for it too. Upload your own local version of asset file in a better and secured folder (maybe from your theme folder), get the public accessible url, use it on the plugin setting page. Just try it out and have fun.</p>
<h4>How It Works</h4>
<p>Once a new replacement set, this plugin will do a match on all queued asset styles and scripts source. If found the matching source, it will replaces target source URL with your replacement URL.</p>
<p>This plugin is not going to dequeue the target asset and enqueue your replacement asset. Issue might be happened if the new enqueue not follow the original plugin or theme like missing dependency or version incorrect etc.</p>
<p>If the target asset url not using the standard WordPress enqueue script method by the developer, the replacement will not works.</p>
<h4>Use Case</h4>
<p>There is a block in Malaysia since end of September 2021, which not allowed all local ISP network to access <strong>maxcdn.bootstrapcdn.com</strong>.</p>
<p>If there is a plugin in your site using the asset file hosted on <strong>maxcdn.bootstrapcdn.com</strong>, the visitor from Malaysia will encounter super slow loading issue.</p>
<p>With the help of this plugin, you can easily replace this asset file url to maybe <strong>cdnjs.cloudflare.com</strong> without disturbing the functionality of the original plugin.</p>
<p><strong>Tutorial for this use case:</strong></p>
<p><a href="https://itchycode.com/use-replace-asset-source-wordpress-plugin-to-solve-maxcdn-bootstrapcdn-mcmc-blocked-issue-in-malaysia/" rel="nofollow ugc">Solve maxcdn bootstrapcdn problem in Malaysia</a></p>


Replace Asset Source

Replace plugins or themes asset source with your own desired source. Not design for auto local host asset file. But you can use for it too.

Filename based asset cache busting vs Replace Asset Source