InformAction Forums

Hi

I'm a big fan of NS, used it for years wtih my old WIN XP rig. Just got a new rig (Windows 7 Home Premium 64 bit) and installed NS with Firefox. However, every time I restart Firefox, NoScript has 'forgotten' the pages I have chosen to Allow Permanently and starts blocking every page again. I looked through the options but couldn't see any settings that seemed to be out of place. Is anyone else experiencing this? Firefox version is 3.6.6

Can you see other Firefox options which are not retained across browser restarts?
NoScript's whitelist and other options are saved the same way as all Firefox's preferences, therefore if there's a problem with them (e.g. a filesystem permissions one) it should affect all the browser.
Otherwise, please try Standard Diagnostic.

Hi,
I'm pretty sure I've noticed this on an XP computer as well. I haven't been disciplined enough to monitor what causes noscript to 'forget' the allowed sites, but it would either be a noscript update or a firefox update. I'm pretty sure I noticed this before WIn7 was released too.
While I use noscript all the time, constantly having to redefine the allowed sites is very tedious and is the thing that stops me from recommending it to less technical friends and family.

I'm open to the possibility that it is user error on my part, and would love to hear any advice/opinions on this.

Thanks

Sk

Same problem here. Windows 7 x64 Pro. Firefox 4. Tried manually adding to whitelist several times/ways. Restarted firefox a bunch. Can't get it to retain certain sites. Ugh.

I'm also having the same problem. Win 7 x64 Ultimate, Firefox 4, NS 2.1.0.1. Seems to "forget" settings at arbitrary times. I was clicking around LifeHacker when suddenly everything stopped working. Looking a the NS menu, lifehacker.com and everything else on the page wasn't allowed.

Are you using Firefox Sync?

I am. I just read the thread about sync. I'm going to guess that this is because I'm not running sync on all my FF installs. Or because not all my installs are FF4. (Although a quick test of changing prefs on a FF3.6.16 install did not affect NS prefs on a FF4 install).

Incidentally, one of my synced installs is FF mobile on Andriod.

Same here. FF4 on two machines. One 32bit, one 64. Sync enabled on both ends.

-> Whitelist is VERY unstable.

I will try to deactivate Sync for a while. Let's see what happens.

Put me down for a user who has FF4 and NoScript, where the latter forgets websites that have been allowed, even within a session. Been using FF and NS for years and never had this issue.

For example, I just went to box.net and registered, allowed the site, and while using it it starts misbehaving. A look at the status bar shows that box.net is back to being disallowed barely a few minutes after allowing it.

alphadogg wrote:Put me down for a user who has FF4 and NoScript, where the latter forgets websites that have been allowed, even within a session. Been using FF and NS for years and never had this issue.

Same thing here.

OK, I just figured this out...at least for me.
In NoScript options, I had disabled 'Open permissions menu when mouse hovers over NoScript's icon' so I could enable 'Left clicking on NoScript toolbar button toggles permissions for current top-level site'. Well...apparently this latter setting, even though useful, only allows for temporary permissions. So that was why Firefox was not remembering the settings...it wasn't supposed to remember, it was temporary.
So I just reversed what I had done and now I guess it's fine.

Hope it helps someone.
Carlos

Thanks Ziwdon.. That Was It.

"Open perm menu when mouse hovers over icon" was something I had also disabled for the convenience. I had assumed that any site for which I clicked the icon would be added permanently, but its only temporary.. this information is not highlighted anywhere apparently.

The sites which were being referenced for scripts, that I had permanently allowed from the drop down menu WERE being remembered, but the sites that I allowed by clicking the icon were not being remembered. AAAGGHHH... this problem was driving me insane. Thanks a lot for the useful information

Thank you both for reporting this. If I recall correctly, temporarily allowing the site is the programmer's desired behavior when clicking the NoScript icon for a top-level site that's not current allowed. But the NoScript > Options > General pane says "Left clicking on NoScript toolbar button toggles permissions for current top-level site". I think the word temporarily should be added to that. I'll report this as a user interface problem.