Please consider adding

function boost_expire_node_update($node) {
	if(isset($node->path) && isset($node->path['alias'])){
		boost_expire_flush_boost_cache(array('scope' => $node->path['alias']));
	}
	boost_expire_flush_boost_cache(array('scope' => 'node/'.$node->nid ));
}

I have currently adapted the boost_expire module but is seems logical to add to boost so that (by default) if a page is updated it is deleted from the cache. That way you can easily flush the whole cache daily or even weekly

Comments

hanoii’s picture

hanoii
Primary language Spanish
Location 🇦🇷UTC-3
commented

really interested in this and think it should be looked at.

Anonymous’s picture

Anonymous (not verified) commented

This already happens and is almost certainly open by mistake, if you edit a page then it is placed in the table queue for expiry and regeneration by cron. I just tested this and it works so unless you have a specific example of a case when it's not working then I'm going to close this. You can just edit a page by adding a space or something to test if the table is populated and then flushed the next cron run. FTP should show the timestamps for regeneration.

Thanks
Philip.