Bug #26161
closedcache_treelist is out of date when using starttime
0%
Description
Files
Updated by Daniel Siepmann about 11 years ago
We have same issue in 4.7.15.
Here is our setup:
- [1] Folder
-- [2] Page 1 [Start Monday End Tuesday]
-- [3] Page 2 [Start Tuesday End Wednesday]
-- [4] Page 3 [Start Wednesday End Thursday]
-- ...
Our TypoScript is the following:
lib.example < styles.content.get lib.example.select { where = colPos=1 pidInList = 1 recursive = 3 }
On Monday the first entry will be inserted into the table containing only 1 and 2.
On Tuesday the same entry will be fetched, but Page 2 is no more accessible. But Page 2 is which is not in the cache entry.
If you don't clear the cache it will not work.
I attached our own working patch for 4.7.15.
It will insert the expired time for the first possible situation. So if we have Tuesday it will no longer fetch the cached entry, but will create a new one and remove the old one.
Another problem was that the simulated time was not used, so you could not test this scenario using the admin panel.
Updated by Wouter Wolters about 11 years ago
- Is Regression set to No
Hi Daniel,
Can you push a patch for this to Gerrit?
For information about how to do this see: http://wiki.typo3.org/CWT
Greetz Wouter
Updated by Mathias Schreiber almost 10 years ago
- Target version set to 7.2 (Frontend)
Updated by Benni Mack over 9 years ago
- Target version changed from 7.2 (Frontend) to 7.4 (Backend)
Updated by Susanne Moog over 9 years ago
- Target version changed from 7.4 (Backend) to 7.5
Updated by Benni Mack about 9 years ago
- Target version changed from 7.5 to 7 LTS
Updated by Mathias Schreiber about 9 years ago
- Target version changed from 7 LTS to 8 LTS
Updated by Benni Mack over 7 years ago
- Target version changed from 8 LTS to Candidate for patchlevel
Updated by ondro no-lastname-given about 6 years ago
D. Pöpping wrote:
When using a startdate for a page the tslib_cObj->getTreeList will never get this page in its results until "clear all cache" is used in order to clear the cache table for the tree list results.
(see Feature #18852 and related Bug #22412)
Can confirm same behaviour with Typo3 8.7.19
Updated by Philipp Thiele almost 4 years ago
- TYPO3 Version changed from 4.4 to 10
- PHP Version changed from 5.3 to 7.2
Can confirm this issue with TYPO3 Version 10.4.10
Updated by Christian Kuhn 9 months ago
- Related to Bug #103139: Missing expires in cache_treelist leads to duplicate key value violates unique constraint in the database added
Updated by Christian Kuhn 9 months ago
- Status changed from New to Resolved
This was finally solved by avoiding cache_treelist since v12 with #103139.