InformAction Forums

I had a FF52 and 5.1.7 was blocking most sites saying webpage could not load . Just updated Noscript this morning when I booted ff. Now I have to keep Noscript turned off which is painful. Also just updated ff57 and now must wait for new noscript version.

I had the same issues as described in the first post, starting when NoScript updated to 5.1.7 with FF 56.0.2:

1. Started getting HTTP 302 or 301 errors on several sites (gmail, reddit, mozilla extension download links)
2. Noscript dropdown menu was missing most entries (such as Allow/Forbid [site], Options, About NoScript) for all sites.
3. NoScript options menu settings were all blanked out.

Strangely, this problem only affected my default profile and not my second profile, even though they both updated to 5.1.7 and are both on FF 56.0.2.

I fixed it (for now) by disabling the NoScript add-on, turning automatic update to Off, manually installing the 5.1.6 .xpi file, and then re-enabling the add-on.

This worked great for me: Close Firefox and ". . . deleted the Firefox Profiles startupCache folder contents (not the whole folder, just the files inside) . . . 5.1.7 worked and all settings were back to normal."

As I wrote in post #7..
..after 5.1.5 was auto-updated into 5.1.7, I also got the "all white" NoScript issue,
and fixed it by manually installing 5.1.6 and turning off auto-updates.

Today, however, I read this..:

Guest wrote:I ended up getting 5.1.7 working..

..and so I wanted to try to get 5.1.7 working myself, too.

I used DTA to download and save the 5.1.7 xpi to my Downloads folder,
then restarted Firefox, and chose from the menu..
File -> Open File... (Ctrl + O) -> "noscript-5.1.7.xpi"
and installed 5.1.7 that way.

My plan was then to delete the Profiles \ startupCache folder,
but I just figured that I would check to verify that NoScript had turned "all white" again..
..and it didn't! Everything was still OK. I restarted Firefox, still OK.
So that was unexpected.

Finally, just as an experiment, I re-installed 5.1.5 and let it auto-update into 5.1.7,
and 5.1.7 was OK this time also. Apparently something strange happened that first time.