Comments on: Make Firefox Extensions Compatible After Firefox Update Breaks Them For No Good Reason

By: web design company

web design company — Wed, 18 Jun 2008 19:13:47 +0000

Or even easier, create a new (true) boolean key in about:config called “extensions.checkCompatibility” http://kb.mozillazine.org/Exte.....patibility

By: Lisaweb

Lisaweb — Tue, 31 Jul 2007 18:40:31 +0000

Wow, awesome, awesome tip! I rely heavily on several of my extensions for work productivity, and the authors of certain extensions are slow to update version compatibility. This saves me, big time. Thanks Geek!

By: Webdog

Webdog — Tue, 31 Jul 2007 18:20:49 +0000

A minor heads-up: You may not notice it at first, but while the Nightly Tester add-on is active, it triggers a “build�? number reference in the title bar of the Firefox browser. If that annoys you, after you have made your extensions “compatible” just disable the Nightly Tester add-on and the build number disappears.

By: The Geek

The Geek — Tue, 31 Jul 2007 16:10:52 +0000

Jake,

Thanks for the update… I’ll install it.

By: Jake

Jake — Tue, 31 Jul 2007 15:54:34 +0000

The Geek: Asa Dotzler answered this it looks like to me. You are supposed to define for maximum version to support, for instance, all 2.0 versions or all 1.5 versions. The author instead specifically said the highest compatible version was 2.0.0.3, which is was a security update. I made a version that shuold work with all future security updates to 2.0.

http://localhostr.com/files/aa.....077cfb.xpi

Let me know if that works.

By: The Geek

The Geek — Tue, 31 Jul 2007 12:54:50 +0000

I realize it’s the extension developers fault for not following the guidelines.

That said, it’s still extremely annoying, especially in this case…. why did it work fine with 2.0.0.5 but not 2.0.0.6 ?

By: Asa Dotzler

Asa Dotzler — Tue, 31 Jul 2007 07:48:00 +0000

Security updates do not break extensions unless the extension author failed to write the extension’s compatibility version correctly. If you have an extension that’s disabled with a security update, contact the extension author and let her know that she hasn’t put the correct compatibility string in the extension. It’s probably missing a .0.* or something simple like that.

- A