Is there any valid reason why this filter can't cache?

Created on 1 August 2013, over 11 years ago
Updated 16 January 2025, about 1 month ago

Having the 'cache' flag on this filter set to FALSE means that any text formats that use this filter can no longer be cache, which makes can cause major performance issues based on the content and complexity other filters in the text format.

Is there any valid reason why this format can't be cached? And if so, why not make it configurable? My clients usecase for this module is to insert tokens that are static, and if they change at any stage they site cache can be regenerated at that point.

Patch coming to remove the flag, but happy to change the patch at a future point to make it configurable.

💬 Support request
Status

Closed: outdated

Version

1.0

Component

Code

Created by

🇦🇺Australia Deciphered

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

Production build 0.71.5 2024