LOGIN BUG, ERASES POSTS IN QUICK REPLY?

[REDJOHNNYMIKE]

Hello, I'm pretty sure this is unrelated to the previous thread I posted rgarding logins, I recently saw a thread saying you required Logins to cut down traffic, but I've had this problem since before then,

This time it erased a rather large detailed response to my modding thread quite a few paragraphs, I ain't mad though,

But the problem is:

When submitting a post, even when I am logged in and it is clearly displayed in the upper right corner, a login screen will pop up, requiring me to relog before posting, it doesn't continue to submit the post though, it instead returns you to the original thread without submitting, anything written in quick reply is erased (in this case quite a bit), if I use the back button to try and return to the page I typed it in, It shows me as logged out and the quick reply is erased.

 

The same thing happens occasionally during normal non quick reply posting, but it actually submits the message and takes you to the thread after loging in.

 

Any idea why this happens???

Has anyone else had this problem?

[coupes.]

Happened to me before...

 

Basically, when you log on, you open a session, and it remains open as long as the server can see activity on your end, meaning you request pages and such. However, if the server doesn't receive any traffic from you, it'll close the session after a while for security reasons and to cut down traffic. My guess is you took a while to write your "rather large detailed response" so it closed your session, thus asking you to login again in order to post your message. I think by default the session is set to 20 minutes.

 

If you're the only one using the computer, you can check the "Remember me" option when logging in to save your login info in cookies, this way this kind of situation shouldn't present itself again. I personnaly always copy my messages in my clipboard before posting, it saved me quite a couple of times back when we were on the old grumpy server.

[Jan Gaarni]

An always good advice when posting stuff on any forum is: Mark and copy everything you wrote before hitting the submit button.

 

I always do that, just in case. Even with 1 sentences.

 

I even copied this one just so I wouldn't have to write it again.

[ChAiNz.2da]

Hey RJM, are you getting that error when you have 2 instances of LF open? I've only run into that problem when I had 2 seperate threads open (via Firefox tabs). The second tab doesn't retain your 'login' if you try to post within it... I always had to make sure that my actual post was in the 1st tab (or first instance) of LF.

 

Though I highly agree with what Jan Gaarni suggested I do that now more often than not.. especially if it's a detailed post

[Joshi]

Copy and paste? I'm not telling you not to complain, obviously it's a problem for you, but as a safety measure, when you post long posts, copy the text before submitting and then if that happens, you can just paste it back after logging in.

[REDJOHNNYMIKE]

@coupes, I admit I'm not very technical, but doesn't writing a really long post count

as activity???

 

@Chainz, I did have it happen that way before, but this time it was only one window and I was clearly logged on.

 

And as for copy pasting, I used to do that when the forum was slow and I had bad service (cut out after 30 min of use,crazy) but it was a modding thread, I was in a creative "ZONE":D I'd typed quite a bit and I was like "AT LAST I'VE ANSWERED EVERYONES QUESTIONS!!! CLICK SUBMIT BEFORE SOMETHING HAPPENS!!!"

just kinda forgot about wierd stuff happening after submitting.

[coupes.]

@coupes, I admit I'm not very technical, but doesn't writing a really long post count as activity???

Not really, I'll try to put this simply...

 

Whenever you request a page to the server, it generates a result page and sends it to your browser. The actual "request" of the page is considered activity, but after the server has sent you the result page (where you compose your message) it has no way of knowing what's happening on that page since it's happening on your machine.