Since the most recent Firefox updates, I am having trouble with certain features on The New York Times website; I can no longer see certain weblog comments, or post comments, etc.
This question is admittedly a little complicated. The New York Times website has a number of weblog pages which include brief stories followed by space for readers to leave comments. You probably need to be a Times On-Line subscriber to really see what I'm talking about, but some examples would be this City Room blog: http://cityroom.blogs.nytimes.com/2011/09/02/bloomberg-cancels-radio-talk-amid-furor-over-aides-resignation/ or this Arts Beat blog: http://artsbeat.blogs.nytimes.com/2011/09/01/theater-talkback-remembering-jerry-leiber-a-reluctant-pioneer-of-the-jukebox-musical/
Since the most recent Firefox updates, when I view these pages, which traditionally have a number of reader comments at the bottom of the Times' story (or at least a space to leave a comment), I can no longer see the comments. There's simply empty. blank space. I know that the comments are there; if I open Internet Explorer and log on to the same page, the comments are suddenly visible. I don't understand where this problem has come from. I haven't noticed whether I'm missing seeing anything on other websites yet.
I also cannot post comments on other parts of the Times website; while the pages dedicated to story-specific reader comment seem to load correctly and the space to type my comment does appear, I can't actually submit the comment. Repeated pressing of the "submit" icon has no effect. Once again, this works normally in IE.
For the record, in the past week, I have changed my computer's anti-virus software from McAfee to Norton 360. I run Windows XP. If there's any another information I can provide, please advise, as I vastly prefer running Firefox to IE.
Všetky odpovede (2)
Update: As of Sunday morning, Sept. 4, this problem has somehow been resolved. I don't understand how -- I didn't make any changes in my system after posting the above inquiry. I contacted the Times about the issue; perhaps it was something of an internal matter with their software. I don't know. I am glad the problem seems to be over.
If it happens again then try to reload the website or clear the cache and the cookies from that website.
Reload web page(s) and bypass the cache.
- Press and hold Shift and left-click the Reload button.
- Press "Ctrl + F5" or press "Ctrl + Shift + R" (Windows,Linux)
- Press "Cmd + Shift + R" (MAC)
"Clear the Cache":
- Tools > Options > Advanced > Network > Offline Storage (Cache): "Clear Now"
"Remove Cookies" from sites causing problems:
- Tools > Options > Privacy > Cookies: "Show Cookies"