Needs review
Project:
Cache Warmer
Version:
7.x-4.x-dev
Component:
Code
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
29 Oct 2014 at 12:44 UTC
Updated:
18 Mar 2016 at 08:08 UTC
Jump to comment: Most recent
Hey,
we wanted to be able to warm the caches hub file after creating a new, or updating a existing content.
To be able to do this, we wrote a simple rules integration as a submodule. The submodule contains a small admin interface where the user is able to add a absolute path to his hub file.
After adding the file, the user have to add the new rule action "Execute cache warmer" to its rule and voilà.
Greetings
sg
| Comment | File | Size | Author |
|---|---|---|---|
| cache_warmer_rules_intergration.patch | 4.96 KB | sgurlt |
Comments
Comment #1
vacilando commentedThis is a VERY good try, exactly in the right direction: little config screen for the hub path, and Rules integration for re-caching.
However, it does not seem to work with Cache Expiration (expire) module. If you set page add/update/delete as trigger, Cache Warmer seems to run before expire purges the caches. So in the end when the user comes to the page the cache is cold.
Any ideas / experiences? Perhaps using another trigger would help?