- changed status to on hold
- what did you do just before that?
- did you get any javascript error?
- is it the first time it did this?
- if you click on another menu item, do the Login and Register button disappear?
- what if you reload the page?
Will provide more details on request
My guess is that when you get a timeout from login it adds these buttons but don't really logs you off.
Logging in again fix the issue
I will wait some time with the tab open and check what happens.
If it's a "you are logged out, but some parts of the menu didn't update" issue, then next time it happens please try to do any action which is login-based, such as creating a player, or viewing your home.
I'm investigating.
You may just want to wait until I gather more information...
How long should I wait until I get automatically logged out?
I can also experiment logging out manually if that would be useful.
Unfortunately, I have no idea right now, since there also are bugs regarding unexpected log-outs.
Doing it manually won't help much for now, because we aren't sure that is the cause.
We'll just wait and see…
Nothing happened after 1+ hours (I mean, the bug is not happening). I tried closing the browser and reopening it. Still not reoccurring.
The 2 cookies I see are set to expire in 1 and 2 months (probably from my first login). So probably it's the server session that expire, not the cookies.
Will wait to see what happens.
Still logged in.
Yeah, don't hold your breath, I guess it might take a few days before logging you out, unless that bug has actually been solved, of course.
Meanwhile I'll try to investigate through other means 🔧
Ok: as you suggested earlier, I tried to logout in another tab, and see what happened in the current one, and the behaviour was similar to what you describe.
However, we still aren't sure that this is what happened to you: next time it happens try to: * click "Home": do you see your actual home, or the generic unlogged one? * do any "logged" action, such as create a player
It's highly likely that the cause was the one you guessed, so for now we'll consider this to be fixed.
In case something new happens, please to re-open this issue.
Created [256]⦿ for user:7[BitJockey], with comment [Issue#6].