Firefox 2.0.0.6 is Making Me Cranky!

August 1, 2007 11:52 AM

Firefox 2.0.0.6 doesn't work with most of the extensions I'm using, including Greasemonkey. What can I do?

Two nights ago, my Firefox automatically updated itself to 2.0.0.6. Now many of my extensions don't work, including the all-important Greasemonkey. Does anyone know what, if anything, Firefox is doing about this? Is there a way to go bak to the version I was using before that actually worked with all my preferred bells and whistles? Does anyone know where there is a centralized discussion about this issue? I'm sure I'm not the only one having this kind of trouble. Right now, there's no mention of this on the FF blog.

posted by abbyladybug to Computers & Internet (16 answers total)

Really? All of my extensions, including Greasemonkey, work fine in FF 2.0.0.6.

Oldversion.com doesn't have FF 2.0.0.5, but oldapps.com does.
posted by Tuwa at 11:55 AM on August 1, 2007

Firefox doesnt have to do anything. Its up to the maintainers of the extension to update their product for firefox. Give them a little time.

Mozillazine is the official firefox forums btw.

You can download and install an old version here. 2.0.0.4 is probably what you are looking for.
posted by damn dirty ape at 11:56 AM on August 1, 2007

Ah, a more authoritative source. win for damn dirty ape.
posted by Tuwa at 11:57 AM on August 1, 2007

Also, have you tried clicking on Tools > Add-ons > Update yet?
posted by damn dirty ape at 11:58 AM on August 1, 2007

I have an extension called "MR Local Tech install" that lets you override the max version of extensions that haven't been updated recently. The extensions I've used it on have worked for the most part, but there is no guarantee.
posted by Good Brain at 12:00 PM on August 1, 2007

You're looking for Nightly Tester Tools.
posted by mullingitover at 12:05 PM on August 1, 2007

You can override this with Nightly Tester Tools or MRTech, I'd recommend the latter unless you don't need all the extra gizmos it comes with.
posted by prostyle at 12:22 PM on August 1, 2007

I'll 2nd the value of "MR Local Tech install." I've been using this extension for well over a year, and have not had to worry about extension compatibility. It's invaluable, as some some extensions wouldn't ever be compatible otherwise.
posted by bawanaal at 12:29 PM on August 1, 2007

Best answer: I had this problem with 2.0.0.5. Following the directions here fixed it fairly easily.
posted by Rock Steady at 12:29 PM on August 1, 2007

Ditto MR Local Tech Install recommendation (or Nightly Tester Tools, but I like lots of the other features of MR Local Tech also.) It's uncommon for a minor revision to break extensions, and well worth using one of these to override the maxversion check -- it'll probably work. (But it's common for the major revisions to break extensions.)
posted by Zed_Lopez at 12:31 PM on August 1, 2007

Rock Steady has the answer you're looking for. All of my extensions (including Greasemonkey) work on 2.0.0.6, so I think the maxversion check has nothing to do with your problem.
posted by Thoughtcrime at 12:41 PM on August 1, 2007

Download any extensions you want.
Change .xpi file extension to .zip
Open this file.
Copy install.rdf from the zip to a useful folder (Desktop).
Open this copy in a text editor.
Locate the em:maxVersion line associated with Firefox, usually labeled with comments.
Edit the value to 2.0.0.*
Save, copy the edited file back into the zip, rename back to .xpi, install.
posted by anaelith at 1:20 PM on August 1, 2007

Response by poster: Rock Steady - You got it! It was a corrupt localstore file. That safe mode restart with resetting toolbars thing didn't work. It's ALL better now.

Thanks, internets! You're more than just a series of tubes to me!
posted by abbyladybug at 1:37 PM on August 1, 2007

FYI, one of the nice things about Firefox (and other not-Microsoft apps of record) is that you can run multiple versions simultaneously. If you wanted to download and install 1.5.x.y, you could.
posted by davejay at 5:46 PM on August 1, 2007

Even a stopped clock is right twice a day, I guess. Seems to be a random occurrence since 2.0 -- I think the Google result that lead me to that fix was someone who had the problem with 2.0.0.3 or .4. The safe mode didn't work for me either. I actually seem to remember I had to do something screwy like create a new default profile and move my extensions folder into it, now that I think about it. Anyway, glad I could help.
posted by Rock Steady at 9:19 PM on August 1, 2007

Response by poster: Well, I appreciate it. That a Withnail & I reference? Or did that quote begin before that movie? Either way, I like it. And I'm glad you suggested it.
posted by abbyladybug at 3:42 AM on August 2, 2007