This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

সহায়তা খুঁজুন

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.

আরও জানুন

Why does the 39.0.3 Firefox update not take existing Add-Ons into account? The most recent update disabled several, despite their regular use.

  • 7 উত্তরসমূহ
  • 3 এই সমস্যাটি আছে
  • 2 দেখুন
  • শেষ জবাব দ্বারা UnusuallyClueless

more options

Unlike one other poster to this forum, I do not have a complex set of Add-Ons for Firefox. On August 6, when I was prompted by Firefox to update, I trustingly presumed any Firefox programmer would take into account existing Add-Ons. All but two of my several Add-Ons were disabled.

Unlike one other poster to this forum, I do not have a complex set of Add-Ons for Firefox. On August 6, when I was prompted by Firefox to update, I trustingly presumed any Firefox programmer would take into account existing Add-Ons. All but two of my several Add-Ons were disabled.

All Replies (7)

more options

Hi, unfortunately the developers of add-ons do not always keep up with Firefox's updates, which may sometimes be because an update has been rushed through for security reasons, as is the case with 39.0.3.

It is worth keeping an eye on any add-ons that are affected, and looking out for updates in due course.

If your question is resolved by this or another answer, please take a minute to let us know. Thank you.

more options

Granted, developers are responsible for keeping track of the Firefox environment, with appropriate help from the Firefox team, itself.

However, my complaint is almost the opposite-- Firefox management should make sure its updates at least accommodate currently installed user Add-Ons, and keep these active through the update process.

If Add-Ons are outdated, of course, the user can take charge, but it is possible to automate even that process. At one point, Firefox updates were much smoother than now, and actually notified users in advance that certain Add-Ons needed to be updated and even helped update the outdated Add-Ons.

In any case, the alternative is chaos-- which is what prevails, now.

As a direct result of its unfocused update Policy, the Mozilla Firefox team should not be surprised to find users do not respond to update notices with the alacrity they should-- all because they are exasperated with Firefox updates which wreck everything.

more options

Specifically, which add-ons were rendered incompatible or are not incompatible with the Firefox 39.0.3 update?

more options

'"Extensions Disabled by the 39.0.3 update--'"

Mozilla Archive Format extension for Firefox (signed) Clean Links (signed) Fire FTP (signed) Session Manager Web of Trust TroubleShooter (signed)


Extensions left active by the 39.0.03 update--

Tree-Style Tab (signed) Open Link in New Tab (signed)

alphaa10000 দ্বারা পরিমিত

more options

Try to rename (or delete) the compatibility.ini file in the Firefox profile folder to reset the profile.

You can use this button to go to the current Firefox profile folder:

If you see disabled or not compatible extensions in "Firefox/Tools > Add-ons > Extensions" then click the Tools button at the left end of the Search bar to check if there is a compatibility update available.

more options

Checked the FF profile folder, deleted compatibility.ini, and returned to the FF / Tools / Add-ons / Extensions screen to check for updates or any indicators of disabled or incompatible extensions, but found none.

Rebooted FF, found no changes on the Extensions screen, but found a reconstituted compatibility.ini, updated to today (August 8).

more options

Mods, please delete this. Thanks!

UnusuallyClueless দ্বারা পরিমিত