Compatibility with Boost

I think removing from boost cache just that one node should not be a big deal, but it's not a solution, because adding/changing one node may affect lots of other pages - e.g. if you post to the front page a news article with some tags, it affects the node page, the front page, taxonomy pages, all pages where the 'Recent news' block or taxonomy blocks are visible, and so on.

I think it may depend on the node. For example, if we edit the title of the 'What's this all about' node visible in the main menu block, it should most probably affect all pages of the site.

Please review the patch for the boost module in #1126122: Boost ability to invalidate/clear cache for single items based on event handler hooks like hook_node_update() comment #15.

See previous comment. I had forgotten to change the issue status.

There are no needs in Boost expire module anymore. Check out 7.x-2.x of Cache expiration.

@Spleshka - is there any documentation on how someone could use Cache expiration with Boost? Before I put any kind of deprecation notice on Boost Expire's project page, I'd like to have a simple guide so people aren't left in a lurch and have to figure out how to simply expire caches after nodes/comments are saved.

Boost module has integration with Cache Expiration via hook_cache_expire(). It means that if user configures to expire pages after some actions, Boost will recieve urls of this pages and expires them itself (see boost_cache_expire()).

Some screenshots for you:

Module settings:

Entity expiration configuration sample:

Sweet! When I get a few minutes, I'm going to make sure I have things in order for Boost Expire, then mark it as deprecated with the proper pointers for people ready to switch to Cache Expiration.

Thank you!

Okay, back to fixed; I've deprecated the Boost Expire module—see #2029269: Deprecate Boost Expire in favor of Cache Expiration.

Great, thanks!