I thought this problem only applied to me since I didnt see many people complain about it until now. I’ve been having this problem for over a year on Chrome, not sure about the other browsers but going by the above posts, it’s not too different either.
Stay Free, SRK. If you had listened to me and bought a staging server (or created a fucking subdomain dev.shoryuken.com) a lot of these issues could have been resolved there before pushing it live. OR you could just install locally, edit/fix, and push builds to a site like http://www.beanstalkapp.com which lets you push git repo’s to a production server once they’re ready. After all of these months this site STILL isnt READY.
How can you have a session bug this bad and not address it? Especially by now? Idc what you say or how you berate me for this, but you are a noob Wizard. I build sites bigger/better than SRK in my sleep, i’ve given you free advice countless times only to be brushed off and treated like i dont know what im talking about (always gives me a good, hearty chuckle). This bug alone turned me from an active contributor to a lurker because of how frustrating this site has become to use.
(had to log in MORE THAN 15 times just to be able to post this)
You appear knowledgeable about the subject. Why do I have to try to log in multiple times just to get logged in?
I’m having the same problem. Having logged in via Facebook, every time I change page a white panel saying “Logging in…” comes up at the top and reloads the page about 3 times before finally letting me browse. Extremely annoying 
Just write a script.
Since you’re the one who had to log in more than 15 times I believe you’re the one that’s free.
nice one.
if they had spent the time to duplicate SRK and its database onto a staging server they could debug all of these issues before pushing them live. That way their users dont suffer as a result of their laziness/inability to create stable software/fix issues. Everytime they change, or try to fix something they’re doing it on THE VERSION OF SRK THAT YOU USE. lol nice job trying to defend them, but no matter what you say it doesnt change the fact that its completely stupid/irresponsible to do things that way.
to attempt to contribute to fixing the issue, im thinking that the bug stems from a session issue. I suspect that once the page refreshes after a login that the session is terminated/expiring as soon as the page FINISHES loading (or just before).