v3.2.0

Added configurable status code caching that allows to:

• Cache error responses (404, 403, etc.) for guest users
• Set custom TTL (Time To Live) for each status code

This feature is particularly useful for forums that experience high volumes of bot traffic or requests to deleted/moved content, as it prevents unnecessary database queries and PHP processing for unsuccessful requests.

Full Changelog: v3.1.0...v3.2.0

v3.1.0

What's Changed

• Compatibility with fof/merge-discussions extension

Full Changelog: v3.0.1...v3.1.0

v3.0.0

This is an overhaul of the extension, with most of the codebase being rewritten.

Changed

• Implemented a new, more robust method for detecting resource updates and cache purging. This new system works in both HTTP and CLI contexts. The previous implementation only functioned in HTTP context, which meant that resource updates processed in job queues were not detected

• Minimum required PHP version is now 8.1

Added

• Compatibility with sycho/flarum-move-posts extension
• Compatibility with clarkwinkelmann/flarum-ext-author-change extension
• Developer documentation for adding custom LSCache support to extensions or forums

Full Changelog: v2.3.1...v3.0.0

v2.3.1

• fix: Do not set vary cookie if something bypassed session. This improves compatibility with the blomstra/realtime extension

Full Changelog: v2.3.0...v2.3.1

v2.3.0

What's Changed

• Compatibility with v17development/flarum-blog extension

Full Changelog: v2.2.1...v2.3.0

v2.2.1

What's Changed

• fixed a warning on post delete
• purge users index cache on post like

Full Changelog: v2.2.0...v2.2.1

v2.2.0

What's Changed

Added

Introduced cache purging for a user profile when a post is added or updated.

Fixed

Resolved a potential issue with tag cache purging when another middleware has read the response.

Full Changelog: v2.1.0...v2.2.0

v2.1.0

What's Changed

Added:

• Cache purging for tags associated with a discussion upon updates or new posts.

Docs:

• Added information on how one can support the extension's development.

Fixed:

• Resolved an issue with fof/masquerade compatibility. Previously, when a user with permissions edited someone else's profile, the cache of the editor's profile was cleared instead of the edited user's profile.

Full Changelog: v2.0.1...v2.1.0

v2.0.1 - Fixed login for installations in subdirectories

Fixed an issue with logging into Flarum when installed in a subdirectory. Now, logging in works correctly regardless of where Flarum is installed.

Full Changelog: v2.0.0...v2.0.1

v2.0.0

🚨 Breaking change. Before updating, please remove the <IfModule LiteSpeed>...</IfModule> code block from your .htaccess file. From this version forward, this extension will automatically add the necessary configurations to your .htaccess file when you run the php flarum migrate command after updating the extension.

Updating Process:

Before updating, it's recommended to create a backup of your .htaccess file and remove the <IfModule LiteSpeed>...</IfModule> code block. Then proceed with the following commands:

composer require acpl/flarum-lscache
php flarum migrate
php flarum cache:clear

Added:

• .htaccess file management. The extension now has the capability to edit the .htaccess file. This simplifies the installation process and paves the way for future admin panel options that require editing the .htaccess file.
• The "Drop Query Strings" option. This feature allows the generation of a single cache version regardless of the query string. By default, parameters such as "utm", "fbclid", and others are "dropped" or ignored.
• Introduced a new setting to enable or disable LSCache. If LSCache is turned off, all cached entries will be automatically purged, providing greater control over your cache.

Improvements:

• Improved the clarity and readability of translations.

Fixed:

• Added missing old migration that was causing problems when uninstalling the extension. A backport has also been implemented for v1.0 (see v1.0.2).

Full Changelog: v1.0.1...v2.0.0