Feature #14496
closed
time dependent displaying of non cached pages/contents
0%
Description
time dependent displaying of non cached pages/contents is not possible.
If you want to display time dependent pages the page mustn't be cached. this does not make sense since we have the flag "cache expires"/cache_timeout in the pages-table.
my suggestion: as soon as any contentelement on a page has a time dependend setting the cache_timeout should be set/overriden to this datetime.
see the mailinglist:
http://typo3.org/documentation/mailing-lists/english-main-list-archive/thread/110102628/?tx_maillisttofaq_pi1%5Bsword%5D=Page%20Start%2FStop&tx_maillisttofaq_pi1%5Banswered_only%5D=0&tx_maillisttofaq_pi1%5Bmode%5D=1
(issue imported from #M683)
Updated by Ingmar Schlecht over 19 years ago
Hi Dominic,
I didn't manage to reproduce this on a 3.8-dev installation..
Could you please write down the steps in an example?
merci vielmals in advance,
Ingmar
Updated by Wolfgang Klinger over 19 years ago
The problem can be solved as follows:
in tslib/class.tslib_fe.php
method realPageCacheContent
after setting the "timeOutTime" we have to check if there's any content on the current page that has a starttime or endtime timestamp lower than the calculated "timeOutTime"... if so, we use this timestamp
Remaining problem:
Can easily be solved for tt_content and/or any other "known" table, but what about records from custom USER plugins? Any ideas?
Updated by Dominic Brander over 19 years ago
Hi ingmar
do you need more precise information or is the bugnote from stfl_wolfgang enough?
a few more information/clarification:
when you use the standard datefields in T3 you will almost never realise the problem since most of the people have set the config.clearCacheAtMidnight=1 This period is ok for most cases since the clearing of the page and the displaying/hiding of the page are the same times: 0:00
but when you install the date2datetime extension you will see that the clearing of the cache at midnight is not sufficient. since the cache-clearing period is larger than the datetime a page/contentelement should be "re-build/re-cached".
an example:
http://www.unia.ch/index.php?id=798
you'll see what I mean... (hopefully nobody clears the cache ;-) )
Updated by Alexander Opitz almost 11 years ago
- Status changed from Accepted to Needs Feedback
- Target version deleted (
0) - PHP Version deleted (
4)
Hi,
as this issue is very old. Is this feature missing in newer versions of TYPO3 CMS (4.5 or 6.1)?
IMHO this was implemented in 4.6/4.7
Updated by Alexander Opitz over 10 years ago
- Status changed from Needs Feedback to Closed
No feedback within the last 90 days => closing this ticket.
If you think that this is the wrong decision or experience this issue again, then please write to the mailing list typo3.teams.bugs with issue number and an explanation or open a new ticket and add a relation to this ticket number.