Hi there, I've playing with the module, but I'm missing something: shouldn't the cache invalidation happen as soon as possible?

Consider a Drupal 8 website (with purge and http purger installed and configured), served by a reverse proxy server like Varnish with xkey mod.

In the current default setup of this module, when a business user/editor creates a new node, she needs to wait for either
a) page expired in Varnish because of max-age
b) cron runs (default is 3hrs), and purges Varnish with the tags

However, IMHO these options are far from ideal. I guess one could write a hook or configure a rule, to run the cron hook of this module, but shouldn't behavior be a default? And if not, what is the recommended way of dealing with this?

Thank you very much in advance,

Comments

mariano.barcia created an issue. See original summary.

davidwbarratt’s picture

davidwbarratt CreditAttribution: davidwbarratt at Golf Channel commented

I believe if you create/enable the "Late Runtime Processor" it should execute the purge on page load which is what you are looking for.

mariano.barcia’s picture

mariano.barcia CreditAttribution: mariano.barcia at ASM Web Services S.L. commented

Hi David thank you very much, I've enabled the module and it seems to provide what I'm looking for.

However, I've yet to make it work, so I'm still testing. Supossing it works as intended, maybe adding it to the docs would be a good idea? Because "Late runtime processor" does not give an obvious idea of what the module actually provides...

MiSc’s picture

MiSc CreditAttribution: MiSc at Wunder commented
Status: Active » Closed (works as designed)

This seems to be fixed, so closing.

mariano.barcia’s picture

mariano.barcia CreditAttribution: mariano.barcia at ASM Web Services S.L. commented

Just to confirm that late runtime processor module does the trick. Thank you!