![]() |
|
#1
|
||||
|
||||
![]()
It's very odd that it logs you out when you're replying to a post UNLESS a) that post, for whatever reason, has taking you a rather long period of time to compose; or b) You have the forum open to the message you want to reply to for a long time before hitting the reply button.
I would suspect that just hitting reply does NOT update the site cookie. I would think that things like clicking on 'New Posts' or even browsing to the main screen would update the cookie (just guessing here - nothing more - I could be WAAAAYYY off - it may only update cookie upon login and New Posts). Does your roomie or her bf ever browse TP at all? Would they have any reason to? If not, it may be okay for you to check it anyway. Worse thing that happens is that they access your account here and post bad things... I'm sure were that to happen TP'd help you out and delete such posts (unless they post nudie pics of you, then he'll sticky it - right TP??? ![]() |
#2
|
||||
|
||||
![]()
I've noticed that if I'm typing up a post for longer than 15mins, I will get auto logged out of here. I will then try to go back to post to copy, paste it and it's gone.Once it logs me out, I need to type in my pw over again to get back in.
Probably just to get me back. Or to cause problems for me. Or cus they got drunk and stupid and come on here to have some fun. So no ...not a good idea. Don't you start with the nudies too. Someone wanted some the other night so as a joke, I went to go find some cartoony nudey and got a trojan instead ![]() So not so funny afterall. Good thing norton caught it right away and seems to have deleted it. Only this morning, I ran Norton again; just in case, and it found another one. ![]() Edit: It just happened again. I got logged out while typing this up. And I noticed that once I log back in it gives me this popup message: Invalid Thread specified. If you followed a valid link, please notify the admininstrator.
__________________
To dance is to be out of yourself. Larger, more beautiful, more powerful. ~Agnes De Mille |
#3
|
||||
|
||||
![]()
TP - Under the admin > vBulletin options > vBulletin options > Cookies & HTTP Headers what is the timeout set for? Is it set for anywhere between 600 and 900? If it is, this could explain why Rook is getting logged out. It IS timing out on her. Would it be possible to bump this to 1200 or 1500 (20/25 mins)? That should give pretty much ANYONE enough time to construct a post. It doesn't appear to add any addition server strain or anything like that. It simply changes the time for the cookie to expire (client side, not server side)
Now, if it's < 600 (10 mins) or already >=1200 then it's something else that's causing Rook to timeout. I took a quick look the vBulletin manual and this seems to be the only thing that could be the cause of her logout issue. Oooh. That would suck. Agreed, definitely not a good idea. Start??? I think we started a LLOOOONNGGG time ago about posting nudie pics of you ![]() Last edited by Robbie Robb; 01-30-06 at 05:18 PM. |
#4
|
||||
|
||||
![]()
Nice find Robb. +Rep for you, buddy. I was looking for this earlier and missed it. I knew it was in there somewhere, but the things I was searching for wheren't coming up. "Cookies" - duh.
I just changed this from 600 to 1200. That should take care of Rook's problem. The only issue this will cause people will now remain in the "Who's Online" section for 20 minutes after their last activity. Not a big deal, but something to be aware of - just because it says someone is online doesn't mean they really are. As a tip though.... whenever I type up a BIG post, I also highlight it and copy it to my clipboard (Cntrl-C) just in case. That way, if there is a server hiccup, a "Bad Gateway," or if my connection drops for a minute or anything else along those lines, I don't lose everything I wrote. I simply go back, Paste it, and try again. Beats the hell out of having to retype it all, ya know? |
#5
|
||||
|
||||
![]()
VERY good suggestion. It's something that I had to do regularly at work due to stupid software. I also would do it here back when we were having the 'bad gateway' problems. The one thing I did find (at least with Firefox) here was that if I did get a BG error, I could just go back a page and it still had my post. But at work...all was lost. Nothing like typing up a huge list of troubleshooting steps only to have it disappear into the aether...
|
![]() |
|
|