Currently the module clears caches for all displays based on the content type, so updating one node will clear the caches for all nodes of that type.

What would be better would be to properly track the entity type, ID and revision ID in the cache ID, then use them to clear the cache records. This would also make the module simpler and would remove the need for the custom table.

Comments

DamienMcKenna’s picture

DamienMcKenna
Location NH, USA
CreditAttribution: DamienMcKenna commented
Priority: Major » Critical

Bumping the priority of this because it's such a fundamental problem.

cthos’s picture

cthos CreditAttribution: cthos commented

I'm not sure I follow exactly what you're thinking of here.

My use case, at least, is I have a pane which is listing out a series of Article nodes, and I want that panel pane's cache to be cleared out when a new article is created or an article is updated.

I'm not sure how you would accomplish clearing out a bunch of disparate pane caches which might need to have new content would work in that case. Could you elaborate?

DamienMcKenna’s picture

DamienMcKenna
Location NH, USA
CreditAttribution: DamienMcKenna commented
Priority: Critical » Normal

Reducing the priority of this as it's not a fundamental problem, it's a feature request.

kopeboy’s picture

kopeboy CreditAttribution: kopeboy commented
Priority: Normal » Major

A very important feature request!

I think this should be written on the module page: "use this module to refresh a panel whenever any node of the designated type gets created/updated"

Of course I came here like Damien to have a panel flush based on the singular node being updated, not any node!

To cthos: many site builders now use Panels to override SINGLE node pages (which ALSO may contain Views' listings.. like related nodes).

Since View Content Cache module has the same behaviour, and if you show a list of entities in a panel you are almost certainly incorporating a View already, this module is almost useless now (hence the low usage).