[TYPO3-core] RFC: #9599: [felogin] Enable Caching "USER" instead of "USER_INT"

[Michael Stucki]

Steffen Kamper schrieb:
>>> For me the whole USER stuff makes no sense. The only point in having a
>>> form cached is when the form is not on its "landing page", ie when you
>>> have a small "login box" on every page.
>>
>> Exactly. So if you have a login box included in the navigation, you'll 
>> end up with at least one USER_INT object on every page.
> 
> why not simply the old way, adding
> <input type="hidden" name="no_cache" value="1" />
> 
> then the object can be USER without any problems.

Because it is the wrong attempt. This will work fine without using 
no_cache, so let's avoid it please.

May someone explain me the problem that Masi mentioned, please? I can 
have a look at it, since I have already quite some experience with 
switched USER/USER_INT objects.

- michael
-- 
Use a newsreader! Check out
http://typo3.org/community/mailing-lists/use-a-news-reader/