5.9.0

Added

• Added the ability to ignore hints in the Blitz Hints utility (#714).

Changed

• CSRF tokens are now only loaded via a script in non-Sprig requests.

Fixed

• Fixed a bug that was preventing the organic regeneration of expired cached pages.

4.23.2

Changed

• CSRF tokens are now only loaded via a script in non-Sprig requests.

Fixed

• Fixed a bug that was preventing the organic regeneration of expired cached pages.

5.8.1

Fixed

• Fixed an error that could occur when updating to 5.8.0.

5.8.0

Added

• Added the onlyCacheLowercaseUris plugin setting.
• Added enabled lightswitches to the URI pattern and query string parameter settings.

Changed

• The injectScriptEvent event is now called on the window element instead of document.
• Increased the batch size used when flushing the entire cache.

Fixed

• Fixed some styling issues in the Blitz Diagnostics utility.
• Fixed false positives from appearing in the Blitz Hints utility when querying entry authors (#710).

4.23.1

Changed

• Improved the deletion of legacy cached element type records when updating to Blitz 4.10.1 and beyond.
• The injectScriptEvent event is now called on the window element instead of document.
• Increased the batch size used when flushing the entire cache.

5.7.1

Fixed

• Fixed a bug in which installing the plugin via the CLI could cause an error (#705).

5.7.0

Warning

This update includes a fix for an issue in which Blitz could send incorrect Cache-Control headers. Please read this article to find out whether the issue affects your site, and what you should do. To ensure the changes in this update are applied, the cache should be refreshed after this update completes.

Added

• Added a check for whether the cache should be refreshed after every request has ended, meaning that setting the RefreshCacheService::batchMode property no longer serves a purposes and can be safely removed.
• Added compatibility with Craft 5.3.0 for detecting eager-loading opportunities in the Blitz Hints utility.

Changed

• The expiry date displayed in the element sidebar panel now reflects the entry’s expiry date, if set and sooner than the cached page’s expiry date (#698).
• The refreshCacheEnabled config setting is now actually respected.

Fixed

• Fixed the default cache control header values that were inadvertently set to incorrect values (learn more).
• Fixed the nested element type count displayed in the Blitz Diagnostics utility.
• Fixed a bug in which the date cached and expiry dates were not being displayed in the correct timezone in the element sidebar panel (#698).
• Fixed a bug in which the homepage was not being displayed as cached in the element sidebar panel.
• Fixed a bug that was causing integrity constraint violation errors to be logged (#699).

Deprecated

• Deprecated the RefreshCacheService::batchMode property.

4.23.0

Warning

This update includes a fix for an issue in which Blitz could send incorrect Cache-Control headers. Please read this article to find out whether the issue affects your site, and what you should do. To ensure the changes in this update are applied, the cache should be refreshed after this update completes.

Added

• Added a check for whether the cache should be refreshed after every request has ended, meaning that setting the RefreshCacheService::batchMode property no longer serves a purposes and can be safely removed from your code.

Changed

• Blitz now requires Craft CMS 4.5.11 or later.
• The expiry date displayed in the element sidebar panel now reflects the entry’s expiry date, if set and sooner than the cached page’s expiry date (#698).

Fixed

• Fixed the default cache control header values that were inadvertently set to incorrect values (learn more).
• Fixed a bug in which the date cached and expiry dates were not being displayed in the correct timezone in the element sidebar panel (#698).
• Fixed a bug in which the homepage was not being displayed as cached in the element sidebar panel.

Deprecated

• Deprecated the RefreshCacheService::batchMode property.

5.6.4

Note

The cache should be cleared or refreshed after this update completes.

Changed

• Recreated some database tables to ensure that composite primary keys are correctly created.

5.6.3

Note

The cache should be cleared or refreshed after this update completes.

Fixed

• Fixed an exception that could be thrown during updating when using MariaDB (#693).