Is there any way to configure Boost so that the crawler only crawls the flushed pages immediately after a node is created, saved or deleted? Or, if this could be configured to happen when cron runs, it would be great, rather than crawling all of the nodes that have been marked as expired whether they need to be refreshed or not.
Depending on how the website is setup, this would be a very beneficial feature that would require a lot less system resources than the current implementation of crawling everything that has expired. In this scenario, I save a node that has three terms and the associated pages are flushed. All that needs to be crawled is the node page itself, the three term pages and the frontpage (if the node was promoted). If this was done immediately after the save, it would ensure that the pages are cached and ready for the next visitor while only consuming minimal resources.
And, if this could be configured to run in tandem with the expiration method, it would be ideal for sites that are regularly updated. I could set the crawler to hit expired pages i.e. once a day or once a week, and that would take care of any dynamic stuff in blocks etc that have content (which isn't so important to keep fresh) on pages that weren't flushed after saving a node.
Comments
Comment #1
LetUsBePrecise commentedI've same requirement. Wish one of drupal Guru can assist here. Thanks.
Comment #2
vacilando commentedIn Drupal 7, this can be achieved using the Recacher module.
Comment #3
c-logemannThe functionality of entity operations is addressed for new D8/9 Version in this Issue: #3292654: Boost Cache operations on entity CRUD
But I currently have no Idea about related pages where information from an entity like a node or term is shown beside the main view page of an entity. But maybe someone else have an idea. So I change the title and set the Version. But in any case this is not related to cron if there is a wish to react immediately.
Comment #4
c-logemannComment #5
c-logemann