InformAction Forums

My Firefox can't detect the 2.5.6 update of NoScript. I've tried installing an old version in AMO (2.5.4) in a new Firefox profile, result is that NoScript latest version is not downloaded after checking for updates in Add-ons Manager. I've tried installing old versions of other add-ons and update is working fine.

I'm seeing the same here, on a development version of 2.5.5. No big deal, I can just install directly from noscript.net, but even though a dev version of 2.5.7 is out, it wasn't detected automatically.

I just noticed a mis-numbering of part of the changelog, which may affect this. I PM'd Giorgio about that issue, and asked him to reply here also. Perhaps 2.5.6 hasn't yet reached AMO, which is common.
It's morning in Italy now, so hopefully ...

btw, this browser had no trouble self-detecting 2.5.6rc2 and notifying me that it was available. (What 2.5.7 dev build, Thrawn?)
Do we all have Fx set to auto-notify on add-ons and updates? (I prefer not to auto-install, but that's just MHO.)

ETA: OK, found the 2.5.7rc1 at latest development build. I expect that this version also has not yet made it to AMO.
This is common, for there to be a lag between Giorgio hosting it on his site (https, btw) and AMO getting it into either stable channel or dev channel, as appropriate. Should be fixed soon -- there were several changes in a short time span.

The changelog problem was just a typo, fixed now, and the dev build should be on the AMO beta channel tomorrow or so. Thank you.

Unfortunately, this issue continues.

Useful URLs

Recent all builds from noscript.net
http://noscript.net/feed?c=200&t=a

NoScript Versions AMO
https://addons.mozilla.org/en-US/firefo ... /versions/

In the last week I have attempted to Update NoScript on more than 20 Profiles.
[3 PCs (2x Windows 7, 1x Vista), 9 Windows Users (4 with Admin rights, 5 'non Administrators')].

Like Thrawn, Tom T. and Giorgio Maone I can (and have) used the Recent all builds from noscript.net
to 'manually do the Updates' and I thought the issue was that the XPIs had not been published at AMO.

However, AMO have had Version 2.5.7rc3 (Released October 1, 2012 529.5 KB) for at least 36 hours and
the 'normal method of updating' is still not working.

STR

1. Create a new profile http://kb.mozillazine.org/Profile

2. Use either Recent all builds from noscript.net or NoScript Versions AMO (see URLs above)
to install an older RC (Dev) version of NoScript e.g. NoScript 2.5.7rc1 (24 September 2012 22:50).

3. 'Fx Menu', Tools, Add-ons and 'use the cog wheel' to force a "Check for Updates" of the Add-ons.

No update are found.
'Expected behaviour' would be to find Version 2.5.7rc3, do an Update (including a Restart of Fx).

I have tried this on Fx 15.0.1 and Aurora (17.0a2).

DJ-Leith

Post to be continued ...

Further investigation:

I have repeated the STR.
Try OLDER NoScript versions to see if I could identify where the issue started.

NoScript 2.5.6rc2 (24 September 2012 10:04)

'splash URL' on installing NoScript "Congratulations, you've got the latest version."
However, this is ambiguous because it DID do an Update when I asked it to.

continued (splitting up post because of the anti spam filter)...

On another new test Profile

NoScript 2.5.6rc1 (22 September 2012 22:47)
'splash URL' on installing NoScript "Congratulations, you've got the latest version."
BUT it DID do an Update when I asked it to.
'splash URL' on NoScript Update continued...

So, I now think
NoScript 2.5.7rc1 (24 September 2012 22:50) and newer
are NOT detected as being 'no longer the latest RC' and so the
'normal NoScript Update' method is failing.

This thread was started 11 hours later (Tue Sep 25, 2012 10:21 am).

Other information:

I also think nitou, who posted using Firefox 3.6.28 (at Mon Oct 01, 2012 1:37 am), in
Bar "Follow the redirection" hide the bar auto-reloading
http://forums.informaction.com/viewtopi ... 35&p=43411
was also trying to say that s/he could NOT update from NoScript 2.5.7rc1.

DJ-Leith

I have now had some sleep and I have done some more tests.

First, it is normal for Giorgio to make new RCs. He works so hard on our behalf.
It can take some time (sometimes less than an hour but sometimes several days) for these to
be published at AMO. Until they are at AMO you'll have to get them from noscript.net.

What is different, in this case, is that AMO (see the URLs posted above) has been showing
2.5.7rc3 for more than 50 hours.

Another new Profile

Try NoScript 2.5.5rc1 (12 September 2012 11:42) to document 'normal Update' behaviour.

The 'NoScript Install result URL is': This page says:
"Looks like you are running an older version (2.5.5rc1), probably because latest version is not published on
addons.mozilla.org yet.
You are strongly encouraged to
install latest development build"

At this point, doing STR Step 3, leads to Noscript doing an Update (from AMO).

The 'NoScript has done an Update result URL' is: This NoScript Release Notes page says:
"Congratulations, you've got the latest version."

All of this is 'normal' / 'expected'.

continued...

Another new Profile (to recheck some of my results).

This time I tried 2.5.7rc2.
This gave results very similar to 2.5.6rc1 and 2.5.6rc2 (see posts - above).

The 'NoScript Install result URL is': This page says:
"Congratulations, you've got the latest version."
To me, this seems ambiguous.
When I did STR Step 3, Noscript did an Update (from AMO)!

Another new Profile, to check 2.5.7rc1.
This still failed to Update.

Revised Conclusion:

NoScript 2.5.5rc1
This is 'detected at noscript.net' as an old version (when I installed it).
Doing a 'normal Update' (STR step 3) it Updates to the newest version (2.5.7rc3).
Very good.

NoScript 2.5.6rc1, NoScript 2.5.6rc2 and NoScript 2.5.7rc2
All three are 'detected at noscript.net' as
"Congratulations, you've got the latest version."
However, all 3 will Update, from AMO, using the normal method to 2.5.7rc3.
While I was puzzled, at first, the main point is that you can
Update these without having to 'get an XPI by hand from noscript.net'.

2.5.7rc1 is the ONLY version that is NOT 'doing a normal Update from AMO'.

DJ-Leith

Giorgio is aware of this, I have emailed him on it and I am sure it will be fixed as soon as it is feasible. Everyone just chill and it will be back to normal soon enough I am sure.

I believe the problem is (oddly) that 2.5.7rc1 has never been published on AMO.
For some (very strange) reason, if you've got a version installed which is not on AMO, you don't get any automatic AMO update.
Or, I believe to recall from a previous similar issue, rather than not getting any update, you're treated as you were in the stable channel, even though the version number you've got uses the beta channel convention (which makes slightly more sense).
At any rate, I've just uploaded 2.5.7rc1. Could you check whether this actually fixes the problem?

http://noscript.net/getit#devel
Here is no 2.5.7rc4 available. Firefox got this half an Hour ago
Any Comments to this?
TX

Boersenfeger wrote:http://noscript.net/getit#devel
Here is no 2.5.7rc4 available. Firefox got this half an Hour ago
Any Comments to this?
TX

Just forgot to update the page

Thx... for this and for ur great work...
HAGD
Bo