Upgrade from NoScript V 2.x to 5.x

[planet222]

Good Afternoon,
I am wondering. I just updated Fx ESR and NoScript from 2.x to 5.x on two user accounts. I didn't update NoScript, just Fx on a third account and was able to securely log onto a site without problem. On the other that was updated to Ver 5.x, initially I got an error, unable to access site in small text in upper left corner. I ended up needing to allow all scripts before being able to log on. The only site I could see needing scripts enabled was google-analytics which I typically don't allow. Is there a reason V 5.x would need this enabled as V 2.x didn't?
Thank you.

[barbaz]

The google-analytics surrogate script was changed in 5.0. Does it work with NoScript 5.x if you replace about:config > noscript.surrogate.ga.replacement with its value from NoScript 2.9.5.3?

[planet222]

The google-analytics surrogate script was changed in 5.0. Does it work with NoScript 5.x if you replace about:config > noscript.surrogate.ga.replacement with its value from NoScript 2.9.5.3?

No. I changed the value for noscript.surrogate.ga.replacement in V 5 to the 2.9.5.3 version. Got the same error message that I couldn't access site in the tiny text in top left corner. It would only let me log in if I allowed google-analytics scripting via NoScript.

[barbaz]

Is it possible to reproduce the problem without login and without entering random invalid credentials?
If so, can you please share the link to the site?

[planet222]

Is it possible to reproduce the problem without login and without entering random invalid credentials?
If so, can you please share the link to the site?

No it won't reproduce without log on. Sorry.

[barbaz]

How much JavaScript knowledge do you have?

I ask in case you know enough JS for us to guide you in the process of trying to fix the surrogate.

[planet222]

Sorry. Noop.

[planet222]

barbaz, on the account that I've not upgraded to V5, is there any harm in not upgrading?

Has V5 forked towards WebExtensions? I've read some about it awhile ago.

[barbaz]

Sorry. Noop.

That's OK, there is still one more thing we can try. If you blank out about:config > noscript.surrogate.ga.replacement, does the page work without Allowing google-analytics?

barbaz, on the account that I've not upgraded to V5, is there any harm in not upgrading?

That partially depends on your usage of NoScript. See the changelog for list of the features and bugfixes you're missing out on.

[barbaz]

Has V5 forked towards WebExtensions? I've read some about it awhile ago.

Not really. It's true that V5 has an embedded WebExtension. But V5 currently does not require WebExtensions at all.

For more info see viewtopic.php?f=8&t=22524

[planet222]

When you say blank out, do you mean leave the value empty of code?

[barbaz]

Correct. Right-click the entry > Modify, delete everything and then click OK.

[planet222]

I deleted the value and tried to log in and got the error again.

[barbaz]

Actually one last thing. If you reset that surrogate back to default, and downgrade NoScript to 2.9.5.3, does it work again?

Old NoScript @
https://addons.mozilla.org/addon/noscript/versions
*or*
https://noscript.net/feed?c=100&t=a

[planet222]

I know I'm sounding paranoid now, but if I reinstall an older version, isn't this, in part anyway, what was driving WebExtensions? I haven't installed any new extensions in years. I've used the extensions internal updaters only.