Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Allow for fine control over what gets flushed ASAP and what will be queued to be flushed (by changing the expired time in the database). Places where you would have the option to go either way.
Comments
Node editing
Node referrer
Reverse node referrer
Voting API
Taxonomy
User profiles
Cache configuration block
Views containing this node
Would be a hackish implementation of this feature request #579720: minimum & maximum cache expiration times; how often you run cron would be determine the minimum cache lifetime.
Comment | File | Size | Author |
---|---|---|---|
#1 | boost-600360.patch | 6.1 KB | mikeytown2 |
Comments
Comment #1
mikeytown2 CreditAttribution: mikeytown2 commentedAll or none; Flush button on block will kill the cache though.
Comment #2
mikeytown2 CreditAttribution: mikeytown2 commentedcommitted