?
avatar widmann-it
widmann-it
18 Jul 2016

Since 3. 6 there are problems with the Login again.

Actual result

Action:
Users in the Frontend announcing and again Cancel, the user once more Announce and there comes the announcement "The inquiry was rejected, because the Sicherheitstoken is invalid. Please, update the side and then try it once more. " earlier it was thus one with F5 a de side new store was able, now this is not any more Mglich, moreover one must close the browser or extinguish the Cachespeicher of the browser.

System information (as much as possible)

Linux 2.6.32-042stab113.11 #1 SMP Fri Dec 18 17:32:04 MSK 2015 x86_64
Datenbankversion 5.5.49-0ubuntu0.12.04.1
Datenbankzeichensatz utf8_general_ci
Datenbankverbindungszeichensatz utf8mb4_general_ci
PHP-Version 7.0.8
Webserver Apache
PHP-Interface für den Webserver cgi-fcgi
Joomla!-Version Joomla! 3.6.0 Stable [ Noether ] 12-July-2016 21:14 GMT
Joomla!-Plattform-Version Joomla Platform 13.1.0 Stable [ Curiosity ] 24-Apr-2013 00:00 GMT
Browsererkennung Mozilla/5.0 (Windows NT 10.0; WOW64; rv:47.0) Gecko/20100101 Firefox/47.0

Additional comments

avatar widmann-it widmann-it - open - 18 Jul 2016
avatar bertmert
bertmert - comment - 18 Jul 2016

Joomla 3.6.0
Confirmed.
Frontend. Logged in as SuperUser via login module. Logged out immediately without further actions.
Tried to log in again

Warning
Your session has expired. Please log in again.

Tried to log in again > success.

avatar sovainfo
sovainfo - comment - 18 Jul 2016

Can't reproduce. Suggest to check other tabs. After the refresh it is possible to login again. No need for closing browser.

Note: Not using any browser caching other than from the browser itself. Not using any server caching!

avatar andrepereiradasilva
andrepereiradasilva - comment - 18 Jul 2016

Frontend. Logged in as SuperUser via login module. Logged out immediately without further actions.
Tried to log in again
Warning
Your session has expired. Please log in again.
Tried to log in again > success.

Sorry, not confirmed in latest staging.

avatar infograf768
infograf768 - comment - 18 Jul 2016

Please test using staging as there was an issue with logout, now solved in staging.

avatar bertmert
bertmert - comment - 18 Jul 2016

Please test using staging as there was an issue with logout, now solved in staging.

Solves this issue here, too.

avatar infograf768
infograf768 - comment - 19 Jul 2016

@widmann-it
Can you confirm so that we close this Issue?

avatar widmann-it
widmann-it - comment - 26 Jul 2016

Hello, can continue to duplicate the problem. It does not matter which browser (Firefox, Chrome, IE) is used. Once the user wants to log in and log out again he gets the message with the session ID. The problem bewteht not only with the 3.6 I am already stumbled several times over. Only this time, it is so that the system can be used not at all more. And the detour via the reload of the browser can indeed be no solution.

avatar brianteeman
brianteeman - comment - 28 Jul 2016

@widmann-it did you test with the latest staging as requested?


This comment was created with the J!Tracker Application at issues.joomla.org/joomla-cms/11169.

avatar widmann-it
widmann-it - comment - 3 Aug 2016

Yes, is not work, when the Systemcache is the same problem as before

avatar widmann-it
widmann-it - comment - 3 Aug 2016

Testet by 3.6.1 RC2

avatar widmann-it
widmann-it - comment - 4 Aug 2016

Testet by 3.6.1
Once the cache function is enabled, the message comes with the token
message.

avatar brianteeman
brianteeman - comment - 4 Aug 2016

@widmann-it can you please confirm if you can replicate this with a clean install of joomla with no extensions and a default template

avatar brianteeman brianteeman - change - 4 Aug 2016
The description was changed
avatar brianteeman brianteeman - edited - 4 Aug 2016
avatar falzueta
falzueta - comment - 4 Aug 2016

Confirmed in 3.6.0
Solved with 3.6.1 upgrade


This comment was created with the J!Tracker Application at issues.joomla.org/joomla-cms/11169.

avatar brianteeman brianteeman - change - 5 Aug 2016
The description was changed
Status New Information Required
avatar brianteeman brianteeman - change - 5 Aug 2016
The description was changed
avatar brianteeman
brianteeman - comment - 5 Aug 2016

I am closing this for the same reason as #11307


This comment was created with the J!Tracker Application at issues.joomla.org/joomla-cms/11169.

avatar brianteeman brianteeman - change - 5 Aug 2016
Status Information Required Closed
Closed_Date 0000-00-00 00:00:00 2016-08-05 15:31:35
Closed_By brianteeman
avatar brianteeman brianteeman - close - 5 Aug 2016

Add a Comment

Login with GitHub to post a comment