Bug #87962
closedIncorrect cache lifetime for MetaTag Cache
0%
Description
Sometimes the cache lifetime of meta tags is still not the same as the cache-time of the page.
See the attached Screenshot which shows the cache_pages_tags joined to the cache_pages tables. The page with uid 1 has a cache lifetime of 15 Minutes. Still the html5 metatags are cached longer than the rest of the page. (1 day)
I am not sure how this happened. #86234 introduced the lifetime, but we still sometimes get the error that meta-viewport tag is not available on the page. That's why we decreased the cache lifetime to 15 minutes. But today it happened again and when checking, we noticed that the cache entry for the html5 metatags only was <meta name="generator" content="TYPO3 CMS"> and the viewport metatag was missing.
We set the meta viewport with the following TypoScript:
page.meta.viewport = width=device-width,initial-scale=1
We have USER_INT objects on the page, multiple page-types and additional cache tags (tx_vierwdcanzler_domain_model_project), but as far as I can see those were not responsible for the problem. It's really hard to debug, because it only happens were infrequently and once the cache is cleared, everything works fine.
Files
Updated by Robert Vock over 5 years ago
- Related to Bug #86234: Missing Meta Tags on Pages with *_INT objects added
Updated by Christian Heindl over 5 years ago
- Priority changed from Should have to Must have
- Is Regression set to Yes
Seems that we are experiencing the same problem. It also occurs only on very rare occasions.
Updated by Richard Haeser over 5 years ago
- Related to Bug #88165: MetaTags suddenly lost added
Updated by Helmut Hummel over 5 years ago
- Related to Bug #88179: Meta tags and page title are unnecessarily cached in separate cache entries added
Updated by Helmut Hummel over 5 years ago
Would be solved with #88179 as this proposes to drop this separate cache entirely
Updated by Richard Haeser over 5 years ago
- Status changed from New to Resolved
With the release of TYPO3 v9.5.8, this issue is solved.