by Tom T. » Tue May 01, 2012 10:48 am
Some likely causes are: not having Admin privileges on the machine (or the ability to elevate your privilege to Admin), the use of a sandbox or VM (virtual machine), which must be given write permissions for these settings; other lack of write permissions to the needed areas; accidentally marking
prefs.js file as read-only; the use of apps like "Steady State", which return the machine to the previous state after each use to protect against malware, and some other issues discussed in
General Troubleshooting Instructions.
Can you save new bookmarks that you create?
Other Firefox settings?
Are other NoScript settings able to be saved (for example, on NS Options > Embeddings tab)?
Change one, close the browser, and restart. Does it save?
Try creating a clean
profile from scratch. Install only NoScript, leaving all of the default settings.
Does the issue go away? If so, then there is likely either an extension conflict, or the profile itself was corrupt.
You can add back your other add-ons, matching them one at a time with NS, to see if you can spot the culprit that is interfering with NoScript.
Let us know the results, and if none of this fixes it, we'll proceed in other areas, thanks.
Some likely causes are: not having Admin privileges on the machine (or the ability to elevate your privilege to Admin), the use of a sandbox or VM (virtual machine), which must be given write permissions for these settings; other lack of write permissions to the needed areas; accidentally marking [url=http://kb.mozillazine.org/Prefs.js_file]prefs.js file[/url] as read-only; the use of apps like "Steady State", which return the machine to the previous state after each use to protect against malware, and some other issues discussed in [url=http://forums.informaction.com/viewtopic.php?f=7&t=1431]General Troubleshooting Instructions[/url].
Can you save new bookmarks that you create?
Other Firefox settings?
Are other NoScript settings able to be saved (for example, on NS Options > Embeddings tab)?
Change one, close the browser, and restart. Does it save?
Try creating a clean [url=http://kb.mozillazine.org/Profile]profile[/url] from scratch. Install only NoScript, leaving all of the default settings.
Does the issue go away? If so, then there is likely either an extension conflict, or the profile itself was corrupt.
You can add back your other add-ons, matching them one at a time with NS, to see if you can spot the culprit that is interfering with NoScript.
Let us know the results, and if none of this fixes it, we'll proceed in other areas, thanks.