Sci2 not working (how to troubleshoot?)

[terminalmage]

With NoScript enabled, http://sci2.tv does not load. This happens irrespective of whether or not script blocking is enabled. How would I find out what was blocked, and craft an exception for it?

[Thrawn]

Which sites have you allowed/blocked?

[terminalmage]

Not sure what you mean by that. Do you mean my whitelist? I have tons of sites on it, but like I said earlier, it doesn't matter; I can globally allow scripts and the site still doesn't work.

I've also disabled all extensions, then enabled NoScript, to isolate the issue and confirm that NoScript is what is keeping the site from loading.

[barbaz]

When the site doesn't load, any related messages in the Browser Console? (Ctrl-Shift-J)

[terminalmage]

Actually, it looks like the problem is that I marked facebook.net as untrusted, and it was still being blocked even though scripts were enabled globally. Ugh. Guess I'll have to use this technique to allow it just on sci2.tv.

[barbaz]

Um, there's supposed to be a surrogate script for facebook.net, so that sites don't break if it's forbidden/untrusted...

EDIT Confirmed the problem. Looks like the surrogate needs updating...
EDIT2 Actually all of facebook, twitter, and ga surrogates may need updating to work with this site...

[terminalmage]

Do you have more information on this? I'm not familiar with it.

[barbaz]

Their requirejs script is throwing errors if any 3rd-party script isn't loaded succesfully.

What's supposed to happen is that NoScript should run "fake" scripts in the place of those blocked scripts, keeping sites that depend on the real scripts happy (meaning, the site works properly) while not actually doing anything nasty like the real scripts would. If you want to view these surrogates go to about:config and filter for "noscript.surrogate.".

[terminalmage]

Oh cool, thanks for the info.

Is this something that will need to be fixed with a new release of NoScript, or can NoScript update these surrogate scripts by itself?

[barbaz]

Is this something that will need to be fixed with a new release of NoScript,

This, assuming you didn't modify the default surrogates.

[terminalmage]

I did not. Until a few mins ago, I didn't know this sort of thing even existed

Thanks for the info!

[terminalmage]

Oh, it looks like google-analytics.com is also affected. Also, in about:config, there is only one surrogate there, for adfly.

[barbaz]

in about:config, there is only one surrogate there, for adfly.

Weird, they're all there for me...
Check the sticky for a full list of sites for which NS runs surrogate. (It's over a year out of date, but I've just requested and sent an update, so it should be current again within the next few days.)

If you're really seeing only the one surrogate you should do Standard Diagnostic because something is very wrong.

[terminalmage]

I wonder, are these surrogate scripts backed up and restored along with the rest of the NoScript settings? I switched to a new laptop last year, and backed up my settings, then restored once I had installed NoScript on my current laptop.

[barbaz]

They are part of NoScript's default preferences so you only have to install NoScript to get them.