This Craft CMS 2.x plugin is no longer supported, but it is fully functional, and you may continue to use it as you see fit. The license also allows you to fork it and make changes as needed for legacy support reasons.
The Craft CMS 3.x version of this plugin can be found here: craft-fastcgicachebust and can also be installed via the Craft Plugin Store in the Craft CP.
FastCGI Cache Bust plugin for Craft CMS
Bust the Nginx FastCGI Cache when entries are saved or created.
Related: FastCGI Cache Bust for Craft 3.x
To install FastCGI Cache Bust, follow these steps:
- Download & unzip the file and place the
fastcgicachebustdirectory into your
- -OR- do a
git clone https://github.com/nystudio107/fastcgicachebust.gitdirectly into your
craft/pluginsfolder. You can then update it with
- -OR- install with Composer via
composer require nystudio107/fastcgicachebust
- Install plugin in the Craft Control Panel under Settings > Plugins
- The plugin folder should be named
fastcgicachebustfor Craft to see it. GitHub recently started appending
-master(the branch name) to the name of the folder for zip file downloads.
FastCGI Cache Bust works on Craft 2.5.x and Craft 2.6.x.
FastCGI Cache Bust Overview
FastCGI Cache Bust is a simple plugin that clears your entire FastCGI Cache any time an entry is saved. This is somewhat of a scortched earth approach to cache invalidation, but it ensure cache coherency.
Check out the article Static Page Caching with Craft CMS for details on how to set up FastCGI Cache on your website.
Configuring FastCGI Cache Bust
Click on the gear icon next to the plugin to configure it by adding the full absolute path to your Nginx FastCGI Cache directory. If you require more than one FastCGI Cache directory cleared, separate the paths with a comma (
Using FastCGI Cache Bust
FastCGI Cache Bust listens for elements being saved, and busts the entire FastCGI Cache automatically when that happens.
You can also manually clear the FastCGI Cache via Craft's 'Clear Caches' tool
FastCGI Cache Bust Roadmap
Some things to do, and ideas for potential features:
- We could invalidate only affected caches onElementSave instead of the entire cache
Brought to you by nystudio107