Bug #19089
closed
Login expired dialog shows up under Linux and FF3
0%
Description
This issue seems related to #0008336.
On various occasions, e.g. saving pages, template records, etc, a dialog would come up asking to re-login with typo3 because the session seems to have expired.
The dialog window however showed the user (admin) to be logged in correctly.
The patch from issue #0008336 was tried against the relating file in version 4.2.1 and it didn't need to be edited because the solution from 4.2.0 was found to be applied.
This rather annoying behavior was reproducable under OpenSuse 10.3 with Firefox 3.
Workaround: Hitting "Abort" did save the page.
(issue imported from #M8947)
Files
Updated by Sebastian Klapdor almost 16 years ago
Tested IE7 and FF3 under Windows environment and everything worked out o.k.
Updated by Oliver Hader almost 16 years ago
Maybe you have a beta release of FF3 installed on your OpenSuSE system?
The behaviour you mentioned could be caused by a JavaScript error in tbe_editor - did you get such JavaScript error messages?
Updated by Jack Skaba almost 16 years ago
please check if this is a duplicate of bug# 0008232 and bug# 0008570
Updated by Sebastian Klapdor almost 16 years ago
Hello Oliver,
over the weekend I used a windows operating system and didn't see a problem. This morning under Linux the error showed again. I use the following FF3 Version:
Mozilla/5.0 (X11; U; Linux i686; de; rv:1.9) Gecko/2008052912 Firefox/3.0
I did get JavaScript errors and uploaded a screenshot of the error messages.
Hi Jack, I can now confirm that it is a similar error, because the information (e.g. header info of translated pages) doesn't get saved in the backend and I get the "Login expired" dialog. The head tag appears empty every time I save the page. Header info however is still updated within the database and shows in the frontend / actual page. (www.toronado.de)
Updated by Dmitry Dulepov over 15 years ago
Sebastian, make sure it is not a duplicate of 8232!
Updated by Sebastian Klapdor over 15 years ago
After this error has not shown up for quite a while I am inclined to call it "resolved".
Updated by Christian Kuhn about 14 years ago
Resolved, no change required as requested by reporter.
Updated by 