Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

Firefox 3.6 Released


  • Please log in to reply
3 replies to this topic

#1 Andrew

Andrew

    Bleepin' Night Watchman


  • Moderator
  • 8,259 posts
  • OFFLINE
  •  
  • Gender:Not Telling
  • Location:Right behind you
  • Local time:03:50 PM

Posted 22 January 2010 - 02:29 PM

Mozilla has released the next version of its popular web browser: Firefox 3.6

There are a number of under-the-hood changes to this version of Firefox which are designed to make it faster and more reliable. But, as with any updated program, there are a few annoyances which need to be beaten out of it.

The first one is well known to affect each new version of Firefox when it's first released: Addon Compatibility. With each new version there's a lag time between final release and Addon writers updating their addons. In the past, this annoyance could be avoided simply by adding the extensions.checkCompatibility=False preference in about:config. But version 3.6 adds a new wrinkle: extensions.checkCompatibility is now ignored! In its place is a new preference which is supposed to be more flexible: extensions.checkCompatibility.<version>. Unfortunately, there's little to no documentation on this new preference and I have yet to figure out how it works. Any advice would be welcome!

So, extensions.checkCompatibility=False no longer works and, if you're like me you now have several addons which are disabled. You may even be intentionally using an older version of an addon like I am with LinkAlert. So what can we do? For the moment, I'm stuck with manually editing the addon files to trick Firefox into installing them. Here's how you do it:

1. Open you list of addons and note which ones are disabled for compatibility reasons.
2. Go to https://addons.mozilla.org/en-US/firefox/
3. Search for the addon in question and go to it's description page. You'll notice that the install button is disabled.
4. Scroll down to the bottom of the page and click the "View All Versions" link
5. Find the version of the addon you want (most likely the topmost, and newest, version.)
6. Right-Click on the "Add To Firefox" button and click "Save Link As." Choose a convenient location to save the addon file, like the Desktop
7. Repeat steps 3-6 for each addon you need.
8. You should now have a collection of .XPI files corresponding to the addons. XPI files are simply ZIP archives with a different extension. Rename each XPI file as a ZIP file (e.g. myAddon.xpi becomes myAddon.zip)
9. Inside each archive is a file called install.rdf. Open this file in notepad and find the line that looks like this:
<em:maxVersion>3.5.*</em:maxVersion>
change the 3.5.* part to read 3.6 (note: the actual number shown may be different from 3.5.* depending on the addon)
10. Save the install.rdf file and put it back in the archive file, overwriting the old one.
11. Rename the ZIP file to XPI
12. Repeat steps 9-11 for each addon.
13. In the Firefox Addon Manager, uninstall each of the addons that you downloaded the XPI file for. Restart Firefox.
14. Drag each XPI file into the Firefox window to install it. Restart Firefox.
15. Done!







The other annoyance (for me, anyway) in 3.6 is that they removed the Properties context menu item. They say they did it because very few users ever used it. I'm one of those few, so I wanted it back. Luckily, there's already an addon for that: https://addons.mozilla.org/en-US/firefox/addon/14228

So now Firefox 3.6 works just as well as 3.5.7 did...

Edited by Amazing Andrew, 22 January 2010 - 02:30 PM.


BC AdBot (Login to Remove)

 


#2 Layback Bear

Layback Bear

  • Members
  • 1,880 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Northern Ohio
  • Local time:05:50 PM

Posted 24 January 2010 - 10:39 AM

Thank you Amazing Andrew I was just today thinking about the update. Unless I have brain fade I check here before doing such things. As like you I use properties on many things, I don't ever know how they would know how many people use properties or not. I'm keeping what I got. Going through all those steps just to get back what I got just isn't me. Your a work horse. Thanks again for keeping track of things like this. I would think Mozilla have people looking at this site, maybe they will catch on and change things.

#3 Broni

Broni

    The Coolest BC Computer


  • BC Advisor
  • 42,699 posts
  • ONLINE
  •  
  • Gender:Male
  • Location:Daly City, CA
  • Local time:03:50 PM

Posted 24 January 2010 - 03:41 PM

Andrew
There is FF add-on, which I've been running forever and which will fix all compatibility issues, Mr. Tech Toolkit: https://addons.mozilla.org/en-US/firefox/addon/421

My Website

p4433470.gif

My help doesn't cost a penny, but if you'd like to consider a donation, click p22001735.gif


 


#4 xblindx

xblindx

  • Banned
  • 1,923 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:06:50 PM

Posted 25 January 2010 - 10:45 AM

Will editing that string in the add on file cause any issues, such as preventing the add-on from updating on its own?




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users