Page 1 of 1

[RESOLVED] Firefox/NoScript Issue: /Newsweek

Posted: Fri Sep 04, 2009 4:00 pm
by john181818
I have had a recurring issue while on the Newsweek site when I click to some Newsweek links, specifically including the Pox Vox topics and a few others. I have tried finding any No Script temporary authorization combinations to figure out what is causing the problem, but I have not found it. I have gone so far as to grant temporary authorizations to everything on the Newsweek site, but it still won't work. The problem does not appear using IE8, nor does it appear on another computer, running Firefox, that does not have No Script installed. That leads me to believe the incompatibility is between No Script and the Newsweek site.

Any thoughts?

Thanks.

John

Re: Firefox/NoScript Issue: /Newsweek

Posted: Fri Sep 04, 2009 4:16 pm
by Alan Baxter
john181818 wrote:I have had a recurring issue while on the Newsweek site when I click to some Newsweek links, specifically including the Pox Vox topics and a few others. I have tried finding any No Script temporary authorization combinations to figure out what is causing the problem, but I have not found it.
Could you provide some more information about your issue? I can't tell from your description what the problem is. Make sure you're using the latest version, NoScript 1.9.8.8, available at http://noscript.net/getit

Re: Firefox/NoScript Issue: /Newsweek

Posted: Fri Sep 04, 2009 4:36 pm
by john181818
I apologize. I am also on the most recent version.

What happens is that I get the following from the Newsweel site.
"Error

Our servers have encountered a problem."

This went on for days before I finally tried it on IE and on another computer and they both worked fine, so it wasn't a server problem that I could see. The only thing I could figure was that somehow it is No-Script.

It only happens on some of the Newsweek pages and I have had the most consistent problem with their Pox Vox section. Others sections are iffy.

I need to run a few errands. I'll check back in a bit in case you have additional questions or comments.

Re: Firefox/NoScript Issue: /Newsweek

Posted: Tue Oct 06, 2009 4:52 am
by Tom T.
I see the topic is old. Are you still having a problem? I just went there with F2.20 and no scripting allowed at all, and clicked through the entire menu, including Pox Vox, without trouble. Of course, I would have to allow various scripts and plugins to view videos, etc. But all of the articles showed up just fine.

Latest official release is 1.9.9.07. If your problem is solved, please let us know. If not, please check the Error Console under the Tools menu, and advise what red errors you are getting, or any other steps to reproduce or info about error messages. Thanks.

Re: Firefox/NoScript Issue: /Newsweek

Posted: Tue Oct 06, 2009 6:07 am
by john181818
I have 1.9.9.01 at the moment.

I am still having issues in the same manner. Here are the error codes.

Warning: Empty string passed to getElementById().

Warning: Empty string passed to getElementById().

Warning: Expected declaration but found '*'. Skipped to next declaration.
Source File: http://ndn.newsweek.com/site/css/structure.css
Line: 253

Warning: Expected declaration but found '*'. Skipped to next declaration.
Source File: http://ndn.newsweek.com/site/css/structure.css
Line: 257

Warning: Expected declaration but found '*'. Skipped to next declaration.
Source File: http://ndn.newsweek.com/site/css/structure.css
Line: 338

Warning: Expected declaration but found '*'. Skipped to next declaration.
Source File: http://ndn.newsweek.com/site/css/structure.css
Line: 339

Re: Firefox/NoScript Issue: /Newsweek

Posted: Tue Oct 06, 2009 6:10 am
by john181818
I just upgraded to 1.9.9.07 and have the same problem.

Re: Firefox/NoScript Issue: /Newsweek

Posted: Tue Oct 06, 2009 7:24 am
by Tom T.
Are you allowing the cookie from newsweek.com, and the additional one from blog....?

I get a ton of those yellow warning messages. Most don't mean much or affect anything. We're looking specifically for the red error messages. Are any of those marked with the red, sort of stop-sign shaped thing with the exclamation? If so, please advise.

What other extensions do you have? Often, extension conflicts will cause problems. Please see the General Troubleshooting Instructions for steps to diagnose extension conflicts. It might well not be NoScript at all, but another Firefox extension. I still cannot reproduce your problem.

If the General Troubleshooting diagnostic does not solve the issue, please let us know, including any red error messages in the Error Console. Thanks for your patience.

Re: Firefox/NoScript Issue: /Newsweek

Posted: Tue Oct 06, 2009 3:14 pm
by john181818
I haven't cleared the issue yet and am down to the Standard Diagnostic stage. I'm both passing my comfort level and getting a bit frustrated. I am installing Windows 7 in a few weeks and will wait until after that, so go ahead and close the thread and we will look at this after the other changes are made.

Thanks.

Re: Firefox/NoScript Issue: /Newsweek

Posted: Wed Oct 07, 2009 2:51 am
by Tom T.
Thanks for letting us know the status.
I understand your frustration, but please know that the Standard Diagnostic has cured thousands of issues.

Marking this closed as per your request. Let us know if it persists after Win 7. Good luck.

Re: [CLOSED BY OP] Firefox/NoScript Issue: /Newsweek

Posted: Wed Oct 07, 2009 8:06 pm
by john181818
I know this is a closed topic but I thought I would provide an update, especially since it is seemingly good news.

I uninstalled Firefox from top to bottom. I used CCleaner and cleaned out all the files and then used it on the registry. Then I downloaded and reinstalled Firefox 3.5.3. Once I had that running I downloaded and installed No-Script. Since I did that I no longer have the problem on the Newsweek site.

Also, for what it is worth, I had gradually uninstalled all the add-ons for Firefox and even with them all uninstalled I had the same issue. I still had the issue when I first reinstalled Firefox without having deleted all my Firefox personal files. That was what had caused me to completely uninstall and use CCleaner. So there apparently was an issue (probably) deep within my personal settings. Because I have twice a day image backups I was able to reinstall my bookmarks from a mounted image file and I will customize the new setup as I go forward.

Thanks for the help and sorry to have been a pest.

Re: [CLOSED BY OP] Firefox/NoScript Issue: /Newsweek

Posted: Thu Oct 08, 2009 1:17 am
by Tom T.
john181818 wrote:.... I still had the issue when I first reinstalled Firefox without having deleted all my Firefox personal files. That was what had caused me to completely uninstall and use CCleaner. So there apparently was an issue (probably) deep within my personal settings. Because I have twice a day image backups I was able to reinstall my bookmarks from a mounted image file and I will customize the new setup as I go forward.

Thanks for the help and sorry to have been a pest.
No problem, and no pest, at all! :)

Thanks for the good news, and for the reminder that complete cleanouts can solve problems, and *especially* that frequent backups are *vital to all users* -- since we never know when a catastrophe might occur, or complete deletions be required.

Will change the topic heading to "Resolved". Thanks again for the update.
Cheers
-- Tom T.

Re: [RESOLVED] Firefox/NoScript Issue: /Newsweek

Posted: Sat Oct 10, 2009 9:31 am
by Grumpy Old Lady
Creating a new Profile would've fixed the problem in around 20 seconds, without any need for a clean reinstall.
http://kb.mozillazine.org/Creating_a_ne ... on_Windows

Re: [RESOLVED] Firefox/NoScript Issue: /Newsweek

Posted: Sat Oct 10, 2009 7:51 pm
by Tom T.
Grumpy Old Lady wrote:Creating a new Profile would've fixed the problem in around 20 seconds, without any need for a clean reinstall.
http://kb.mozillazine.org/Creating_a_ne ... on_Windows
Which is one of the steps in Standard Diagnostic, which is one of the steps of General Troubleshooting, which had been recommended to OP, who stated that he was somewhere in the Standard Diagnostic process when he decided on his own to do the clean install.
john181818 wrote:I haven't cleared the issue yet and am down to the Standard Diagnostic stage. I'm both passing my comfort level and getting a bit frustrated.
(emphasis added)
Thanks for reinforcing that the first set of recommendations, including the Standard Diagnostic, would have resolved the issue.
But it seems that all users should stay within their comfort level at all times, and that we as support personnel should be sensitive to that, wouldn't you agree?