The 2026 Drupal Business Survey is open. Your response will help shape the future of the Drupal business ecosystem.There are a number of issues associated with Metatag's cache and there seems little in the way of benefit. Metatags are aimed at anonymous bot visitors so for most use cases, Drupal's page cache does the job of providing a cache layer for its output.
Dropping the cache would reduce the size and complexity of the module significantly and remove a major source of bugs and confusion for users.
| Comment | File | Size | Author |
|---|---|---|---|
| #5 | metatag-n2474427-5.patch | 2.18 KB | damienmckenna |
Comments
Comment #1
damienmckennaI think it's beneficial to keep the general configuration in cache, but maybe disabling the output cache might help? This could be an option on the settings page.
Comment #2
alfaguru commentedDamien, yes, my concerns are with the output cache, not with configuration. I am agnostic about the latter as it has not caused me any problems to date.
Comment #3
damienmckennaComment #4
thomwilhelm commented+1 I'd also be keen to see this as an option in metatag, have run into issues recently with output keys over 128 causing conflict, all our pages are cached by varnish so there isn't any reason to separately cache the generated metatags.
Comment #5
damienmckennaHow does this work for you? It adds an option to the Advanced Settings page called 'Cache meta tag output' that is enabled by default but which controls whether meta tag output for entities is cached.
Comment #6
damienmckennaCommitted.