I run into this problem sometimes where if I take too long to type a post, it seems like my session times out. When I hit submit, it takes me to a page where I need to log in again. Then, after logging in it takes me to a page where it says thread not specified. Usually I can get back to my post intact by hitting the back button of the browser a few times and then hit submit again, but a couple times I've lost my post this way. I've tried this in Linux and Windows and I've tried it in at least 3 browsers with the same results. The time limit is pretty long and normally isn't an issue, but sometimes I have to do some research in the middle of answering a question or I'm flipping back and forth between a computer I'm working on and another I'm posting with. Sometimes I'll time out in this case. I'm just wondering if this time limit is a necessary thing... I'm sure it's not much of an issue for most people.

Second suggestion would be to consolidate the main menu into one main menu. One time I spent about an hour looking for something around the site because I didn't realize that it was a link in the second main menu farther down the page.

You need to select the option in your UserCP to browse the forum with cookies so it keeps you logged in until you log out.

Yup, I double-checked. Browse with cookies is set to yes in my profile. Perhaps it's some other setting in my browser I guess. Was just checking to see whether this was something other people were getting as well. Still, it's strange that it's a certain amount of time before the session times out. For short period of times, everything works fine.

If you have cookies enabled in your browser and your LQ profile, your session will be transparently restarted.

--jeremy

The only unusual setting I have dealing with cookies is only allowing them for the originating website. Do linuxquestions cookies originate from a different site or something like that? I'll turn off that option and see if I can replicate the problem.

All LQ cookies originate from .linuxquestions.org

--jeremy

Just as I follow up. I confirmed that it was the the allow cookies "for the originating website only" option in Firefox that caused this problem for me (and a similar option in Internet Explorer most likely). So if anyone else has this problem, just uncheck that box.