Bug #19879
closed
after upgrade from 4.1.7 to 4.1.8 feusers and beusers have to clear there cookie cache before they can login
Added by Sebastian Enders almost 16 years ago.
Updated about 6 years ago.
Description
We upgraded several sites to the new versions 4.1.8 and 4.2.4
And we habe the problem that after the upgrade the frontend users and backend users cannot login. But if they clear all cookies they can login.
But you can not say hunderts of users, please clear your cookie before!
Help wanted!!!
(issue imported from #M10216)
Files
will be fixed with a #19867 bugfix
I am sorry!
The bugfix of 0010205 doesn't help!
I have to switch back to 4.1.7! :-(
Still it is the same problem, so there is no need to reopen this issue. Please report to #19867 and especially try my latest patch (posted 10 minutes ago) to see if that works better...
- michael
We have also problems with the 4.1.8 Version of typo3
There are 3 cookies created with expire date of 2010?
e.g.
Name be_typo_user
Value 5b67a8fff6b747e5ef69a16cca059cca
Path /
Secure No
Expires Sat, 23 Jan 2010 09:52:47 GMT
also fe_typo_user and PHPSESSID
After I login in the BE and browse in the FE and logout in the BE those cookies still there. And if I now close all my browser windows and try to login with a new one those cookies with expire date of 2010 will cause that the login doesn't work.
I wonder why those cookies aren't set to expire on 'At End Of Session' instead of 1 Year later ?
How come your be_typo_user cookie is valid for 3 years? That can't be normal, please investigate the reason for this first.
I think you're right.
I also have yaml installed. I dropped the constant pageHeaderData declared at yaml's constants template and cleared the cache/cookies.
After doing that, the cookie's lifetime was set to "at the end of the session".
Yeah, just found out the same after doing some testing.
I fixed the cookie.js for us by not letting it touch ?e_typo_user and PHPSESSID "cookies".
I attached the fixed cookies.js here and close this report, since TYPO3 behaves perfectly right in this case.
I'm glad TYPO3 behave perfectly right and does not accept the faulty cookies,
Sorry for uploading the wrong file. Now I changed it with a version Albert van der Veen suggested. It only changes the efaSize cookie and leaves all others alone...
Leave it as resolved for the time beeing
- Status changed from Resolved to Closed
Also available in: Atom
PDF