When disconnect the login loops while all tabs opened are not closed

Hi,

I try to explain the problem in another way.

When you are working on a site as admin you have to open both admin back-end tab and front-end to view and modify documents and various elements.

If the session ends (any reason) you will have to login again.

The problem comes from the process when you login again with various situations.

In my current installation 4.6.5 (cannot upgrade for now : see note 1), I met a problem in reconnection.

Until I have not closed all tabs opened I cannot login again : the login page (the full page) after filling it and validated, loops and shows again the login page without error message.

The cases are multiple because :

1. you can try to login from a front-end page or back-end and the behavior is different.
2. you can get the login page

1. on one unique page (the one you are working on) when you are working on your browser
2. on several (sometimes all) pages if the browser restarts and try to load all pages previously opened. In this last case all pages will show the login page

In each different situation the behavior, with probably one unique problem, is different.
While is am writing this answer I made a test which another browser : Firefox.

I tried to open directly an admin session : url = https://<mysite>/admin

1. WP displays the login page : I failed to login and just met this loop which refuses the login and loops without any Error message (if you make an error you get two line of Error message)
2. After this I have launched the welcome page and from it using the lwa widget I have opened an admin session in back-end without problem

Another test :

1. First I open (Firefox) 2 front-end articles login from widget and open a back-end session as admin
2. I disconnect from one of the front-end : I get the login page which confirms “you have been disconnected”
3. I go to the first tab, previously logged in and reload it : I get a connected front-end page… no care of the previous message telling that you are disconnected.
4. The same from the back-end, I can go on working in admin session
5. Load a new front-end : idem connected

Conclusion :

1. The disconnection has not been taken in account
2. It is impossible to log again from the panel shown after this failed disconnection, I had to close the tab.
3. I fail to login directly on admin !!

So, my point of view, my current explanation after these last test, is that when such situations are met the last case (a login page which shows nothing and refuses to operate a login) on several tabs it becomes impossible to find a way to connect without closing everything.

I found just now to obvious problems :

1. When I have closed the session from the front-end page, even I got the message “disconnected” it was not true.
2. The disconnected message shows again the login panel which lets think that you can log again, it loops

I think that, because I test everything that I tell and new cases that I find while writing, I have found one of the problems (they are several, I do think so now) :

1. When you are locked on this loop, if you try to login with any wrong id and pswd you get the ERROR message and when you try again with the good ones you reach the success in login. Nevertheless this is wrong because you are already logged in. What happens if you log with valid ids different of the current not disconnected ? I have not tested this case yet

The fondamental problems is that :

1. When you disconnect from a tab you are not sure that you are disconnected for all your pages currently opened (front and back-end)
2. When you login successfully on one tab, pages which have failed to be loaded (automatically) previously cannot be reloaded.
3. When you have disconnected from a user you cannot use the current login form to log again fro the same user

I ignore if they can be interactions with lwa.

Best regards

Trebly
______________________________________________________________________________
note :
for now because
– of several plugins with no time to check them or which have no upgrade and uses obsolete instructions
– I have developped several plugins and forked others which are not distributed, and I have no time to package them and they are no more tested for 4.7

Hi,

I agree (as I suppose it in my first message).
I just comment here this behavior because for some users the login form lwa can fail too and they would not see immediately the reason.

I note that, I have not received any answer from the same subject opened in WP main forum (us and fr). Nobody seems concerned.

The main problem seems to be that, because the circumstances of the anomaly are multiple and cannot easily identified. What an admin can see is first something complex because the conditions of a login, when multiple tabs are opened and more front end and back end at same time, creates a great multiplicity of cases.

Practical cases found cannot be easily reproduced because of the difficulty to identify criteria and phenomenons. Any explanation is complex and circumstances cannot be reproduced.

Writing this tread I finally think that there are two problems :

1. The fact that an admin has been disconnected and try to reconnect immediately the login doesn’t fail but it is the submit form which fails, refusing to receive and check identical ids than previously. So, when there are several tabs opened you don’t understand at all what happens thinking that there is a login error…
   I could deal with this, which is not in relation with the management of multiple tabs, using this (this is a proof) :

1. Fill with wrong ids : you generates a login error
2. login now with rights ids : you are successful (this is the reason why when you can login with lwa from not logged page (previously loaded) your login is successful.
3. After a load failure in browser restoration process the login doesn’t allows the back load of the previous url, but after a forced login error, when you try a log with right ids you get back the right url loaded because before

• You have logged in a page but you are not logged in for any
• All back-end page must be loaded successfully (logged in individually) to login in front-end (it could check a cookie of any local storage – or use an Ajax request – from login data updated by the first new successful login to reload or load a back-end page or front-end document but it doesn’t)

1. While each admin pages have not been reloaded successfully using the previous described process you cannot anyway login for front-end as admin (probably for any other user) : you get an error)
2. When all back-end page have been re-loaded (admin) when you refresh or load a new front-end page you will get it as admin

Best regards

Trebly

Hi,

Again, I agree. I just report this here that I found about this subject, for several reasons :

1. to close the subject
2. to let here full information that I have built from what I have observed,
3. to explain to anybody who have same problem and first came here, to get easily here my conclusions before seeking to the huge WP forum to look further into the subject.

Best regards
Trebly

• This reply was modified 7 years ago by Trebly.

Hi,

I have submitted the problem in forum ”
Support » Fixing WordPress » Coherence problem between plugin lwa (login with ajax) and query-monitor and WP