#4806 (ok 4.4) Unable to work with two different databases in two tabs
Hello,
I just updated my phpMyAdmin from old 3.x version and found a very annoying bug. I try to work with two databases in two diffent tabs. But every action made in one tab destroys sessions in both tabs!
Example. I open first database, log in and do something, that's good. Next I open the second tab and switch to another database in left pane, log in to the second DB and see the start page. From this point parallel work is impossible. Trying to make something in first tab cause the "Session expired. Please log in" error and I have to log in to first DB again. But when I log in, the session in the second tab with second DB become invalid and trying to do anything case same error. Different tokens in the browser's url field dont have any value.
How to work? I think I will downgrade to version 3.x again. First time I tried version 4.x I downgraded after 15 minutes... Now I tried it for a week. Progress...
Hi,
I think this is a duplicate of https://sourceforge.net/p/phpmyadmin/feature-requests/1561/ which was partially fixed by https://github.com/phpmyadmin/phpmyadmin/pull/1563 .
You could try the current master to see if that fixes or or wait for the next release. I imagine Madhura will comment here if he has anything to add about this as well.
Regards
Yes, seems it is a duplicate. Will try current master. Thanks.
Addition: I mean two browser tabs and selecting different DB servers, not databases from one server.
We figured that out :)
Yeah, sorry that was clear in your initial post and I didn't really respond well with that in mind. The two items are related but not directly duplicates and I should have phrased my response to reflect that. I do believe that the intended fix for the other ticket item will also fix this, though I'm not completely clear from reading the discussion in the pull request whether your issue is expected to be fixed yet. I'll certainly leave this ticket open for now until we have more answers about it :)
The current fix provide a workaround for the problem. It fails to support the exact scenario described in https://sourceforge.net/p/phpmyadmin/feature-requests/1561/, but should be good enough until we figure out a full fix.
I think it makes sense to port the fix to 4.4 branch, so it will be part of upcoming 4.4.0 release. Will do that soon.
The current master is working good, problem is fixed. Thank you.
Great, I'm delighted. Thanks for reporting back!
Fix ported to QA_4_4 branch https://github.com/phpmyadmin/phpmyadmin/commit/9f1f0e6bc1e4161e048628a3b177d97faac0254d