InformAction Forums

ETA 2024-12-21

If any of your Profiles are 'stuck on NoScript Version 12.0.901' you can now manually get back on the Release Candidate channel using https://noscript.net/getit/#devel to install 12.0.902 (or newer).

Below is the original thread for posterity.
------

OS Windows 10
Firefox Version 128.5.2esr
NoScript 12.0.901 (previously was on ver 11.5.3rc2 - so 'in the RC channel' for NoScript updates)


I have many profiles, all have NoScript, none are set to 'Automaticity Update Extensions'.
All of my profiles include (in prefs.js) So, I manually update Extensions (in each Profile) using

Tools > Add-ons and Themes > click the gear icon > "Check for Updates".

If there is an update available there will be a 'blue dot' on the Extension that has an 'update available for you to install' and there will be a Tab called "Available Updates" with the Extension(s) shown - that can now be updated (if you 'click the blue dot').


STR

On a test Profile

01. use "about:config" to set "extensions.update.autoUpdateDefault" to "false"

02. Install an old RC / beta version of NoScript for Firefox
I use the RSS Feed https://classic.noscript.net/feed?c=200&t=a

Try NoScript 11.5.3rc1
Published: Mon, 11 Nov 2024 20:40:50 +0000

03. In a new Tab (or New Window) "about:support" and check the version of NoScript,
which should be "11.5.3rc1" in this example.

04. In a new Tab (or new Window) "about:networking#dns" and click the "Refresh" button.

05. In a new Tab (or new Window) use Tools > Add-ons and Themes > click the gear icon > "Check for Updates".

06. You will see, here in "about:addons", both the 'blue dot' and the Tab called "Available Updates"
(showing that there is a 'newer NoScript' available).
Do NOT 'click the blue dot' for now.

07. Go back to 04 (the "about:networking#dns" Tab/Window) and click the "Refresh" button.
You should see
in the list of DNS entries because "11.5.3rc1" has checked for an update at
You might also see if the test Profile has any other Extensions or Dictionaries -- that are normal / 'non-beta' Extensions from 08. Now, in the "about:addons" Tab/Window (see 06 above) click the 'blue dot' and Update NoScript.

09. Exit Firefox.


10. Start Firefox using the Test Profile.

11. Use "about:support" to confirm that you are now have NoScript "12.0.901".

12. In a new Tab (or new Window) "about:networking#dns" and click the "Refresh" button.

13. In a new Tab (or new Window) "about:addons" and click the gear icon > "Check for Updates".

14. Now back in the "about:networking#dns" Tab/Window click the "Refresh" button.

My profiles with NoScript "12.0.901" are NOT checking
My profiles with 'older RC versions of NoScript' (and other Extensions) are checking both and when I do step 13 (the "Check for Updates").


DJ-Leith

Can confirm this. Monitoring network requests with the Browser Console (Ctrl-Shift-J) shows that updates for NoScript 12.0.901 are being checked against AMO instead of Giorgio's sites.

Thanks DJ-Leith for the heads up, I'll keep an eye out to install manually when the next NoScript dev build is available.

I looked in the "manifest.json" files (from backups of two Profiles) using Notepad++ as an editor.

Here are the first 15 lines. I have added pseudo line numbers.

Good - Version 11.5.3rc1


The Version 12.0.901 - which is 'NOT checking' for updates
The "update_url" (line 8) in the GOOD has moved to line 11 in the BAD, and
is now below the "gecko_android" line (outside of the block for "gecko").


DJ-Leith

Fixed in 12.0.902, thanks.

Thanks, Giorgio. All is OK.


I have done some Tests, including:

A. On less frequently used Profiles (including some old test Profiles)

I did the 'semi-automatic' "Check for Updates" (as documented in the first post in this thread).
All were at "11.5.3rc1" or older.
All updated NoScript to "12.0.902".
This is what I hoped and expected would happen. So, they 'bypassed the broken 12.0.901' and are still in the 'RC channel'. Excellent.


B. On half a dozen Profiles that were 'stuck at 12.0.901'

I used https://noscript.net/getit/#devel to update these.

I have uMatrix on all my Profiles (I know it is no longer maintained but it still works).
As I am blocking '3rd party requests' in uMatrix I had to disable uMatrix to do the
"Install NoScript 12.0.902 on Firefox Desktop by simply clicking here." (on the getit page).
All Profiles updated NoScript from 12.0.901 to 12.0.902 (as expected).
I have re-enabled uMatrix on all these Profiles.


C. I have tested that 12.0.902 is checking secure.informaction.com for updates

I used some Profiles from 'Group A' [where I used the 'semi-automatic' "Check for Updates" method] and some from 'Group B' [where I manually updated using the getit page].

I again used the "Check for Updates" method (as documented in the first post in this thread).
As expected, all are now checking secure.informaction.com for updates.


DJ-Leith