Fingerprint

The Fingerprint plugin is updated to be compatible with Kirby 2.3.0 and up using the new component architecture.

What is it?

The Fingerprint plugin adds fingerprints to css and js filenames based on their contents.

Why use it?

As the fingerprint on the file changes after the contents of the file have been changed it will help you bust the browsercache.

How to use it?

Add it using git: git submodule add https://github.com/iksi/KirbyFingerprint.git site/plugins/fingerprint or do it manually by downloading the repository, renaming the folder to fingerprint and placing it in /site/plugins. You can use the normal Kirby css() and js() helper functions.

Add the following lines to your htaccess file (after RewriteBase):

RewriteCond %{REQUEST_FILENAME} !-f
RewriteRule ^(.+)\.([0-9a-z]{32})\.(js|css)$ $1.$3 [L]

Or for Nginx you can add the following to your virtual host setup:

location /assets {
    if (!-e $request_filename) {
        rewrite ^/(.+)\.([0-9a-z]{32})\.(js|css)$ /$1.$3 break;
    }
}

Enable fingerprinting by adding the following to you config.php file:

c::set('fingerprint', true);

You can also use Kirby’s @auto for autoloading and fingerprinting template specific assets.

External urls

External urls won’t be fingerprinted.

Author

Iksi, https://www.iksi.cc/

ericcholis / KirbyFingerprint