[TYPO3-dev] FE-user becomes someone else
Bart Laarhoven - Ostendo
bart at ostendo.nl
Tue Sep 8 10:42:47 CEST 2009
Thanks. While debugging this problem, I've been looking in the cache_pages
table for something with "Logout" in it. (A button "Logout" is displayed
when a user is logged in)
I found a few records, but they all had "<!--###USERNAME###-->" in the place
where the username should be...
Bart
-----Original Message-----
From: typo3-dev-bounces at lists.netfielders.de
[mailto:typo3-dev-bounces at lists.netfielders.de] On Behalf Of Mathias
Schreiber [wmdb >]
Sent: 2009-09-08 10:31
To: typo3-dev at lists.netfielders.de
Subject: Re: [TYPO3-dev] FE-user becomes someone else
Bart Laarhoven - Ostendo schrieb:
> Thanks. I'm just using the default "login" tt_content element to display
the
> username. It appears that the tt_content.login TS element is indeed a COA
> and not a COA_INT.
> Should that fix it? Seems weird to me that it isn't a COA_INT by default
> then..
>
> Bart
>
> PS. Sorry, I can't reproduce it so I guess I'm a little skeptical before I
> accept it as a solution.. ;)
Could also be a proxy in between.
Had this once.
But mostly it looks like a TYPO3 caching issue.
Imagine this scenario:
User "bart" in group A logs in.
TYPO3 generates the pagecontent "Hello Bart" and saves this to the cache.
User "mathias" also in group A logs in.
TYPO3 sees "oh great, I got that in cache already" and delivers cache
(from bart)
If felogin does not happen to be a COA_INT this just seems like a small
bug to me.
Use the Typoscript object browser and override the COA to an COA_INT.
If this doens't fix the issue, you can simply remove that line again.
Only trade-off:
You lose your caches so far - if this is no problem, go ahead.
cheers
Mathias
--
TYPO3 certified interogator
T3DD09 Entertainer
_______________________________________________
TYPO3-dev mailing list
TYPO3-dev at lists.netfielders.de
http://lists.netfielders.de/cgi-bin/mailman/listinfo/typo3-dev
More information about the TYPO3-dev
mailing list