I'd like to suggest adding a hook which allows other modules to inform Boost what pages also need to be flushed on node expire. I'm using this for a custom module of mine, and I think others may also find it useful.

Please see patch.

Feel free to mangle the patch. I'm not particularly happy with hook_boost_expire_node() returning an array so if you can think of a better signature, that's good with me.

Thanks.

CommentFileSizeAuthor
boost-expire-node-hook.patch.txt736 bytesbengtan

Comments

bengtan’s picture

bengtan commented

Bump please.

Alice Heaton’s picture

Alice Heaton commented
Status: Needs work » Active

Hi,

I also would really like this feature.

I have a fairly complex site, with a lot of automatically generated pages containing several views in blocks (using the composite_layout module).

None of Boosts' settings can let me say when those pages' cache should be cleared - however, as it's all generated there are clear rules. If I could use the hook proposed by bengtan, I could really fine tune my cache clearing by writting the code myself, specifically tailored for that site.

+1

Alice Heaton’s picture

Alice Heaton commented
Status: Active » Needs work

A few thoughts about the proposed patch :

1. Maybe it should check whether $result['paths'] and $result['data'] are defined ?

2. As it is, modules have the option to override derivates that were added by Boost. I'm not sure this is a good behaviour ? Maybe the module should enforce a prefix to the paths/data keys ?

Let me know what you think.

Status: Active » Needs work

Correcting issue status, see #2125263: Issue status not taken from last comment during D7 migration.