[RESOLVED] V2.04 -- Now I cannot allow or disallow scripts

[lpmorgan1]

Since upgrading to V2.04, I cannot mark ALLOW for scripts at a particular site, or DISALLOW a script at a site. I have had to deactivate NO SCRIPT.

Example: When using OPTIONS I see ALLOW http://sitename.com, but when I left click it nothing changes.
I am running FIrefox 3.6.12 *(Mozilla Firefox for Ubuntu Canonical 1.0) on Ubuntu 10.10.

I have tried disabling all other Firefox Extensions and see no change.

Suggestions ? I really hate running without No Script

lpmorgan1

[Giorgio Maone]

Can I see a screenshot?
Do you get any error (red) message in Tools|Error Console when this happens?

[lpmorgan1]

No. I do not get error messages. Just no changes.

[Giorgio Maone]

Again, could you show me a screenshot?
Does it work on a clean profile?
If it does, could you try Standard Diagnostic?

[evanpelt]

I am seeing the same thing with the latest updates.

I run Firefox profiles and each profile/browser must be updated separately so I have a few slightly different versions of NoScript on my machine. I am not having this issue on the profile that has NoScript v 1.9.9.77, but I am having it on v 2.0.3.2

I run Ubuntu 9.10 - Karmic Koala and Firefox 3.5.9 for Ubuntu canonical - 1.0

NoScript v 2.0.3.2
I am getting Scripts partially allowed, but as you can see I cannot allow one of the scripts.




This is what it looks like in 1.9.9.77 on the same site



Not being able to allow this script is creating a major functionality issue for me on this site.

Thanks!

[Giorgio Maone]

OK, I can see what you mean.
This is a bug, because http://media2.bonanza.com:9000 should be automatically added to your temporary whitelist as soon as it is encountered, since bonanza.com is allowed, but it's not because this behavior has not be wired into XMLHttpRequest on the now obsolete supposition that it couldn't work cross-site (now cross-site XHR is allowed under some circumstances).
I'm gonna fix this in next development build, but in the meanwhile you can work-around by manually adding http://media2.bonanza.com:9000 in NoScript Options|Whitelist.

[Giorgio Maone]

@evanpelt:
your issue should be fixed in latest development build. Not sure whether it's the same as OP's, though...

[evanpelt]

Thank you Giorgio, adding http://media2.bonanza.com:9000 directly to the whitelist did the trick.

-- Elizabeth

[lpmorgan1]

Again, could you show me a screenshot?
Does it work on a clean profile?
If it does, could you try Standard Diagnostic?

I have some screen shots. I will try to post them here.
How to do that is not clear to me.

I will try to upload them to a web site and link the URL. I cannot see how to post a screen shot here.

[lpmorgan1]

Here are two screenshots

1. What I see when I try to allow a script:


http://travelingmorgans.com/Misc/noscriptss1.jpg


2. Error Log

http://travelingmorgans.com/Misc/errorconsole.png


I hope these are visible to anyone interested.

lpmorgan1

[Alan Baxter]

@lpmorgan1:
Install NoScript 2.0.5rc1, the latest development build. Does that help?

[lpmorgan1]

The latest test build is installed. I can PROHIBIT scripts but cannot allow scripts.

[Alan Baxter]

Try these steps, in order, until NoScript is working right again.

- If you have any Firefox extensions called HP Smart Web Printing, Skype, .NET Framework Assistant, or McAfee Site Advisor, then uninstall or disable them. They're buggy and known to cause problems with the status bar icon.

- The NoScript settings became messed up somehow. Reset the NoScript Options by pressing Reset at the bottom of the Options dialog. Export your whitelist before doing that if you've added any trusted or untrusted sites you'd like to restore after NoScript is working again.

- There might be an extension conflict. Use the Add-ons manager to temporarily disable any other Firefox extensions you have installed, except for NoScript.

- Perform a Standard Diagnostic. If NoScript isn't working by the time you get to the "Create a new profile" step, a new profile with no other extensions besides NoScript should work right.

Hope this helps. Please let us know whether it does.

[lpmorgan1]

The RESET button did the trick. Thanks!

[Alan Baxter]

You're welcome. Thank you for letting us know.