Bug #15835
closedPidInRootline malfunction
0%
Description
PidInRootline seems to conflict with caching under certain conditions.
When this happens, PidInRootline conditions are NEVER met, even when th current UID is clearly in the Rootline.
The attached db dump reproduces the problem reliably.
Take these steps to reproduce the problem:
- Install a virgin RC1 including Dummy.tgz.
- Load the attached SQL file into a free db and set localconf.php to use this db.
- Open BE (user: admin, pwd: admin) and clear the FE cache.
- Open FE, click under "Menu" on "Category1", then on "Page 1"
- You should see the correct PidInRootline result under topic "Conditions"
- Now click "Page 1" again. The page is reloaded and the PidInRootline output vanishes (!). The same can be done with Page 2 & 3: First click gives the correct PidInRootline output, second click makes it vanish.
- To show the correct condition outputs again, clear the FE cache from the BE.
As discussed in typo3.dev,
Thread "RC1-BUG?! PidInRootline malfunction under certain conditions"
started on March 15th 2006
System:
WinXP and Win2003
Apache2
PHP4.4
(issue imported from #M2888)
Files
Updated by J¶rg Wagner over 18 years ago
Strange detail:
If you uncomment the four lines in TS setup that display [PIDinRootline = 1], then the problem does NOT occur!
Updated by Michael Stucki over 18 years ago
FYI: We decided to just revert the new feature and look at it again after 4.0