InformAction Forums

Hi,

My Windows64 computer has 3 user accounts. Updated noscript to version 2.1.2rc0 on one account but won't update on the other 2 accounts.
The other are stuck on version 2.1.1.

Any ideas why?

Thanks

(wonder if the rc0 is throwing off AMO?)

Popsicle wrote: My Windows64 computer has 3 user accounts. Updated noscript to version 2.1.2rc0 on one account but won't update on the other 2 accounts.
The other are stuck on version 2.1.1.

The one which got updated did so because it had been accidentally switched to the "beta" channel by this AMO bug.
The other ones are "stuck" with version 2.1.1.1, actually, because it is the most recent "stable" version published on AMO.
The most recent "stable" version available is 2.1.1.2, which currently waits for approval in the AMO queue (betas and RCs are pushed directly for update, which is the reason why 2.1.2rc0 arrived first).

Notice that I've tried to clarify this issue on the release notes page, which now greets Firefox 3.6, 4 and 5 users who are on the beta channel with this message:

Thank you for helping NoScript development by using a beta or release candidate. This is absolutely safe, because only reliable NoScript packages, even if labeled as "beta", are given for automatic updates; as a bonus, you get new protection features and bug fixes faster. Nonetheless, you may have been switched to this "beta" update channel accidentally, by a recent [url=https://bugzilla.mozilla.org/show_bug.cgi?id=663780]bug of the Mozilla Add-ons website, rather than intentionally. If this is the case and you prefer to switch back to the "stable" channel, you may want to install latest "stable" version.

Thanks for the help.

Hi Giorgio! I was wondering if you will be putting the 2.1.1.2 link in the direct download page for d/l?

Thanks!

Guest wrote:Hi Giorgio! I was wondering if you will be putting the 2.1.1.2 link in the direct download page for d/l?

Ooops, my fault. I was sure I did yesterday. Done now, thanks.

Thanks so much!