[FIXED] 10.1.9.3 broke media sites

[ZeppMan217]

The sites say that JS is disabled, even though everything is allowed in NoScript. Tested with youtube.com, twitch.tv, and imgur.com - all broken. Turning off NS entirely restores site functionality.

[Giorgio Maone]

Could you please use NoScript Options>Export (and possibly send me your configuration file), then NoScript Options>Reset and check whether it fixes Youtube (it should work out of the box)? Thanks!

[ZeppMan217]

Could you please use NoScript Options>Export (and possibly send me your configuration file), then NoScript Options>Reset and check whether it fixes Youtube (it should work out of the box)? Thanks!

Resetting to default fixes it. Importing the settings back breaks it again. Any chance of being able to salvage the saved permissions? And how do I go about finding the location of the config?

[0xffff]

Same here. Since the update to 10.1.9.3 my configured per-site permissions do not work any longer. The icon shows that all scripts are blocked, when I open the menu the configured permissions are shown correctly..but they do not have any effect.
Since I have al lot of site specific permissions resetting and reconfiguring them all is something I would like to avoid.

[0xffff]

Problem solved!
The cause is an invalid empty entry in the per-site permissions: "§:"
Steps to solve:
1. Export configuration
2. Reset configuration
3. Open config file with a json-capable editor (i.e. notepad++) and remove the entry "§:" and save.
4. Import the config file
5. Works like a charm..

I saw the empty entry in the UI before (at the end of the list) but i thought it was an editable placeholder for a custom entry.

[ZeppMan217]

Problem solved!
The cause is an invalid empty entry in the per-site permissions: "§:"
Steps to solve:
1. Export configuration
2. Reset configuration
3. Open config file with a json-capable editor (i.e. notepad++) and remove the entry "§:" and save.
4. Import the config file
5. Works like a charm..

I saw the empty entry in the UI before (at the end of the list) but i thought it was an editable placeholder for a custom entry.

That did it!

[Oasiz37]

DON'T DO THAT!!!

My setup is now completely broken. Exported-> Edited->Reset ->Import = NOTHING WORKS!

An attempt to re-import broken config didn't fix anything, still broken. UI shows scripts globally enabled, and this can't be changed anymore. Sites are still broken.

[Giorgio Maone]

DON'T DO THAT!!!

My setup is now completely broken. Exported-> Edited->Reset ->Import = NOTHING WORKS!

An attempt to re-import broken config didn't fix anything, still broken. UI shows scripts globally enabled, and this can't be changed anymore. Sites are still broken.

Could you please send me this configuration file? email is shown here
Thanks!

[therube]

(I'll note that some time back, I noted §, not that there was an issue with it at the time, but a search will not find it?

Thinking that "§" will have nothing to do with the issue, more that people are now looking & happen to be seeing this, & seeing something "odd" associating that oddity with an "issue", where it is not?

An older export, compared to current, only has the addition of 'highContrast' & older had some entries in 'custom', but is otherwise the same.
I rarely make any "permanent" domain setting changes (Custom), only to the extent of removing some defaulted domains; yahoo & google.


And then also, I'm not able to duplicate the current issues mentioned with 10.1.9.3.)

[Giorgio Maone]

I think I know exactly what's going on (a crossing between two bugs in two different PAST versions biting together now).
I suspect auto-allowing top level sites has something to do with that, too.
I'm about to release a fix 10.1.9.4 later today, but in the meanwhile NoScript Options>Reset should fix the issue.
Please notice that the only entry to be removed is the "§:" (without any domain attached) one.

[therube]

So what, you're saying that there is an Allowed domain that is solely "§:" ?

Does that "domain" show up in Per Site Permissions?
IOW, can you remove it from there?

If not, the only "reasonable" option is to do a Reset, which (seemingly) would reset it.
Though that reset resets one's "customized" settings, they are lost.
So that means that one needs to first Export, manually remove the rogue entry, then manually import...

IOW, there is no user friendly method to fix things if things go awry.
As in you can no longer open prefs.js, delete one line, & be done.
Sigh.


Perhaps a Reset should automatically prompt to Export (with option to dismiss)?
[You are about to Reset...
Do you want to Export prior to... Y/N?]

[Giorgio Maone]

Does that "domain" show up in Per Site Permissions?
IOW, can you remove it from there?

I think I've seen it there, but I've had no time to check.

IOW, there is no user friendly method to fix things if things go awry.
As in you can no longer open prefs.js, delete one line, & be done.

You can use NoScript Options>Advanced>debug and use the raw policy editor to a similar effect, though.

[ZeppMan217]

If you do a reset and export the default settings, there's no empty "§:". That's basically how the reset fixes the problem - by removing the empty "§:" line.

[Giorgio Maone]

Please check latest development build (or stable 10.1.9.4):
v 10.1.9.4
=============================================================
x Prevent total breakages when policies accidentally map
to invalid match patterns
x Internal messaging dispatch better coping with multiple
option windows
x Avoid multiple CSP DOM insertions

[ZeppMan217]

9.4 works fine on my end.