Skip to main content

Firefox Add ons

How to make Firefox addons compatible with the newest release.

Everybody likes to try out the newest version of Firefox. At the time I was writing this Firefox 3.1 beta 1 was available. When you install it you will find some of your existing Firefox add-ons may have already been updated to work with the new version. Others won’t install at all.

Don’t be surprised if some of the add-ons you modify to be compatible, bring Firefox to its knees. They don’t let you install older versions for a reason. But so I’ve had no problems at all.

Step 1 – Downloading the add-on

Locate the add-on you want to install. If it’s on the official Firefox add-on page you’ll have to click “See All version” to be allowed access to the .xpi. Right click on the now clickable “Add to Firefox” button and choose save target file as.

Step 2 – Extracting the add-on.

Locate the add-on you just saved. You should be able to open the .xpi file with your favorite compression utility. I use Power Archiver and it seemed to work just fine. Other compression utilities compatibility may vary. Extract the add-on to the folder of your choosing. I usually recommend extracting it to its own folder on the desktop.

Step 3 – Modifying install.rdf

Open the folder you just extracted the xpi file to. You’ll see a file called install.rdf. By default windows will have no idea which program to use to open the file with. You can either use notepad or WordPad.
Once you have the document opened do not get intimidated by the amount of text that you see. I find it’s easiest to just do an edit / find and look for the word max. That should take you directly too


All you have to do is edit what is between the > <. In this case it says 3.0. Change the number to the current installed version of Firefox. In this case I have Firefox 3.1 Beta 1 installed. Which is written out as 3.1b1. So when I get done, it should say


I guess you could also plan ahead so you don’t have to edit this for every new release. You could probably change it to 3.1b4 or something in that nature.
Once you have that change made, save and exit the file.

Step 4 – Recompressing the xpi file.

The method of recompressing it into a file will vary by the software you use. If you use power archiver or winzip, I would recommend you open the folder containing the extracted contents of the xpi file and do a select all. Once all the files are selected, right click anyone of them and click “Add to zip”. When you’re done you should have a file ending in .zip. All that is left is to rename the zip file (in XP you’ll have to make sure you can see file extensions) to the name of the xpi file you downloaded earlier. Just make sure when you are done that the file ends in .xpi and not .zip.

That’s it. Now just open Firefox and drag the xpi file you just created into Firefox and choose install. Once you reboot Firefox your add-on should now function properly (hopefully).


Popular posts from this blog

ARCore and Arkit, What is under the hood: SLAM (Part 2)

In our last blog post ( part 1 ), we took a look at how algorithms detect keypoints in camera images. These form the basis of our world tracking and environment recognition. But for Mixed Reality, that alone is not enough. We have to be able to calculate the 3d position in the real world. It is often calculated by the spatial distance between itself and multiple keypoints. This is often called Simultaneous Localization and Mapping (SLAM). And this is what is responsible for all the world tracking we see in ARCore/ARKit. What we will cover today: How ARCore and ARKit does it's SLAM/Visual Inertia Odometry Can we D.I.Y our own SLAM with reasonable accuracy to understand the process better Sensing the world: as a computer When we start any augmented reality application in mobile or elsewhere, the first thing it tries to do is to detect a plane. When you first start any MR app in ARKit, ARCore, the system doesn't know anything about the surroundings. It starts pro

ARCore and Arkit: What is under the hood : Anchors and World Mapping (Part 1)

Reading Time: 7 MIn Some of you know I have been recently experimenting a bit more with WebXR than a WebVR and when we talk about mobile Mixed Reality, ARkit and ARCore is something which plays a pivotal role to map and understand the environment inside our applications. I am planning to write a series of blog posts on how you can start developing WebXR applications now and play with them starting with the basics and then going on to using different features of it. But before that, I planned to pen down this series of how actually the "world mapping" works in arcore and arkit. So that we have a better understanding of the Mixed Reality capabilities of the devices we will be working with. Mapping: feature detection and anchors Creating apps that work seamlessly with arcore/kit requires a little bit of knowledge about the algorithms that work in the back and that involves knowing about Anchors. What are anchors: Anchors are your virtual markers in the real wo

Visualizing large scale Uber Movement Data

New York's cab data visualization from Uber's Engineering blog Last month one of my acquaintances in LinkedIn pointed me to a very interesting dataset. Uber's Movement Dataset. It was fascinating to explore their awesome GUI and to play with the data. However, their UI for exploring the dataset leaves much more to be desired, especially the fact that we always have to specify source and destination to get relevant data and can't play with the whole dataset. Another limitation also was, the dataset doesn't include any time component. Which immediately threw out a lot of things I wanted to explore. When I started looking out if there is another publicly available dataset, I found  one  at Kaggle. And then quite a few more at Kaggle. But none of them seemed official, and then I found  one released  by NYC - TLC which looked pretty official and I was hooked. To explore the data I wanted to try out OmniSci. I recently saw a video of a  talk  at jupytercon by Randy Zw