Ever since the upgrade (well, it seems that they coincide, anyway), I seem to occasionally get an "invalid session" error when posting a message. It doesn't happen all the time, but when it does happen, the only way to fix it is to click "log off"and then log on again, even closing the browser window and re-opening doesn't seem to work. I have flushed my cookies in case it's anything to do with that.
Is this happening to anyone else? Or am I just Jonah?
BTW: You're right about the color scheme, it has grown on me.
Brian.
I have gotten them both posting and replying to PMs. In my case simply backing out, then reclicking the link back into the thread or email worked, though that may have been coincidence.
I've had one of those as well in replying to a message.
In that case, I was able to back up and resubmit the post...but oddly enough, it posted the item twice.
It's happened to me once since the upgrade, during a normal post. As a result, I double-posted, tho I noticed it in time to delete the second post.
Hi there,
It hasn't happened to me at all, but I've been getting reports from individuals as well.
Best,
Ron
It hasn't happened to me either, but I have been noticing that I get session IDs in addition to cookies. (Crazy web talk. Ignore. What I mean is that I have a big-ass string up in my URL that starts with 'sid='.)
I've increased the length of sessions, in case the problem was that they were expiring in between clicking the 'Post a reply' button and finishing your post. Please report if this keeps happening.
Quote from: Clinton R. NixonI've increased the length of sessions, in case the problem was that they were expiring in between clicking the 'Post a reply' button and finishing your post.
Dang. Do you mean we're time-limited in how long it takes for us to write a reply? I'm in trouble....
--M. J. Young
I thinl Clinton's got it. I just had my first one and it occurred after I'd gone for a loooong time (couple of hours) between getting to the post page, and hitting submit. The first of these sorts of posts for me since the new look.
Mike
Mike,
I hope so - this release of the forum software is supposed to be a lot more stable.
M.J.,
The limit was four hours, and I increased it to 8, which is a crazy large amount of time. If you're taking longer than that, write it in Notepad.
Hmm. It wasn't nearly that long. Perhaps I had the old parameter from being logged in all day? Hmm..
Mike
I certainly wasn't taking 4 hours to write replies :-)
Having said that though, it hasn't happened yet today, so fingers crossed!
Brian.
Quote from: Clinton R. NixonM.J.,
The limit was four hours, and I increased it to 8, which is a crazy large amount of time. If you're taking longer than that, write it in Notepad.
It happened to me twice tonight (since my last post on this forum, above, 3:33 Eastern Time). It had not happened to me before at all (although I have once or twice hit the submit button and had the system error responses I reported before--not since the upgrade, but it is entirely possible that this is the new version of that error). Although I don't run a timer on my posting time, it's only just been four hours since I posted the previous comment on this thread, and I've read every new post on four major forums since sometime early yesterday morning and answered more than just those two. They were, I think, somewhat longer posts, but I doubt I was an hour on either of them.
I came back (to this forum--my usual procedure is to look at each forum once each day) to report it was happening; I can't say what time I made those posts (although I suppose it's recorded in the system, isn't it? I just don't remember which two they were), so I can't be certain whether the glitch happened before or after the posting time adjustment.
How does the software measure the time limit? Is it possible that it reacts differently in different browsers or platforms? Just a thought--I'm really out of my depth, but I know these can be problems. I'm on a W98 using NS6.2.1, if that helps.
--M. J. Young
Just happened to me when sending a PM (only about 2 lines long so not a lot of time). Backing out and resending didn't help, but when I backed out hit the PM button again and did a new message it went through without a hitch.
Is there perhaps an issue with people posting simultaneously where one of them gets shut out till the other posting is complete that wasn't an issue before?
edit: Heh, it happened again when submitting this post. The same solution as above worked.
This is starting to be odd. (I actually got one today.) I'm going to contact the phpBB dev team and ask them what their solution might be. Until then - be aware of the issue and be proactive.
Yes, prophylactic.
I've been using Ralph's method successfully. I just go back, cut the text, back again, hit the reply or post button, paste, and submit. So, it's only annoying at worst.
Mike
FYI, I got this message *every time* (not an exaggeration) I posted today and on several occassions even using my previously described technique didn't work without several (as in half a dozen+) attempts.
I got this message, too. I didn't think much of it, but it happened when I took a while compasing a message, couple hours, yes, but sure as hell not 8 hours.
I've been searching on the phpBB support forums, and think I might have found the solution. I've made some changes to the board configuration to work around the problem (which I think exists because of rotating IPs - i.e. a load-balancing proxy. AOL uses these, and some other ISPs.)
If anyone else gets an invalid session error, let me know.
was getting them all the time before. Haven't had one today. You may well have fixed it. I was using a proxy server both at home (aol) and at work.
I've had none at all today (and have done a fair bit of posting), I think you may have fixed it. Well done!
Brian.
Hey Clinton, not only does it look like your solution fixed the "Invalid Session" error, it also fixed a problem I have ALWAYS had with my machine at home (using AOL or direct through my cable modem) in which the unread messages flags never worked right. The were on when the page was first loaded, but any refresh would turn them off whether the thread was actually opened or not. It now seems to be that this is no longer happening either...yay!