Feature #19283
closedpage cache is not influenced by tt_content.starttime/endtime
0%
Description
The actual caching meachanism works like that:
- page is generated
- expiredate is calculated (by clearAtMidNight or page caching config,
usually set to generating time + one day)
- if a page is requested, TYPO3 checks wether the cache is expired or the
page starttime/endtime should take effect.
So an content element has no influence on caching time.
If a page is cached at 2pm (with 24hours cache-expire) and there is a
content element with an starttime at 3pm on that day, that content element
will be visible first at 2pm the next day (when the page cache expires).
As an proof of concept i wrote an extension:
http://forge.typo3.org/projects/show/extension-cacheexpire
With that extension the expire-timestamp of the pagecache will be calculated based on starttime/endtime of all content elements on that page. Deleted, hidden, starttime, endtime and group-permissions are respected.
For different tables then tt_content it is possible to use an hook. With that extension i provide an very simple class which hooks in and takes care of tt_news elements (if there is a plugin on that page).
I made an patch of that extension for integrating into the core.
(issue imported from #M9284)
Files