"Allow" options grayed out

[Guest]

I am using the latest version of NoScript. Contrary to older versions, all of the "Allow [http://site.com]" options are initially grayed out when clicking on the NoScript icon. To make them active I have to click "temporarily allow all items on this page," and then click on the appropriate option. Is this a bug in the most recent version? If not, how to enable the "Allow" options without first allowing every element on the page (as was the default in previous versions)? Thank you.

[therube]

Do you have Options | General -> Temporarily allow top-level sites by default enabled?
If so, that may do something similar to what you say.

[Guest]

Thanks for yours quick reply. No, "Temporarily allow top-level by default" is not checked. Everything seems to be set as it should be. Normally, NoScript works without too much tweaking. Let me be a little clearer about the problem perhaps.

All the scripts are blocked by default (which is correct). However, when trying to selectively allow some scripts, I cannot, because all of the "Allow" options are grayed out and do not respond to clicking. So I have to first "Allow all for this page" and then forbid the scripts I do not want. This is the reverse of how NoScript is designed to work and also entails much more clicking for every page visited. I have tried reinstalling previous versions of Firefox with the same result. However, older versions of NoScript have worked fine. Any suggestions?

[therube]

What other extensions are you running?

Backup your settings, then try a Reset ?

(There were some lockdown measures in NoScript <now where did I see that?>, but even if they are actually implemented, you would have to manually make changes to affect them in about:config, so something like that is unlikely.)

[Guest]

I have tried uninstalling and reinstalling NoScript several times with no change. Perhaps the developer has a solution? Alternatively, are older versions archived somewhere on the Internet to use until this problem is solved?

[therube]

Uninstall/reinstall will not change the NoScript user settings which are stored in your Profile.
A Reset will.

Older versions can be found here, http://noscript.net/feed.
Won't hurt to try an older version. If it happens to work, then retry the latest. If the latest again does not work, then see if you can pinpoint the last older version that worked.

[Guest]

Hello,
I have too many extensions installed to list here. But only two or three more than when NoScript was working. Perhaps one of them is the problem.

I renamed the ABE file, just in case it was the problem. I then moved the numerical file which stores the NoScript files, uninstalled NoScript, downloaded it again and reinstalled it. Does this accomplish the same thing you were referring to by user settings? Unfortunately, the same problem occured.

Perhaps I should start Firefox in safe mode and just uninstall the extensions until the problem stops?

[Grumpy Old Lady]

I strongly advise you to follow the advice from therube to use the Reset provided in the NS Options. It's been provided by Giorgio for just this kind of situation - -
It looks like you have set Options|Advanced|HTTPS |Behaviour "Forbid active web content unless it comes from a secure (HTTPS)connection." to "always".
This setting should remain at the default "never" unless a user has a specific reason to change it.

[GµårÐïåñ]

Something else to consider before the reset, do you have allow sites through bookmark? If so and you are launching from a bookmark, that would explain that, otherwise, follow the advise already provided.

[Giorgio Maone]

Could you check if you've got NoScript Options|Advanced|HTTPS|Behavior|Forbid active content unless [...] HTTPS set to something different than "Never"? If so, please reset it to "Never".

[Guest]

I was under the impression that uninstalling and reinstalling NoScript would automatically reset options to default, but I guess as with everything else in Firefox all settings are carried over. You are all correct. The Forbid active content unless it comes from a secure(HTTPS) connection: option was set to "When using a proxy(recommended with Tor)". It is now set to "Never" and the "Allow" options are now active. Thank you therube, Grumpy Old Lady, and Mr. Maone very much for your accurate diagnosis and quick assistance. And thank you, Mr. Maone, for developing NoScript. The web seems to only be increasing in its insecurity as it matures. Have you all heard that Google and other marketers are considering combining offline credit report data with people's online surfing trails? Amazing in its invasiveness. Thank you again.

[Guest]

I too have the "Allow"-button grayed out. "Forbid active web content unless it comes from a secure (HTTPS)connection." is "Never" and I have tried a reset. No luck. What's my problem?

[Giorgio Maone]

I too have the "Allow"-button grayed out.

Button? nobody here talked about a button.
Are you trying to allow a site whose parent is already in the whitelist from NoScript Options|Whitelist (e.g. allowing mail.yahoo.com when yahoo.com is already there)?