– the login cookie only gets set when you actually log in and expires a set time (say 30 days) after that timestamp, regardless of how often you visit during that time or even if you are visiting a that moment.
– or the session tracking (the bit that ties the login cookie to an actual login) is a bit screwy.
– or they are doing maintenance again and had to take the session database down.
Or some combination of those.
We have enough geeks here to sort this with a bit of coordination from the STW “web team” surely?
Well, as the system I logged into last night is already showing me as logged out, here’s the result of some cookie sniffing in case its helpful.
Ignoring what just look like ad cookies, while in a logged out state I have this:
wordpress_logged_044ac5fc50cc83ccdacd1d7b50e78053 for path /
wordpress_044ac5fc50cc83ccdacd1d7b50e78053 for paths / and /wp-content/plugins
premier_auth
The wordpress ones have a June 4 expiry and the premier_auth, June 1
After logging in, the same wordpress cookies are present with expiry updated to June 12. Was too dim to note down the cookie value before re-logging in.
So looks like a session tracking issue. I see the same thing across 3 different Windows systems I use, on different networks, all running Firefox. Which might sort of point to then possibility of issues of overlapping sessions on the different systems.