2 yabba Sep 02, 2008 10:53

¥åßßå:
Thanks for the suggestion. There is no www/non-www version of the domain. I use blogs.mydomain.com, and before anyone asks, it's behind a firewall that I can't let you get to.
I'm not immediately seeing what this would do. It may be the right path to chase, so would you mind explaining why you suggested this.
Ok, quite often the problem is that the cookies are set for the www version off the domain name and the baseurl is set for the non-www version ( or vice versa ). FF seems to barf at cookies that are misrepresented in that way.
But, if your on a blog.domain.com then that *shouldn't be a problem.
It might be worth meandering through /conf/_advanced.php and seeing what you get for $cookie_domain though ( just var_dump() it and sod the header errors :D )
¥
Ahh, I see. That's definitely not the problem.
I know I'm a bad admin for going the easy route and not doing the root cause analysis, but I simply don't have the time to keep trying to figure this out. I just reinstalled 2.4.2, and the problem has gone away.
This is exceedingly strange.
Baaaaad admin ...... sheeesh a proper admin would *never* just press reset :| ... at the very least they'd cover it with something like "it was a necessary reboot so our firewall could install it's latest rules which will keep maaaaaaaaaaaany more nasty guys off our servers sir" ;)
¥
Chashock,
Try deleting the blog cookie from your browser. I had the same issue, and deleting the cookie solved the problem for me.
Good luck,
RocketDude
Try both the www and non-www version of your domain ;)
‼