InformAction Forums

"It took 2 restarts"... of Firefox, or your computer??

If you're experiencing this right now on Firefox, do this for the hotfix to immediately apply (it happened to me minutes ago on my main profile):

1. Open about:config
2. Turn app.shield.optoutstudies.enabled to true (if false)
3. Turn app.normandy.run_interval_seconds to 1

As soon as you can see all your add-ons coming back (it should happen right away), reset both preferences.

Can't resist a simple thank you post!.. NoScript is essential these days and this was a surprise just now.
Great to see a simple fix so promptly.

For FF 56, & even though a "fix" came through from Mozilla (surprisingly), it does not "fix" anything.
NoScript will not work without applying the "hack".

It is the same as it was before, 5.1.8.7rc4 is not signed.

Already did that (just changed seconds to 1, studies was set to true already) but still waiting for plugins to come back =S. Already restarted Firefox like 4 times and restarted pc once

GuestK wrote: ↑Sat May 04, 2019 9:37 pm Already did that (just changed seconds to 1, studies was set to true already) but still waiting for plugins to come back =S. Already restarted Firefox like 4 times and restarted pc once

If the hotfix is already shown in about:studies but still no extensions, either you removed them while trying to fix this (and you need to reinstall them) or that's an instance of this bug.

Starting in Firefox version 57, only extensions built using WebExtensions APIs will work. Its seems that this was being worked on sometime ago, but confusing to look at forum. Is this being updated to work now, or do I need to find something else??? I've always trusted NoScript and although frustrating to use at times, felt it was well worth the effort! Simply, is it being revised and how long need I wait???

Just wrote re deactivation a few minutes ago. Then noticed the fix w/about:config. The first line was correct. The 2nd I changed to "1". Clicked OK. The change happened quickly. <G> Went back and changed the 1 to original number and still working ! Great. Haven't restarted FireFox as yet; hoping the fix will stay fixed.... Tks much, Admin!

Well, like a dumb-a$$ , I didn't write down the original value. I think it was 12xxx but am not sure, so I just entered "12000". Could somebody please tell me what the original value is?

Skeezix wrote: ↑Sun May 05, 2019 1:23 am Well, like a dumb-a$$ , I didn't write down the original value. I think it was 12xxx but am not sure, so I just entered "12000". Could somebody please tell me what the original value is?

21600

Thank you for the instructions on how to set studies on and especially the reminder to turn it of again, worked like a charm, on my slow connection it took only a few minutes. Firefox simply suggests turning it on an waiting a few hours/days!? And is not telling people that they could turn it back off, you're a life saver again, happy to have your wonderful add on back on again!

Glad to find this discussion, but I believe it should be clearly linked from the noscript.net home page.
A lot of people are pretty lost right now.

Giorgio Maone wrote: ↑Sat May 04, 2019 8:54 pm If you're experiencing this right now on Firefox, do this for the hotfix to immediately apply (it happened to me minutes ago on my main profile):

1. Open about:config
2. Turn app.shield.optoutstudies.enabled to true (if false)
3. Turn app.normandy.run_interval_seconds to 1

As soon as you can see all your add-ons coming back (it should happen right away), reset both preferences.

While this works well on PC..
I see this now on mobile and wonder neither option is available in about:config ..
is there an alternate solution then for mobile Firefox on Android?

-MelVin- wrote: ↑Sun May 05, 2019 2:03 am

Skeezix wrote: ↑Sun May 05, 2019 1:23 am Well, like a dumb-a$$ , I didn't write down the original value. I think it was 12xxx but am not sure, so I just entered "12000". Could somebody please tell me what the original value is?

21600

Or, as with any about:config preference, you can just use the "Reset" command (context menu item) to restore its original value.

Speaking of about:config, on Firefox for Android there's no hotfix, but at least on the Beta which I'm using you can turn off signature verification just like you do in the Tor Browser (xpinstall.signatures.required=false).

Giorgio Maone wrote: ↑Sun May 05, 2019 10:08 am Speaking of about:config, on Firefox for Android there's no hotfix, but at least on the Beta which I'm using you can turn off signature verification just like you do in the Tor Browser (xpinstall.signatures.required=false).

and thanks again that worked well for Android.

I wonder still why and how this happened.. and why Firefox doesn't recognise NoScript is a large critical part of what makes Firefox a better user experience.