[TYPO3-dev] RC1-BUG?! PidInRootline malfunction under certain conditions

[Joerg Wagner]

Hi all,

this is just a preemtive strike in case anybody else gets into similar 
trouble.

I experiences strange effects with TS conditions using PIDinRootline.
I tried to isolate and boil down the problem to give you a more accurate 
description than the one that will follow here, but I failed so far.
So here I go, hoping that me or somebody else will soon find a way to more 
easily reproduce this problem.

The effect is that certain TS-conditions of the form
    [PIDinRootline = 25]
    ...
    [global]
are ignored although the given UID is clearly in the rootline.
Even a debug output like
    page.10 = TEXT
    page.10.data = debug:rootLine
shows that page 25 (in my case) is in the rootline, but the condition fails 
nevertheless.
If this happens, it happens for many UIDs on the same level as page 25, e.g. 
all the neighbours of page 25 and all their child pages too.

The effect is triggered by a strange procedure:
I have to login as a frontend user and logout again. After that the 
conditions fail. If I clear the FE cache the malfunction is corrected.

Another strange detail:
If I use a condition that checks for the start page of my page tree (in my 
case it has UID=3) then the malfunction does not occur!
So if I put this emtpy (!) condition into the TS...
    [PIDinRootline = 3]
    [global]
then all other PIDinRootline conditions work flawlessly.

Ok. I will try to dig deeper into this and will report any findings.
If any of you finds something similar or complementary, please tell me.
I do not want to post a bug report right now because so far the effects are 
so weird and so hard to reproduce that I doubt it will help anybody.

--
Jörg Wagner
DigiLog multimedia