Changes I make to my NoScript WhiteList (e.g. by using “Allow” (not “Temporarily Allow”) when a script is blocked, or using “Remove Selected Sites” in the Whitelist tab) seem to be forgotten after FireFox exits. When I again run FireFox, the recently Allowed sites require Allowing yet again. Sites removed from the Whitelist with “Remove Selected Sites” reappear on the Whitelist.
I’ve tried using “Reset” in the NoScript Options. I’ve also tried removing and then reinstalling NoScript in Firefox. No improvement.
[Invalid] WhiteList frozen
-
mck
[Invalid] WhiteList frozen
Mozilla/5.0 (Windows NT 6.1; WOW64; rv:40.0) Gecko/20100101 Firefox/40.0
Re: WhiteList frozen
Do other changes to NoScript settings save?
What about changes to Firefox settings?
What about changes to Firefox settings?
*Always* check the changelogs BEFORE updating that important software!
-
-
mck
Re: WhiteList frozen
Barbaz,
Thanks for your quick reply.
It seems that other changes to NoScript settings, as well as changes to Firefox settings, are NOT remembered. So, as you guessed, it seems to be a broader problem.
Thanks for your quick reply.
It seems that other changes to NoScript settings, as well as changes to Firefox settings, are NOT remembered. So, as you guessed, it seems to be a broader problem.
Mozilla/5.0 (Windows NT 6.1; WOW64; rv:40.0) Gecko/20100101 Firefox/40.0
Re: WhiteList frozen
So see if Standard Diagnostic helps get anywhere?
Check the contents of your profile folder (mostly look for excessive prefs-*.js or similar) and maybe create a new profile to see if it's working there?
Check the contents of your profile folder (mostly look for excessive prefs-*.js or similar) and maybe create a new profile to see if it's working there?
*Always* check the changelogs BEFORE updating that important software!
-
-
Guest
Re: WhiteList frozen
Barbaz,
Following your advice, I built a new FireFox profile from scatch. Although tedious, that seems to have solved the problem.
Thanks for you help!
Following your advice, I built a new FireFox profile from scatch. Although tedious, that seems to have solved the problem.
Thanks for you help!
Mozilla/5.0 (Windows NT 6.1; WOW64; rv:40.0) Gecko/20100101 Firefox/40.0