http://forums.mozillazine.org/viewtopic.php?f=38&t=3049775
http://forums.mozillazine.org/viewtopic.php?f=38&t=3049746
The fix suggested didn't work for me.
http://forums.mozillazine.org/viewtopic.php?f=38&t=3049759
"It takes a while longer for the portable apps versions to upgrade as John Haller and his team need the source code from Mozilla.
Although I'll check their forums as soon as I leave here.. In the meantime...stay off strange websites"
See my posts as Mudder, fingers too sore for re-typing.
Visit the Community page
Join our forums
Subscribe to our email newsletter
Subscribe with RSS
Follow us on Facebook
Follow us on LinkedIn
Follow us on Twitter
Follow us on Mastodon
Follow us on BlueSky
It looks like for now anyway, Mozilla has disabled signature requirements or something. I have 2 installs of Firefox, I had my addons disabled for a few hours on my primary display. I needed to do the re-enable telemetry and studies tweak, close then re-open Firefox - wallah, everything began to reappear. I opened my second Firefox install on my second display (large flat panel tv), same version of Firefox... I did this about an hour later, by then Mozilla made some changes so the second install needed no attention, everything was in place as if nothing happened. So I suppose some of you waking up may have dodged a bullet, but for many millions of users the last few hours were quite discomforting, having all your addons disabled for no apparent reason.
All hail the kings of the digital world, thank you for making our decisions for us.. you have our best interest in mind (I'm sure) every time you tell us what we can or cannot do, say, think, wear, believe, eat, drink, read, vote on, speak about...
1. Clarified that the Studies fix applies only to Desktop users of Firefox distributed by Mozilla. Firefox ESR, Firefox for Android, and some versions of Firefox included with Linux distributions will require separate updates. (May 4, 12:03 EST)
2. We’re aware that some users are reporting that their extensions remain disabled with both studies active. We’re tracking this issue on Bugzilla in bug 1549078. (May 4, 12:03 EST)
3. Clarified that the study may appear in either the Active studies or Completed studies of “about:studies” (May 4, 12:10 EST)
4. Updated the post to clarify that deleting extensions can result in data loss, and should not be used to attempt a fix. (May 4, 12:58 EST)
5. Temporarily disabled commenting on this post given volume and duplication. They’ll be re-enabled as more updates become available. (May 4, 13:02 EST)
6. There are a number of work-arounds being discussed in the community. These are not recommended as they may conflict with fixes we are deploying. We’ll let you know when further updates are available that we recommend, and appreciate your patience. (May 4, 15:01 EST)
For more up-to-date updates, see below:
https://blog.mozilla.org/addons/2019/05/04/update-regarding-add-ons-in-f...
https://discourse.mozilla.org/t/certificate-issue-causing-add-ons-to-be-...
https://twitter.com/mozamo
Well, in deference to point 6, I'm returning the boolean value mentioned in the first 'fix' from false back to true, while I wait for John and his crew to issue 66.0.4 for us.
https://news.ycombinator.com/item?id=19826903
Confirmed working on the Portable Apps version. It's the fix Mozilla are deploying.
Don't forget to backup 'data' folder just in case.
Mozilla fixed this issue with the release of 66.0.4 which has just been pushed out.
Sometimes, the impossible can become possible, if you're awesome!
I will remember you and share when I get win the lottery, or when Ontario sends me my Trillium benefit.
Posted at moxillazine;
Hip-hip-hooray! Mr. Haller and his team got 66.0.4 out to users of FF portable and my extensions are back!
Are you planning on updating Portable ESR with the fixed 60.6.2 version?
Cheers,
Fred
You can report outdated apps and check their progress here: https://portableapps.com/development/outdated
Sometimes, the impossible can become possible, if you're awesome!
At the time I posted the question Mozilla had released fixes correcting the signing certificate problem to both the current Firefox release (66.0.4) and Firefox ESR (60.6.2). At the time of the post Portable apps had updated the current Firefox release but not the ESR. I was, in context of this thread, asking if the certificate fix for the ESR version was happening. I see that portable Firefox ESR is now at 60.6.2 so obviously it was in the works. How about you just saying that, yep, ESR would get the fix. Your reply wasn't helpful.
Fred
In the context of the way we work, it's just another outdated app like every other outdated app. It's just another version release from my perspective, so it gets built and pushed out like all other Firefox versions. When you posted, the Outdated App thread had an entry that said "Mozilla Firefox ESR 60.6.2 (John built, mirroring...)"
Sometimes, the impossible can become possible, if you're awesome!
Latest update from Mozilla:
Source: https://bugzilla.mozilla.org/show_bug.cgi?id=1549604#c53
Temporary fix to enable extensions/add-ons while you wait for official Mozilla's fix:
"appDisabled":truewith"appDisabled":falseand replace"signedState":-1with"signedState":2in the file called extensions.json using any text editor of your choice. Save and set the file permission to read only.Mozilla has released an extension to fix the expired intermediate certificate issue for Firefox 52-56. You can remove the extension after it has downloaded the new intermediate certificate to your existing Firefox portable. To verify it has successfully downloaded the new intermediate certificate, open Browser Console (Ctrl+Shift+J on Win and Linux, Cmd+Shift+J on Mac) and look for:
WebExtensions: new intermediate certificate addedAlternatively, if you don't want to install the above extension on your existing Firefox portable, you can install the extension on a clean install of Firefox 52-56 portable and then export and import the new intermediate certificate into your existing Firefox portable.