⚠️ ⚠️ ⚠️

This plugin is EOL. Minor patches may be issued. For a robust static cache solution, try Blitz.

CraftCMS LSCache Purge for Craft CMS 3.x

PURGE the LiteSpeed Cache on saving entries.

Installation

To install the plugin, search for LiteSpeed Cache on the Plugin store, or install manually with the following instructions:

1. Open your terminal and go to your Craft project:

    cd /path/to/project
   

2. Then tell Composer to require the plugin:

    composer require thoughtfulweb/lite-speed-cache
   

3. In the Control Panel, go to Settings → Plugins and click the “Install” button for LiteSpeed Cache.

Use

On Page Save

Choose whether or not to clear caches by URL, and set the directory where your LSCache folder is located in the plugin settings. If you do not select the per-URL option, all of the cached content in the LSCache folder will be removed on every page save.

Manually

If you just want to nuke the whole cache folder at once, you can go opt to Force Clear LiteSpeed Cache in the plugins CP section. Clicking the clear button will remove all of the cached content in the LSCache folder.

Forms

If you have forms on your website and you're using CSRF protection, you want to either:

1. Make an AJAX call to a plugin/module action that outputs your CSRF token and use the result to update your CSRF input.

{% js %}
    $(function() {
        $.get('/your/controller/action', function(data) {
                $('form.csrf').prepend('<input type="hidden" name="{{ craft.app.config.general.csrfTokenName }}" value="'+data+'" />');
        });
    });
{% endjs %}

2. Choose to not cache the page at all using the following Twig header.

{% header "X-LiteSpeed-Cache-Control: no-cache" %}

If you use the standard {{ csrfInput() }} inline, the tokens will be cached by Litespeed and all of your form submissions will fail.

Requirements

This plugin requires Craft CMS 3.0.0 or later.

Notes

If you're using per-URL purging, the plugin taps into Craft's native caching functionality, meaing you must use {% cache %} tags so that a cache record can be found on page save. If you don't have a cache record for the page you're saving, the plugin doesn't know it needs to PURGE that page, so won't.

Cloudflare

Due to CloudFlare being a reverse proxy, you cannot use CloudFlare and still use per-URL purging. Either do not route through CloudFlare, or just enable the global purge.