In the past couple of days, I've had to log into the forum fairly frequently, even though I've got the "remember me" clicked. Summat oop?

It's happened to me a few times lately. I'm assuming updates to code causing a cookie refresh or something. Or not.

Browser? Phone?

Have you tried clearing cookies for tehforum.co.uk and try again?

Both/all three - Firefox on Windows 7 and Nexus, Blackberry browser as well.

Me too - different computers - cleared cookies several times.

for me, most links on teh crash chrome, I am here in IE now because chrome crashes so much

only happens here

Sounds like your Chrome is buggered.

This getting logged out problem is very difficult to diagnose, mostly because I'm not suffering from it! Doesn't matter if I switch browser, use my phone, my Transformer Prime, once they're logged in they stay logged in.

Jon: That definitely sounds like your Chrome is buggered. If Teh / Beehive was crashing everyone's Chrome, someone else would surely have said something.

Me too, pretty much every other time. Using FireFox 21.0 on Mac OS 10.6.8. Always this computer, but then I only look at Teh on this computer.

Just noticed it's happening quite a bit on my phone.

If it's any help, I'm currently on my work PC. In IE9, if I log in with "remember me" set, close the browser and re-open, I'm logged out. If I do the same in Firefox, I'm still logged in.
Previously, I cleared the cookies in Firefox, and attempted to do it in IE using the F12 menu, but it doesn't seem to be playing.

Looking at the cookies in IE using the F12 menu, I've got multiple instances of the cookie set, with a variety of expiry dates:

Cookie Information - http://www.tehforum.co.uk/forum/lpost.php?webtag=DEFAULT&replyto=40507.8
NAME forum_style
VALUE tehforum
DOMAIN www.tehforum.co.uk
PATH /forum/
EXPIRES 12/10/2013 16:53:48

NAME user_logon
VALUE wingnutkj
DOMAIN www.tehforum.co.uk
PATH /forum/
EXPIRES 12/10/2013 15:25:28

NAME user_token
VALUE a token
DOMAIN www.tehforum.co.uk
PATH /forum/
EXPIRES 12/10/2013 15:25:28

NAME forum_style
VALUE tehforum
DOMAIN www.tehforum.co.uk
PATH /forum
EXPIRES 24/08/2013 12:44:26

NAME user_logon
VALUE wingnutkj
DOMAIN www.tehforum.co.uk
PATH /forum
EXPIRES 24/08/2013 12:44:26

NAME user_token
VALUE the same token
DOMAIN www.tehforum.co.uk
PATH /forum
EXPIRES 24/08/2013 12:44:26

NAME forum_style
VALUE tehforum
DOMAIN www.tehforum.co.uk
PATH /
EXPIRES 27/12/2013 19:41:23

NAME user_logon
VALUE wingnutkj
DOMAIN www.tehforum.co.uk
PATH /
EXPIRES 04/06/2014 14:11:52

NAME user_token
VALUE a different token
DOMAIN www.tehforum.co.uk
PATH /
EXPIRES 04/06/2014 14:11:52

NAME sess_hash
VALUE a hash
DOMAIN tehforum.co.uk
PATH /
EXPIRES At the end of the Session


Any use to you?

Tried clearing cookies using the link on the login screen - works on FF, according to Cookie Monster, but not on IE, according to the F12 menu (and using it to clear cookies doesn't seem to be working). Could be two issues - one with IE not deleting cookies when asked, the other with Beehive having written multiple login cookies at some point, then not clearing them properly (but when cleared using Cookie Monster, goes back to working fine).

I'm loathe to do a full clear-out of my IE cookies right now - sorry!

You should be able to use the developer tools in IE to delete the cookies just for tehforum.co.uk.

Yeah, that didn't seem to want to happen - they weren't being deleted no matter how hard I pushed the button. I've now exported all cookies to a text file, edited out the forum ones, cleared IE's cookies fully, and re-imported the text file, and everything seems to be working. Does the multiple-sets-of-cookies-causing-repeated-logging-in theory sound plausible?

Yes.

The HTTP specification allows for cookies with the same name, but different paths. Unfortunately as far as I know PHP doesn't account for this, instead all it does is add all the cookies to a simple single-dimension key-value-pair array (named $_COOKIES) and makes them all available to the script regardless of whether the path matches or not.

And because it's perfectly possible for the browser to format the cookie header so as to send the valid cookie before the invalid one, when PHP processes the header, it simply overwrites any existing entry in the array resulting in the valid cookie never being available to the script.

Which is a bit shit.

Thanks for the explanation!  (Although it's reminded me of just how much I've forgotten about this kind of thing. I'm sure I used to be able to do websites...)

FWIW - I didn't fix my chrome since it wasn't happening anywhere else, it isn't happening here any more - odd