Rev Asset model urls with date modified timestamps. Its simple… just call the
function and pass the asset and an optional transform.
Before:
Template: {{ asset.url(transform) }}
Output: https://local.craft3/uploads/biggie.jpg
After:
Template: {{ nsm_rev_asset_url(asset, transform) }}
Output: https://local.craft3/uploads/biggie.1496670969.jpg
Additionally NSM Asset Rev can check a manifest file for urls and return the marching revved url.
Manifest:
{ "app.css": "app.1e9915c1398b2ba2fcc2.css" }
Before:
Template: {{ url(app.css) }}
Output: https://local.craft3/app.css
After:
Template: {{ nsm_rev_manifest_url('app.css') }}
Output: https://local.craft3/app.1e9915c1398b2ba2fcc2.css
Manifest files will most likely be created from a build process.
Here's some examples:
Note: NSM Asset Rev only supports one level key: value pairs.
Open a command console, enter your project directory and execute the following command to download the latest stable version of this bundle:
$ composer require newism/craft3-asset-revThis command requires you to have Composer installed globally, as explained in the installation chapter of the Composer documentation.
Install plugin in the Craft Control Panel under Settings > Plugins.
This plugin provides two twig functions.
{{ nsm_rev_asset_url(asset, transform) }}
{{ nsm_rev_manifest_url(url) }}
There's actually three twig functions :). The third is a helper that either calls
nsm_rev_asset_url or nsm_rev_manifest_url based on the arguments.
If the first argument is an Assetl then nsm_rev_asset_url will be called
internally:
Template: {{ nsm_rev_url(asset, transform) }}
Output: https://local.craft3/uploads/biggie.1496670969.jpg
If the first argument is an string model then nsm_rev_manifest_url will be called
internally:
Template: {{ nsm_rev_url('app.css') }}
Output: https://local.craft3/app.1e9915c1398b2ba2fcc2.css
Important: This plugin doesn't actually change the the filename on the server. You'll need to implement rewrite rules in your apache conf or nginx access.
See: https://github.com/h5bp/server-configs-apache/blob/master/dist/.htaccess#L968-L984
# ----------------------------------------------------------------------
# | Filename-based cache busting |
# ----------------------------------------------------------------------
# If you're not using a build process to manage your filename version
# revving, you might want to consider enabling the following directives
# to route all requests such as `/style.12345.css` to `/style.css`.
#
# To understand why this is important and even a better solution than
# using something like `*.css?v231`, please see:
# http://www.stevesouders.com/blog/2008/08/23/revving-filenames-dont-use-querystring/
# <IfModule mod_rewrite.c>
# RewriteEngine On
# RewriteCond %{REQUEST_FILENAME} !-f
# RewriteRule ^(.+)\.(\d+)\.(bmp|css|cur|gif|ico|jpe?g|js|png|svgz?|webp|webmanifest)$ $1.$3 [L]
# </IfModule>
See: https://github.com/h5bp/server-configs-nginx/blob/master/h5bp/location/cache-busting.conf#L1-L10
# Built-in filename-based cache busting
# This will route all requests for /css/style.20120716.css to /css/style.css
# Read also this: github.com/h5bp/html5-boilerplate/wiki/cachebusting
# This is not included by default, because it'd be better if you use the build
# script to manage the file names.
location ~* (.+)\.(?:\d+)\.(bmp|css|cur|gif|ico|jpe?g|js|png|svgz?|webp|webmanifest)$ {
try_files $uri $1.$2;
}
See ./src/config.php.
Some things to do, and ideas for potential features:
- Release it
Add manfiest based revving- Integrate other 3rd party image manipulation plugins as they become available
Brought to you by Newism
