Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Lolu chungechunge lwabekwa kunqolobane. Uyacelwa ubuze umbuzo omusha uma udinga usizo.

Well, it's happened again. The 40.0 upgrade disabled a bunch of add-ons including Dashlane. I'll be off to Chrome at least until these issues are fixed.

  • 3 uphendule
  • 54 zinale nkinga
  • 2322 views
  • Igcine ukuphendulwa ngu James

more options

The 40.0 upgrade disabled an unusual number of add-ons. On my browser, they are Bing Fastest Search NoScript Office Launcher Qualsys Browser Check Readability Skype Click-to-Call WebRank SEO Toolbar Webroot Filtering Extension

As I understand it, I would have to contact each of the add-on producers to ask them to restore their Firefox verification. Instead, I'll do what I have done in the past and go over to Chrome. This disabling has greatly affected my browsing experience, especially for business. Firefox is the only browser I have encountered that disables add-ons and extensions almost every time it is updated. I love Firefox but this is getting old. I'll seriously consider staying on Chrome.

Isisombululo esikhethiwe

Two potential issues with Firefox 40 and add-ons getting disabled.

The first is the 'normal' reoccurring issue where the extension developer set the maxVersion for the Release version, and Beta is one version higher. IOW, that developer only "supports" Release versions and not a Pre-release version such as Beta. Nothing that can be done about that except to use the Release version [currently Firefox 39.0] when you're using add-ons that you rely upon. A very limited number of extensions have Beta versions available for pre-release versions like Beta; and a few even "support" the Nightly, WD/Aurora, and Beta channels. Plus, if an extension is created with Binary components it has to be "versioned" correctly or it's automatically disabled, and requires an update to be installed. Mozilla is very strict with Binary components in add-ons, which some browsers don't allow to be installed, at all. Binary components can pose a security risk, thus Mozilla strictness.

The 2nd issue may involve Extension Signing. https://blog.mozilla.org/addons/2015/02/10/extension-signing-safer-experience/ Although that may have been postponed until Firefox 41. https://wiki.mozilla.org/Addons/Extension_Signing Currently I am not running a Beta version on this PC, so I have no first hand knowledge of what is happening on the Beta channel.

Take a look at about:addons and see if any of those disabled extensions show -signed which is how you can tell whether a p[articular extension it is signed or not. For some reason NoScript seems to be one of the few very popular extensions that are hosted at the official Addons.Mozilla.org website that is yet "-signed", which surprises me. The only one that I have out of 21 total extensions that is hosted at AMO that hasn't been "updated" for Extension Signing as of yet. The other extensions that you mentioned I don't believe are available from AMO and I have no use for them, so I don't know if any of those have been "signed" yet or not.

Funda le mpendulo ngokuhambisana nalesi sihloko 👍 1

All Replies (3)

more options

Isisombululo Esikhethiwe

Two potential issues with Firefox 40 and add-ons getting disabled.

The first is the 'normal' reoccurring issue where the extension developer set the maxVersion for the Release version, and Beta is one version higher. IOW, that developer only "supports" Release versions and not a Pre-release version such as Beta. Nothing that can be done about that except to use the Release version [currently Firefox 39.0] when you're using add-ons that you rely upon. A very limited number of extensions have Beta versions available for pre-release versions like Beta; and a few even "support" the Nightly, WD/Aurora, and Beta channels. Plus, if an extension is created with Binary components it has to be "versioned" correctly or it's automatically disabled, and requires an update to be installed. Mozilla is very strict with Binary components in add-ons, which some browsers don't allow to be installed, at all. Binary components can pose a security risk, thus Mozilla strictness.

The 2nd issue may involve Extension Signing. https://blog.mozilla.org/addons/2015/02/10/extension-signing-safer-experience/ Although that may have been postponed until Firefox 41. https://wiki.mozilla.org/Addons/Extension_Signing Currently I am not running a Beta version on this PC, so I have no first hand knowledge of what is happening on the Beta channel.

Take a look at about:addons and see if any of those disabled extensions show -signed which is how you can tell whether a p[articular extension it is signed or not. For some reason NoScript seems to be one of the few very popular extensions that are hosted at the official Addons.Mozilla.org website that is yet "-signed", which surprises me. The only one that I have out of 21 total extensions that is hosted at AMO that hasn't been "updated" for Extension Signing as of yet. The other extensions that you mentioned I don't believe are available from AMO and I have no use for them, so I don't know if any of those have been "signed" yet or not.

more options

Thanks for the excellent information! I'm going to turn off the beta updating and wait for the full version. That seems to be a likely cause. Will also look into signing.

more options

The Release currently has 39.0 www.mozilla.org/firefox/all as it will be awhile until Firefox 40.0 is on Release channel.

You were likely using one of the seven Beta builds of Firefox 39.0 before and when 40.0b1 was available yesterday it updated to 40.0b1 since you are on Beta channel and not the Release channel.