Problem with cookies?

[Katman]

Ever since the first of the year I have to login every time I enter the forums. Prior to that I was always logged in.

I haven't changed any settings, and I don't have any problems with other sites where I have cookies set.

Is it HQ or is it me? Any suggestions?

[Astros34]

Maybe you unchecked the "remember me" box.

[RAY@HQ]

I think my cookie expired around 1/1 and I had to login again, but that was only a one-time thing.

[Katman]

I check the "remember me" box every time I enter the forums and log in. Can't figure it out.

[Howie M]

It's been happening to me on and off for the past few days....

[mnollen]

Probably just a Y2K thing that's 10 years late.

[RAY@HQ]

Are you guys who are having the problem using IE? Firefox? Other?

[Ed@HQ]

Are you guys who are having the problem using IE? Firefox? Other?

I have experienced this in Firefox only (still happening as of today). IE has been working fine. -Ed

[Tom_T]

I use Firefox, and haven't had any issues.

[PD@HQ]

I'm on Firefox (two different computers) and I had to re-sign in on both but only once each.

Anybody have trouble with the Play Index service at baseball-reference.com? On Jan. 1, it would not take my login -- it did not reject the credential, but just kept sending me back to the public page. It started working on Jan. 2.

[tribefanz]

using IE here : has occurred near daily over the past week :would love to fix as i frequently need a reminder just to get my password

[RAY@HQ]

I dropped a note to our tech guys to see if they have any insights.

[Katman]

I have the problem every time I enter the forums on Firefox. Tried it on IE and had the same problem.

[Tom_T]

You might want to try deleting your HQ cookies and starting from scratch, so that HQ stores a brand-new cookie. I notice that my current cookie has an expiration date of 12/31/2010, so clearly that's a new version.

[Katman]

You might want to try deleting your HQ cookies and starting from scratch, so that HQ stores a brand-new cookie. I notice that my current cookie has an expiration date of 12/31/2010, so clearly that's a new version.

Solved the problem. Thanks.