Attached Image: Setting minimum cache lifetime to 1min. Still "boost expire" module flushes the cache on node update. Am I understanding this module correctly or something wrong here?

Thanks in advance.

Comments

geerlingguy’s picture

Boost Expire is kind of a dumb module in this regard; it does not respect the minimum cache lifetime right now, and I'm not sure if I'll try implementing this feature, as Boost Expire is a pretty simple concept—when you save a node, comment, etc., Boost's cache is flushed—and I hope that more complex cache expiry will either be added by integration with the Cache Expiration module, or maybe as another revision of this module...

denny84’s picture

Thanks for the update. I will keep tabs on cache expiration module stable release.

geerlingguy’s picture

Title: Boost expire does not respect "Minimum Cache Lifetime" option » Respect "Minimum cache lifetime" option
Assigned: Unassigned » geerlingguy
Status: Active » Needs review
StatusFileSize
new2.46 KB

I've added code to allow Boost Expire to be configured to respect the Minimum cache lifetime option, as set on the Performance page. Patch attached. Will commit soon (I've tested on my local computer).

geerlingguy’s picture

Status: Needs review » Fixed
denny84’s picture

Great thats awesome. I will give it a try.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.