[TYPO3-project-4-3] [TYPO3-core] RFC Bug #10951, #9843: Hidden content elements displays in Module viewpage

[Niels Fröhling]

Niels Fröhling wrote:
> Niels Fröhling wrote:
> 
>> Solution:
>> Removed the interpretation of flags which were used to indicate to 
>> display visual information from the configuration of 
>> versioningPreview, as that's wrong. I tested, no side-effects except 
>> having a working Web->View. Obviously I can have missed something.
> 
>  I just found out that when a BE-user is logged in and seeing the 
> web-page, despite having a regular FE-user logged in, MUST have 
> "versioningPreview" set, otherwise no FE-user protected element appears!
 >
>  That's pretty much a conceptual mess, I'm going to dig deeper. The 
> given patch should be fine, I'm just going to hunt for the piece of code 
> that think that you must have "versioningPreview" enabled to see the 
> live-workspace when you are in as a BE-user, and even kills off your 
> status as a logged in FE-user ...

  Reason is Bug #11194, you can't turn off or switch the fe-group for simulation 
in Web->View, in consequence you're not going to see any elements visible to 
other fe-groups.

  Bug 11194 shines here with all it's nasty glory, even turning off the 
admin-Panel once you enter a non-protected page inside a extentToSubPages 
protected tree and maintaining the completely wrong fe-group persistantly ...

  I collect all detailed fail-cases in the corresponding Bug-Report #11194, and 
well I just started hammering.

  I'm sorry for the noise (maybe I should open a 11194.blogspot.com ;^), but 
this a real real bad major bug, and intersects with quite some other bad bugs. I 
have the time to attend this in this moment, and I'd like you to be up-to-date 
about it, so you can jump in at any moment and say "ah, great here I just saw 
how to fix it" or "man you missed this relationship there and it won't work".

  All right, IMHO the patch #10951 is fine.

  Ah, one note, I often get cache-interference, it seem that in extendTo-cases 
even protected pages and content ends up in the general cache and can be 
accessed without being FE- or BE-loggedin. I can't determine the exact 
conditions yet, maybe after a hundred times going over this setup over and over 
again, maybe I get enlightened and write an exact bug-report. I just mention it 
because of the "hey I know what it is" possibility.

  Ciao
	Niels