Firefox - Workarounds for Add-On incompatiblities with Firefox updates

Various methods for getting incompatible Firefox Add-Ons to work in newer browser versions

   Information
Firefox Add-Ons depend on the developer of the Add-Ons to keep them up-to-date with current and future Firefox browser versions. There are some Add-Ons that that we may use and depend on that are poorly kept up-to-date with new and future Firefox versions (Aurora/Beta/Nightly builds) by the developer/s.

Most of the time (but not always), the Add-Ons will work just fine in a new Aurora or Beta build even though the Add-On on addons/mozilla.org states only up to a lesser browser version than you want to use. Say you want to use a Firefox 6 Beta build, and the Add-On only states up to Firefox 5.0*.

Firefox will run the Add-On compatibility check when updating the browser and disable any Add-Ons that it finds are incompatible. While this may be necessary as the Add-Ons may truly have incompatibility issues, it may also not be really necessary as the Add-On might work just fine in a newer version.

This will show you a few ways to workaround the compatibility check and get the Add-On to work in the new browser version.

   Warning
These methods are at your own risk. The Add-Ons may or may not work, or possibly in rare cases cause corruption in your Firefox profile. So make a backup / backup of your last known good Firefox profile before you do it if you're unsure.





OPTION ONE

Check the developers website



Some Add-ons will have an newer updated version on the developers personal website weeks or even months before they show up on addons/mozilla.org. Best to check the devs website first (if they have one) to see if there is an newer version than at addons/mozilla.org. You can usually find the devs website link on Mozilla addons page.




OPTION TWO

Use an Add-on



Use the Add-on Compatibility Reporter add-on from Mozilla. It will enable the disabled incompatible add-ons. You can also test them out and report incompatible add-ons to Mozilla.

Or use the Nightly Tester Tools add-on. It has several features.




OPTION THREE

Use about:config



This will just disable the browser from auto checking if any add-ons are incompatible or not, allowing them to install.

Type about:config in Firefox's address bar and press Enter. Click OK for I'll be Careful, I promise.

Right-click on an empty space in about:config, and create New-Boolean value.

1.JPG

Enter extensions.checkCompatibility and click OK.

2.JPG

In the True or False value popup that pops up next, enter False, then OK.

3.JPG

Restart the browser.




OPTION FOUR

Edit the version number in the install.rdf file



Edit the specific Add-ons install.rdf file.

Navigate to
Computer/Users/YourUserName/AppData/Roaming/Mozilla/Firefox/Profiles/Profilename/extensions.

The add-ons will most likely be named with numbers followed by the file extension .xpi.

Example: {1AFDJD34-753F5-4cHk-08334445533}.xpi

You'll need to find out which one of those is the add-on you want to edit. You can open and find out which one is which and also edit the .rdf file with a file archiver like 7-Zip.

(The install.rdf file will have the name of the add-on in it somewhere.)

Right-click on the add-on you want to edit, and in the context menu go to 7-Zip/Open archive.

4.JPG

Right-click on the install.rdf file and choose Edit.

5.JPG

Near the bottom it will show a minversion/maxversion. Enter in the browser version number you want it to work with (if it said 5.0 and you want it to work with FF 6, put in 6 where the 5 was.

6.JPG
7.JPG

Go to File and Save in notepad. Then click Yes to save in archive.

8.JPG


Restart the browser. The add-on should now be enabled.


That's it.

Airbot
 
Last edited:
Nice tutorial Airbot ! ;)
 

My Computer

Computer type
PC/Desktop
Computer Manufacturer/Model Number
Custom Build
OS
Windows 10 Pro x64
CPU
Intel Core i5 4440 @Stock
Motherboard
Gigabyte Z97 D3H
Memory
4 x 4GB HyperX Fury DDR3
Graphics Card(s)
Gigabyte GTX 1050Ti O4G
Sound Card
Integrated
Monitor(s) Displays
Dell P2417H
Screen Resolution
1920 x 1080
Hard Drives
Samsung EVO 850 120GB / Toshiba DT01ACA050 1TB 7200prm 32MB
PSU
Riotoro Onyx 750W
Case
NZXT H500 Black-Red
Cooling
Stock CPU + NZXT 120mm + 2x120mm red fans
Keyboard
Modecom Volcano Lanparty
Mouse
Asus ROG Gladius / DeepCool E-Pad Plus
Internet Speed
DOCSIS 50/3 Mbit
Browser
Google Chrome
Other Info
Asus K55VJ(i5 3210M, GT635M / 2GB, 8GB DDR3, 500GB HDD)
Use the asterisk

Make a backup of the rdf file before attempting to edit it! :geek:

You can often get away with replacing the entire FF version number with an asterisk (see gif below).

Click on thumbnail for animation.
FF Edit RDF 01.gif

I have edited all of my favourite extensions using this method (the ones that FF didn't "like") and I have had no problems.
This may not be true for all Add-ons.

I would also suggest that you change the Add-on version number, so that you can remember which Add-ons you have edited.

I've changed all of my edited Add-on version numbers (to 7.0.0).
Of course I'm running FF8a now. D'oh! :D
 

My Computer

Computer type
PC/Desktop
Computer Manufacturer/Model Number
n/a
OS
W7 Ultimate SP1, LM19.2 MATE, W10 Home 1703, W10 Pro 1703 VM, #All 64 bit
CPU
AMD Phenom II x6 1100T, 3.3 GHz
Motherboard
ASUS M4A88T-M/USB3 (AM3)
Memory
12GB DDR3 1333 G-Skill (4GB x 2), G-Skill (2GB x 2)
Graphics Card(s)
NVIDIA GeForce GTX 660
Sound Card
Realtek?
Monitor(s) Displays
Samsung S23B350
Screen Resolution
1920x1080
Hard Drives
WD Green 2TB (SATA), WD Green 3TB (SATA), WD Blue 4TB (SATA), WD Blue 6TB (SATA)
PSU
Cooler Master
Case
Antec GX300 Tower
Cooling
3x Antec TRICOOL 120mm Fans
Mouse
Wired Optical
Internet Speed
DSL
Antivirus
Avast
Browser
Pale Moon (64 bit)
Other Info
2018-12-27 Upgraded HDDs
2015-12-10 Upgraded case, graphics card, storage
2015-08-15 Upgraded motherboard & RAM
2015-07-15 Upgraded LM17.1 to LM17.2
Back
Top