- Issue created by @hkirsman
- 🇳🇿New Zealand quietone
Changes are made on on 11.x (our main development branch) first, and are then back ported as needed according to the Core change policies →
- 🇬🇧United Kingdom catch
The use case is solvable via contrib with https://www.drupal.org/project/views_custom_cache_tag →
Seems worth looking into whether we can conditionally add cache tags based on argument validation.
- 🇪🇪Estonia hkirsman
I forgot to mention that to fix the issue I used path rule on the block itself so it would be rendered on the correct pages.
Not sure if cache tags would work? So the content i was listing was fix content type. I understand I could now add hook to invalidate for example new custom tag list_fix, I would then add it to the view. It would still invalidate this on all the pages.
- 🇬🇧United Kingdom catch
OK that makes sense. I think this is more of a task than a bug, but it sounds like something that's worth a try.