Closed (fixed)
Project:
Boost Expire
Version:
7.x-1.0
Component:
Code
Priority:
Major
Category:
Bug report
Assigned:
Reporter:
Created:
15 Jan 2012 at 16:46 UTC
Updated:
5 Apr 2012 at 14:00 UTC
Jump to comment: Most recent file
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.
| Comment | File | Size | Author |
|---|---|---|---|
| #3 | minimum-cache-lifetime-1405656-3.patch | 2.46 KB | geerlingguy |
| boost_expire.jpg | 50.6 KB | denny84 |
Comments
Comment #1
geerlingguy commentedBoost 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...
Comment #2
denny84 commentedThanks for the update. I will keep tabs on cache expiration module stable release.
Comment #3
geerlingguy commentedI'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).
Comment #4
geerlingguy commentedCommitted: http://drupalcode.org/project/boost_expire.git/commit/30c753b
Comment #5
denny84 commentedGreat thats awesome. I will give it a try.