New posts page broken
Re: New posts page broken
I encounter the same issue now and then.
Re: New posts page broken
Yeah, this is actually one of those bugs which we've encountered ourselves from time to time. There seems to be an issue with the forum software recognizing sessions. It's something we intend to look into!
Re: New posts page broken
Or maybe a cached page part is shown?mpowell wrote:There seems to be an issue with the forum software recognizing sessions.
Re: New posts page broken
It also happens to me from time to time (username invisible but "sign out" displayed – exactly as in the screenshot above). Today it took me 20 minutes trying to log in.
- I deleted the entire cache, so contrary to my expectation above, it cannot be a caching issue.
- I also deleted all cookies, that didn't help either.
Maybe the problem is criticker.com vs games.criticker.com and the sessions (cookies) cannot be cross-referenced.
- I deleted the entire cache, so contrary to my expectation above, it cannot be a caching issue.
- I also deleted all cookies, that didn't help either.
Maybe the problem is criticker.com vs games.criticker.com and the sessions (cookies) cannot be cross-referenced.
Re: New posts page broken
Sorry for asking, but do you make any progress on this?
It now happens to me every time I try to login.
It now happens to me every time I try to login.
Re: New posts page broken
No, we haven't really started yet on this one, but it is on our list of bugs we intend to get to soon.
Re: New posts page broken
thank you
Re: New posts page broken
Has anyone been able to reliably reproduce this issue, yet? I know it happens, because I've seen it myself, but not for a few weeks. And try as I might, I haven't been able reproduce it.
Re: New posts page broken
@ "reliable": Yes, happens every time I try to log in. No exceptions.
Maybe you cannot reproduce it, because your account renews the session too regularly.
Seeing that you are the developer, maybe your session never gets too old.
You could try this:
1. login with a test account
2. close browser without logging out
3. don't use this test account for, say, 3 days
4. log in again
Or else it might be browser-specific. What browsers do you test on?
Maybe you cannot reproduce it, because your account renews the session too regularly.
Seeing that you are the developer, maybe your session never gets too old.
You could try this:
1. login with a test account
2. close browser without logging out
3. don't use this test account for, say, 3 days
4. log in again
Or else it might be browser-specific. What browsers do you test on?