TYPO3 Core

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

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?

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 ;-) )