- 🇺🇸United States sclsweb
I arrived at this issue with a very similar use case to #5 -- a small, low-traffic site with a view displaying a carousel of image fields drawn from 3 content types - events (with a date field that needs to be examined at midnight every night to flush past events out of the view), articles, and slides (which are supposed to stay until removed manually by un-promoting or unpublishing them).
I have the custom cache tag to remove events from the view when their date passes. The problem is that with the custom tag alone, new article & slide content isn't being added to the view. New events are added immediately for some reason(?), but new articles/slides aren't added until the cache is cleared. Presumably the view also needs whatever original tags a simple view of content provides.
So, the suggestion in #2 to display the default cache tags in the description would help my use case (because whatever they were, I need to add them back to my view in addition to my time-based custom tag). (Node_list is probably the culprit, but if there is anything more complicated, it would help to have a list of the tags that would have been there before the custom tag was added.)
- 🇨🇭Switzerland berdir Switzerland
You can just manually add node_list for your view, or node_list:article and node_list:slide for your specific node types. Again, this is by design.
If you don't care about invalidating too much, you can also just invalidate node_list and not use this cache plugin at all as mentioned in #6.
- 🇨🇭Switzerland berdir Switzerland
And you only need to worry about additional cache tags other than node_list if you have relationships to another entity type and changes there could also affect the view.