So Firefox 1.5.0.1 killed your extensions
The recent firefox 1.5.0.1 release has caused a number of problems for various parties, including extension authors and users. Sadly, many extension authors did not set up their extensions to be able to deal with firefox security updates gracefully. There have been no changes to the extension api, but a surprisingly large number of extensions report that they are Disabled – not compatible with Firefox 1.5.0.1. Well, if the extension is compatible with 1.5, you are in luck, there is a way to fix this that is not too difficult that doesn’t involve the extension author having to release a new version.
(in firefox, go to Tools->Extensions)

First thing you need to do is shut down firefox. Next, open the file “extensions.rdf” from your profile directory (something similar to C:\Documents and Settings\your username\Application Data\Mozilla\Firefox\Profiles\default.ugt in windows, ~/.mozilla/firefox/eucals91.default in linux) in a text editor. (it would be a good idea to save off a backup of this file, just in case). Search for every instance of 1.5 in the file. Those cases where the line says NS1:maxVersion=”1.5″ need to be changed:
Editor’s Note: This needs to be a text editor like notepad or textpad or ultraedit. If you use word or wordpad, you will break your extensions.rdf. At least two people have done this, so please, *be careful*. Also, some text editors will append .txt to the rdf file name. ensure that when it’s done, you have the right windows file extension.
<RDF:Description RDF:about="rdf:#$0Q1PK2"
NS1:id="{3550f703-e582-4d05-9a08-453d09bdfdc6}"
NS1:minVersion="1.5"
NS1:maxVersion="1.5" />
You will want to alter them so that they say NS1:maxVersion=”1.5.0.*” as below:
<RDF:Description RDF:about="rdf:#$0Q1PK2"
NS1:id="{3550f703-e582-4d05-9a08-453d09bdfdc6}"
NS1:minVersion="1.5"
NS1:maxVersion="1.5.0.*" />
Now, restart firefox, and go to Tools->Extensions:

Right click on the disabled exension, and select Enable from the dropdown. Finally restart firefox. If everything went well, your extensions should be happy again.
Ed: A second solution has come to my attention in the form of the Nightly Tester Tools extension which will allow you to install incompatible extensions via it’s interface. With this installed, in the extensions panel, you can right click on an extension, and select “Make Compatible”. This method may be somewhat riskier, as it makes an extension potentially compatible across larger updates that may have API changes. The original method carries no risk of this, as it only covers security updates to firefox 1.5
February 8th, 2006 at 4:06 am
Downloadsquad is showing another approach to fix the not working extensions after the upgrade. I don’t know which method is more effective.
http://www.downloadsquad.com/2006/02/03/how-to-make-old-extensions-work-in-a-new-version-of-firefox/
February 8th, 2006 at 2:03 pm
Thanks dude, Still had a few non functionning extension, hope your tweak will fix them, I’ll report back!
Cheers!
Kiltak
[Geeks Are Sexy] Tech. News
February 8th, 2006 at 2:18 pm
Both ideas should work. Mine is updating the extensions to work with the version, theirs is backdating the software to an older version. Mine should be pretty clean, I have no idea what effect (if any) this should have on future firefox core updates.
It appears there are a number of ways to solve this problem.
February 8th, 2006 at 2:34 pm
The Nightly Tester Tools extension allows you to make
extensions compatible
http://users.blueprintit.co.uk/~dave/web/firefox/buildid/nightly.html
February 8th, 2006 at 2:40 pm
It’s Funny that the example is Venkman. There’s a specific version of Venkman for the 1.5 branch. It’s on a separate webpage from the .9.85jw2 Venkman. Once you install the correct version. It will update automatically for FF 1.5.x and jsut work.
http://getahead.ltd.uk/ajax/venkman/
February 8th, 2006 at 3:18 pm
If its so easy to fix, why cant extension authors just bang out an updated version with the fix quick?
February 8th, 2006 at 3:25 pm
If its so easy to fix, why cant extension authors just bang out an updated version with the fix quick?
Donno, I have no control over that. I suspect many of the extensions are just poorly maintained. The three solutions here and in the comments allow users to avoid having to wait for a developer who doesn’t even know his extension is broken yet.
February 8th, 2006 at 3:59 pm
Infact, everything did not go well. When I try to access my extensions the extension list is blank but I can access the extensions in right click menus and from the tools menu.
February 8th, 2006 at 4:10 pm
mikae1, you only touched your extensions.rdf, and backed it up? You didn’t touch anything else?
I’ve never used the extensions in the sidebar, so I didn’t test that. To get to the extensions, does Tools->Extensions still work?
February 8th, 2006 at 4:16 pm
mikae1, are you using the All-in-One Sidebar Extension? http://firefox.exxile.net/
That’s the only way I can find to store an extensions view in the sidebar. Perhaps this jsut needs to be reconfigured?
February 8th, 2006 at 5:40 pm
[...] Evilsoft.org has a good rundown of how to edit a Firefox configuration file in order to restore extensions caused by minor updates. [...]
February 8th, 2006 at 6:08 pm
Went to downloadsquad.com (above link) and followed the directions and it my one extension is now working. It was Footie Fox that stopped working when I changed to FF 1.5.0.1
February 8th, 2006 at 6:37 pm
This is similar to how when you uninstall FF completely the extensions all have to be reinstalled again. I would love it if there was a way of keeping track of those without editing a file and copying out pieces to find out what was installed, or even without jotting things down on a piece of paper.
This would also be great for when your hard drive gets scrogged or you just want to duplicate your setup somewhere else.
FF definitely needs better extension management. But this is still miles ahead of Mozilla’s extension management.
February 8th, 2006 at 6:57 pm
I tried the fix with my SpellBound extension and it allowed the SpellBound extension to be reactivated but the fix did not work on the Mozilla SpellCheck Libraries which are required to make the SpellBound extension work.
Sigh…
I think extensions are one of the most important features of FireFox and I would hope that the Mozilla Team finds a way to stop breaking extensions with every update. This is especially of concern because so many extension developers are developing their extensions on the side and perhaps don’t have the time to be forever updating extensions that the Mozilla Team keeps breaking.
February 8th, 2006 at 7:48 pm
a friend had a pretty hilarious problem after the latest updATE. all but one site that he visits would bounce.the temp solution is just hit F5 at startup or visit http://kb.mozillazine.org/Window_shakes
February 8th, 2006 at 9:06 pm
Hi Guys,
I have been having some trouble with JavaScript when I visit some sites. More in particular when I visit my mailbox (ISP). I too just updated to the latest firefox, but it seems that all of a sudden IE and firefox both give the same error:
“JavaScript Error
http://URL.html?sid=qn1bPyziGCE&lang=en&cert=false, Line1
opensummary is not defined”
I tried doing the things above, but no use. Anyway if it matters, I have installed Firefox on another drive than C: and when I go to the “JAVA CONTROL PANEL” through “Program Files” and in the “Advanced” tab where one can change the settings under the “tag support” drop down menu IE is checked but not Mozilla Firefox. When I check it and click OK, it says either software not installed properly or I do not have sufficient privellages (I AM DA ADMIN!!) However this does not explain why the same things are happening in IE too.
Hope someone can come to my aid.
February 9th, 2006 at 12:52 am
[...] Mozilla FireFox最近推出了1.5.0.1版, 解决了一些bug的现时随之而来的是又一大堆的bug, 由于很多插件作者在写插件时没有很好的支持ff的安全升级以至于升级到新版本的用户发现之前可以使用的插件相继瘫痪, 对于1.50版下可以使用的插件, 这里提供了一个解决方法. Tag:extension, firefox [...]
February 9th, 2006 at 1:09 am
why not just uninstall and re-install the extension?
February 9th, 2006 at 9:00 am
Make your extensions work with Firefox 1.5.0.1
If last week’s update to the latest version of Firefox broke some of your extensions (you DID pay attention to that update dialog, didn’t you?), Lifehacker reader Devon offers a quick solution which involves editing Firefox’s extensions.rdf file. P…
February 9th, 2006 at 10:24 am
Firefox 1.5: Updating / Upgrading extensions / add-ons
I was one of those many, but now only a few, that resisted from migrating from Firefox 1.0.7 to the latest Firefox 1.5. Only on account of the lack of upgrade/updates to the numerous, yet ‘cannot live without’ extensions I…
February 9th, 2006 at 12:37 pm
So Firefox 1.5.0.1 killed your extensions
The recent firefox 1.5.0.1 release has caused a number of problems for various parties, including extension authors and users. Sadly, many extension authors did not set up their extensions to be able to deal with firefox security updates gracefully. Th…
February 9th, 2006 at 12:40 pm
Thanks, for some reason I have never heard of the Nightly Tester Tools!
February 9th, 2006 at 4:38 pm
[...] The recent firefox 1.5.0.1 release has caused a number of problems for various parties, including extension authors and users. Sadly, many extension authors did not set up their extensions to be able to deal with firefox security updates gracefully. There have been no changes to the extension api, but a surprisingly large number of extensions report that they are Disabled – not compatible with Firefox 1.5.0.1. Well, if the extension is compatible with 1.5, you are in luck, there is a way to fix this that is not to difficult that doesn’t involve the extension author having to release a new version. Link: http://www.evilsoft.org/?p=69 [...]
February 9th, 2006 at 6:50 pm
[...] Tolle Sache, wenn ein Browser aktuell gehalten wird, Löcher geflickt und Probleme beseitigt werden. Zumal man inzwischen nicht einmal eine neue Version installieren muss, sondern ein bequemes Update nutzen kann. Trotzdem nervt es, wenn bei jedem Miniupdate zwei Drittel aller Extensions abgeschaltet werden, weil diese angeblich nicht mehr kompatibel sind. So geschehen beim Update von Version 1.5 auf 1.5.0.1. Da muss eine bessere Lösung her. Wer nicht warten mag, bastelt sich das selbst zurecht. Lösungen im Angebot haben: Evilsoft und Downloadsquad. Namen übrigens, die man eher mit dem Internet Explorer assoziieren würde… Spaß. [...]
February 10th, 2006 at 4:43 pm
I upgraded to the new Firefox. It totally crashed my laptop. (But works flawlessly on my desktop.) Now no version of Firefox works on my laptop, and cannot figure it out. All the tech support recommendations on the Mozilla site did not resolve the problem.
Now I’m stuck without Firefox, my saved passwords, and all my Web stuff. Switching back to IE or over to Opera is painful… But IE is the most painful. So I guess I’ll just migrate all my passwords and bookmarks to Opera. Sorry Firefox, but I guess I just relied on you too much. Now I’m sad.
February 13th, 2006 at 10:04 am
Please, please, please, learn the difference between “to” and “too.”
The difference is important to know if you are a blogger.
February 15th, 2006 at 2:11 am
[...] For more info. see Evilsoft.org » So Firefox 1.5.0.1 killed your extensions firefox, firefox, extension, problem [...]
February 15th, 2006 at 3:39 am
Extension MRTech Local Install will update the MaxVersion problem with other extensions. It adds a make compatible entry as well as a restart firefox and other nice things to the extension menus.
It’s truly a wonderful extension
February 26th, 2006 at 7:30 am
Fix your Firefox extensions for version 1.5.0.1
Firefox is a great web browser. But if you have upgraded to the latest version 1.5.0.1, you may have found that it broke your extensions. So does that leave you “up the creek with no paddle?” Not really.
There are at least two approaches out ther…
March 15th, 2006 at 7:02 am
[...] Evilsoft.org suggests another strategy to “open the file “extensions.rdf” from your profile directory…in a text editor….Search for every instance of 1.5 in the file. Those cases where the line says NS1:maxVersion=”1.5″ need to be changed” and changing the parameter here will also make it work. Read their full article. [...]
April 13th, 2006 at 10:46 pm
[...] Evilsoft publicó, hace ya casi 2 meses, un buen tip para forzar a las extensiones a reconocer la nueva versión de Firefox, para que puedan funcionar. Así que aquí les traduzco una parte, paso a paso: [...]
April 14th, 2006 at 9:51 pm
[...] read more | digg story [...]
April 17th, 2006 at 2:27 pm
[...] Cómo recuperar extensiones asesinadas por Firefox 1.5.0.1 [...]