Slate.com commenting failure

Jojo999 · Post by **Jojo999** » Wed Jan 13, 2016 9:29 am

I am unable to comment at Slate.com any longer and I suspect that NS has something to do with this.

I believe that the problem might have started occurring when I downgraded from FF 43.x to the v38.5.2 ESR release because I am tired of being an effective beta tester for Mozilla's stupid experiments with FF.

My ability to comment works fine in Chrome.

When I try to comment in FF, I get this rather useless error: "An error has occurred. Please try again".

I tried disabling Adblock Plus but that did not fix the problem.

I wanted to play around with NS scripts but I noticed something strangeness. I don't believe that I ever allowed ALL scripts to run in Slate, so when I noticed that there was no red bar through the NS "S" icon, I suspected something was wrong. When I moused over the "S" icon, I ONLY SEE ONE SCRIPT enabled, which is "Slate.com". All the other myriad other scripts that Slate throws at the user are missing! However, I can see them all under the Untrusted label. How they got under that label is a mystery to me.

See screenshot here:
https://drive.google.com/file/d/0B3aloI ... pudEE/view

Any help appreciated.

Edit: Updated with corrected link

Post by **barbaz** » Wed Jan 13, 2016 2:58 pm

Screenshot link just returns this:

Code: Select all

<HTML>
<HEAD>
<TITLE>Not Found</TITLE>
</HEAD>
<BODY BGCOLOR="#FFFFFF" TEXT="#000000">
<H1>Not Found</H1>
<H2>Error 404</H2>
</BODY>
</HTML>

Something got corrupted in your settings anyway. Check the value of about:config > noscript.forbidImpliesUntrust?

Do you have cascading permissions enabled? (NoScript Options > Advanced > Trusted)
If not, and if those entries in Untrusted show as "Allow [...]" and/or "Temporarily allow [...]": I would also suggest you go to NoScript Options > Whitelist and export the whitelist (as backup - this also exports your Untrusted list). If anything looks "off" in that Untrusted list, reset about:config > noscript.untrusted (it should go empty), and try again... does the problem recur?

Jojo999 · Post by **Jojo999** » Wed Jan 13, 2016 7:23 pm

barbaz wrote: Something got corrupted in your settings anyway. Check the value of about:config > noscript.forbidImpliesUntrust?

Do you have cascading permissions enabled? (NoScript Options > Advanced > Trusted)
If not, and if those entries in Untrusted show as "Allow [...]" and/or "Temporarily allow [...]": I would also suggest you go to NoScript Options > Whitelist and export the whitelist (as backup - this also exports your Untrusted list). If anything looks "off" in that Untrusted list, reset about:config > noscript.untrusted (it should go empty), and try again... does the problem recur?

I fixed the link in the original post. Sorry.

"about:config > noscript.forbidImpliesUntrust" = False

"Do you have cascading permissions enabled? (NoScript Options > Advanced > Trusted)" - Yes

Unclear what, if anything, I can change in NS settings.

As I said, everything was working fine until recently. I made no changes to NS in any way, shape or form. Only change I can recall was the change from FF 43.x to ESR 38.5.2.

Post by **Thrawn** » Wed Jan 13, 2016 10:11 pm

Jojo999 wrote:How they got under that label is a mystery to me.

That's because you have cascading permissions enabled (Options-Advanced-Trusted-Cascade top document's permissions to 3rd-party scripts). It means that if the top-level domain is enabled, everything is enabled, unless specifically marked as Untrusted.

If that's not what you intended, then you should probably switch it off.

InformAction Forums

Slate.com commenting failure

Slate.com commenting failure

Re: Slate.com commenting failure

Re: Slate.com commenting failure

Re: Slate.com commenting failure