Category Page Cache not invalidated when a product is modified.

[siu00adg]

Hi,

Is there a way to automatically invalidated the varnish cache of a category page when a product within that page is modified (e.g. set to out of stock, etc.)?

Even better than that... is there a way to automatically rebuild the varnish cache for products and category pages when products are modified?

I think if the first is possible then the 2nd should be easy enough using the following method:

http://nwlinux.com/preload-varnish-cache/

Many thanks,

Alex.

[aheadley]

Is there a way to automatically invalidated the varnish cache of a category page when a product within that page is modified (e.g. set to out of stock, etc.)?

No, see issue #78 .

Even better than that... is there a way to automatically rebuild the varnish cache for products and category pages when products are modified?

For categories containing a modified product: no, same issue as above. For products, the product page will be automatically flushed on save. Additionally, if the built-in crawler is enabled it should automatically re-crawl the modified product product page (within about 5 minutes).

[siu00adg]

Makes sense, thanks!

[siu00adg]

One quick question, is there a way to keep the layered navigation warm (other than a wget / varnishreplay cronjob)? We use an ajax layered nav and the ajax requests are cached, but looking at your code turpentine seems to only keep categories, products and cms pages warm.

Many thanks,

Alex.

[aheadley]

One quick question, is there a way to keep the layered navigation warm (other than a wget / varnishreplay cronjob)?

No, you'd need to write a script to do the cache warming yourself, or maybe find an extension that will do it for you.

[siu00adg]

No problem, I've got a few ideas, thanks for your help.

[livneb]

@siu00adg , can you share your ideas with the layered navigation warmer?