• Forum Moderator applications are now open! If you're interested in joining an active team of moderators for one of the biggest Pokémon forums on the internet, click here for info.

Session data getting lost

*points to this thread* I wanna know if there's a major issue going on with this. If somebody gets frustrated and just papers over it once, we get no report. They see this thread, they mention it, we know it's a big issue.
 
I've been getting these "loss of session data" message quite a few times lately, myself, sometimes winding up having to hit "Save Page" about 3-4 times before my changes are actually saved.
 
That's odd. I thought the problem was solved after the update 2 weeks ago. Has it reemerged then?
 
I, too, experience this quite often. I'd say about a third to a fourth of the times I change the page.
If this helps, I don't think it happened to me during my first login. Only after I logged out and back in for the very first time, the problem started appearing.
 
I had this problem a couple of days ago, when I was writing a response to a thread. But it only happened one time.
 
It happens to me every so often, typically in the event of edits taking long periods of time. That said, it normally processes properly within a retry or two, and my changes aren't lost, so it doesn't strike me as overly onerous.
 
Session data being lost after, say, two or three hours is normal. Please specify the length of time between starting your edit and getting the error.

I've just fixed a minor configuration error which affected memcache efficiency. I estimate roughly 25% of users would have been affected, with symptoms including session loss.
 
Session data being lost after, say, two or three hours is normal. Please specify the length of time between starting your edit and getting the error.

I've just fixed a minor configuration error which affected memcache efficiency. I estimate roughly 25% of users would have been affected, with symptoms including session loss.
This seems to have fixed it for me.
 
Please note: The thread is from 17 years ago.
Please take the age of this thread into consideration in writing your reply. Depending on what exactly you wanted to say, you may want to consider if it would be better to post a new thread instead.
Back
Top Bottom