I know some readers come to the blog and don't see the new posts -- at least not unless they hit "reload." This happens to me too when I use Firefox. I can't think of anything I can do about it other than to let you know there are new posts here every day, so if you're not seeing them, hit reload.
UPDATE: I believe I've solved the problem, based on a clue given in the comments by P. Froward.
August 25, 2006
Subscribe to:
Post Comments (Atom)
Posts
21 comments:
FWIW, it's a Firefox problem, not specifically an Althouse problem or even a Blogspot.com problem - I get the same persisting cache problem on several websites.
However, if the worst thing about Firefox is that until the next major release one must hit refresh on accessing a new page, that still puts it streets ahead of the competititon.
Hitting reload doesn't even work for me. I have to clear cache and cookies. I suspect it's my particular setup for Firefox. However, I'm not going use IE, and I haven't tried Opera, though I have it on my computer. I'm hoping the next release of Firefox will fix it.
This problem just started a week or so ago for me (I use Firefox on a Mac), and only at this site.
This problem just started a week or so ago for me (I use Firefox on a Mac), and only at this site. Hitting refresh does work, but it's a pain. Why is this happening now? And why only here?
It certainly is strange. I use Firefox, and I have to reload in order to see fresh posts at this site -- but not always. It seems to happen at random. And curiouser and curiouser, it only happens here -- not at any other sites I visit, not even other blogspot sites. Dunno why. Still, it only takes a second to click refresh.
Well, reload still doesn't work for me. I have to clear both cache and cookies together -- neither one alone does it. I'm guessing that some combo of Firefox (I downloaded an upgrade about 2-3 weeks ago and the problem appeared shortly after), ZoneAlarm Pro, McAfee Anti-virus and my spam blocker is at fault.
Try putting the following between the <head> tags in your template:
<meta http-equiv="pragma" content="no-cache">
See if that helps.
P. Froward: What do you mean by "between the head tags?
I can find the opening "head" but I can't find a closing tag.....
Wait a minute....
I found an older copy of the template and saw that it had a closing "head" that was missing from the current template.
I'm putting the closing tag in and seeing if that solves the problem!
What do you think???? That should be the solution, right?!
Thanks, Gerry! That's exactly where it was in my old copy of the template and where I've put it in my new version. This is great!
I really wonder how it got lost, though. I never made any modifications there before.
I wouldn't think fixing the missing close-head tag would fix the caching problem, but wtf do I know about Firefox's internals? Squat, that's what.
So you still think I should put that other code in? Should I just put it anywhere between the "head" tags?
The reason I thought it would make a difference is that it is a way that my blog was different from others, and people were saying they only had the problem here.
"With the other metatags" -- what does that mean? I put it right before /head. Is that okay? You know, I don't even know what "metatags" are.
Gerry, I don't think I've solved the problem yet. I'm still seeing it with Firefox on my computer.
Gerry: that page you linked to said the code is
META HTTP-EQUIV="CACHE-CONTROL" CONTENT="NO-CACHE"
but P. Froward said it's
meta http-equiv="pragma" content="no-cache"
I'm redoing it using the code from that page.
I still don't think it's working...
I do.
I hope it's just me...
Any new ideas?
Thanks so much, Gerry. I'll see if it worked on the problem for me as soon as I get some new posts up.
Well, I put up a new post and tried it. Didn't work....
Ah! That worked!!!!! Thanks, Gerry!
Post a Comment