Re: Forced logouts now?
...and then not giving everyone else who lives at the house a new key to get in, so they have to ring the doorbell every time they come "home".
Not quite, the new key has and is being given out, but your browser is refusing to accept it and is still trying to use the old one thus the reason you need to ring the doorbell each time...
Believe it or not or whatever but the problem is on "your" end, the server is doing it's job... I know that sounds blunt but it's the simple truth...
Get rid of the bad cookie and get the new cookie and it will fix itself, I have done it on no less then 7 machines now all different configurations without a hiccup... If you delete the old cookie and verify it's gone and log back in I see no legit reason it shouldn't work... the new cookie being served up is valid, the only reason the issue should arise is if you are still trying to use the old cookie...
Those still having problems, open up the browser, don't go to any site blank browser window...
Delete cookies, refresh and view cookies to verify it was deleted...
Shut down the browser and restart to a blank page, again verify that no cookies exist for either
www.therpf.com or therpf.com
TYPE IN don't use a shortcut or link...
http://www.therpf.com
Log in and click the remember me button...
I have a feeling people are not really deleting the old cookie, I suspect the cookie might be sitting in RAM as a valid session in the browser as well as on the hard drive in some instances and because the site is still open and you session still active when you delete the hard drive copy it simply re-writes the cookie sitting in RAM (or possibly another cache) back to the hard drive...
On top of not even telling them you "changed the locks" until after the fact.
Yep they could have but as Art said 99% of the security updates are silent and never noticed, this one though caused issues, and from what I gather vBulletin never informed anyone about the possible issues until after the fact either... At this time I don't administer any vBulletin boards so I don't have access to the members only section of vBulletin support to verify if they did or didn't warn against possible cookie problems...