Bug #89285
closedTYPO3 regenerates cached page every page reload for specific TypoScript
0%
Description
To reproduce this error, please do these steps:
1) Setup a new "Root Page" with this TypoScript:
TS Constants:
aaaa = 222222 [globalVar = GP:L = 2] aaaa = 111111 [global]
TS Setup:
[globalVar = TSFE:id = {$aaaa}] [global] page = PAGE page.1 = TEXT page.1.value = {$aaaa} page.2 = TEXT page.2.value = cachetest
2) Create two new "Website Language" records
3) Create a new page and translate it into these two alternative languages
4) Flush all caches
5) Logout from TYPO3 BE
6) Open page in first language in your browser (e.g. domain.local/?id=1&L=1) => TYPO3 generates cache for this page
7) Reload this page => TYPO3 serves page from cache
8) Open page in second language in your browser (e.g. domain.local/?id=1&L=2) => TYPO3 generates cache for this page
9) Reload this page several times => TYPO3 generates the page cache every reload!!
10) Look in your database in table cf_cache_pages, there should be two entries. The first entry has ID 1, the second entry has an ID > 2 (this depends on how often you had reloaded the page with second language).
Error occures in TYPO3 8.7.27
Tested with Ubuntu / Vagrant Box / PHP 7.1 / MySQL 5.6
Tested with Windows 7 / MAMP / PHP 7.2 / MySQL 5.7
Updated by Sven Burkert about 5 years ago
- TYPO3 Version changed from 8 to 9
This error also occures in TYPO3 9.5.9!
Could someone please grant me rights to edit the issue description?
Updated by Christian Eßl about 5 years ago
- Related to Bug #23736: Condition with globalVar TSFE does not care about page language overlay added
Updated by Christian Kuhn about 2 years ago
- Related to Feature #97816: New TypoScript parser added
Updated by Christian Kuhn about 2 years ago
- Status changed from New to Closed
The constant and condition to page cache logic got a major overhaul is v12. In case this issue still existed before v12, it has been resolved now.
Please re-open in case you think we missed something.
Updated by Sven Burkert about 2 years ago
Ok :) Reading this ticket again, 3 years later, I guess it's the missing cHash why domain.local/?id=1&L=2 isn't cached.
But on the other side, domain.local/?id=1&L=1 is cached...!?