Offsprung wrote:Not sure what fx atm is
Sorry. Fx is Mozilla's official abbreviation for Firefox. It's mentioned in
Forum Rules #12, but I shouldn't have assumed that you read that, or knew the abbreviation.
ATM is a common web acronym for "at the moment", meaning "now", or "at this time". Again, apologies for assuming. Some advanced users complain of condescension if everything is spelled out for them ...
or if whitelist is effected.
I am referring to FireFox and NoScript.
Yes, I got that. And you were in fact describing the whitelist. No problem.
On the menu in FF notification area there is 2 options. Allow and Temporary Allow.
That would not be the Firefox menu, it would be the NoScript menu.
and yes obviously Temp allow is TEMP, But Allow (not temp means PERMANENT?)
Yes, it should be permanent.
only lasts until either FF or NoScript updates via FF plugin update.
That shouldn't happen. Do you use any kind of
"virtual machine" or
"sandbox" that would prevent new things from being stored on your hard drive? (Links have definitions and info on those terms.)
Do you have Administrative privilege on the machine in question? In other words, do you have an Administrator account, a limited user account, or a guest account? I can't help define those any better for you, but the Windows Control Panel should have a User Accounts icon. In Windows XP, you get there from the Start menu and click Control Panel, unless you have Classic menu enabled, in which case, it's Start > Settings > Control Panel.
I'm not so familiar with Vista/7 interface, but unless they've changed the program itself, you can also click Start, click Run, and in the Run box, type
nusrmgr.cpl (Click OK or Enter)
Then double-click User Accounts to see what level is your account.
The whitelist seems long, but have never compared it to my Allow <page> or Allow All selections from FF notification menu.
The Allow menu (in NoScript, not Firefox) will show
only those scripts and objects that are currently being blocked by NoScript. The entire Whitelist, which is what you're referring to with the large Allow list, is in NoScript menu > Options > Whitelist.
By history/setting I mean the choices that I always allow+allow all from the notifications area.
OK, that's the Whitelist in NoScript > Options. In the NoScript menu, they'll show up in red if they're *allowed* to run at the moment (see how useful the acronym is?
), which gives you the chance to revoke their permission conveniently, should you wish to do so.
So you are saying Allow means ADD TO WHITELIST
Exactly.
and when FF finds a FF update or NoScript plugin update, I should not install, bup the whitelist, install update and restore the whitelist or the history of allows will be gone on purpose?
(Terminology: NoScript is an extension or add-on. Plug-in refers to things like Flash player, QuickTime player, etc.)
When Firefox advises you that an update is available for NoScript (or any other extension/add-on), then either it will install automatically or ask you what to do, depending on your settings in FIREFOX Tools > Options > Advanced > Update.
"Automatically check for updates to" -- check Firefox and Add-ons, at least. (Not a fan of the search-engine feature myself, but that's just a personal opinion.)
"When updates are found": Again a personal opinion, but I'd rather be asked what to do, because I might be in, say, an online banking session and don't want to be interrupted. Then I can install the update later, by checking manually. (Firefox Tools > Add-ons > Check for Updates). If installed automatically, it will prompt you to restart Firefox (not your entire computer), but you can click "Not now" if you want; then, it will be installed the next time Firefox is restarted. Or allow the restart to occur.
None of this should change your Whitelist, or anything else.
When Firefox finds an update
for itself , there are two kinds:
1) Update to an existing version. I see that you have 3.6.24, as I do, so I assume that you updated it, or it updated itself, from 3.6.23. (Firefox Help > About Mozilla Firefox will show your current version.) Whether you let it auto-update as above, or choose to wait for a more convenient time (Firefox Help > Check for Updates) when you are able to restart, none of your settings should change, including the whitelist.
2) A brand new version. For example, recently Firefox 7.01 was replaced by Firefox 8.0.
Close version numbers usually don't change too many of your existing settings. But if you were to go from the current 3.6.24 to 8.0, there are so many changes that it might require new versions of your extensions (add-ons). The new version
should automatically check for updated versions of these add-ons, or even just apply a "compatibility update". Again, your settings should be mostly preserved, including whitelist.
The situation where you would *not* keep your settings is:
You have Firefox 3.x in your Program Files folder (or equivalent) and you decide to *add* Firefox 8, rather than *replace* Firefox 3 with Firefox 8.
The reason is that you have to choose a new folder in which to store it, and a new profile must be added alongside the existing one. But it doesn't sound like that's what's happening here.
May I suggest that you peruse the
NoScript Quick Start Guide, the
NoScript FAQ, the
NoScript "Features" Page, and the
video tutorial at your leisure? Learning to drive a car or fly an airplane isn't an instantaneous process. Fortunately, NoScript isn't anywhere near that complicated, but like all excellent things, there's a brief learning curve. Believe it or not, after using it for a while, it will mostly become second nature.
I hope this helps. Let us know if we can assist further, especially if you have questions about the above guides.
