Replies

That makes two of us. Every single time Mozilla breaks wind it breaks extensions and themes, one of the features they beat their chest about. They're screwed up the themes and extensions site so that it's a pain to keep going back and finding and reloading it all. (Used to be you could select 50 items on a page, now it's at 10 only. Yawn....)

Every single time Mozilla breaks wind it breaks extensions and themes, one of the features they beat their chest about.

Not really. Extensions and themes work like this: each Firefox version has its own internal version ID. Extensions and themes specify which versions of Firefox they can install on by defining a range between a minimum version (usually 0.9) and a maximum (which is usually the latest version at the time of that extension or theme's release.) Shortsighted extension/theme authors would set the maxversion in such a way as to require that extention/theme to be constantly updated whenever a new version of Firefox came out. That's not Mozilla's fault.

1.5 attempts to work around this with the four-digit version numbers. The third number represents whether or not there's been a change in the extension/theme APIs that would require code reworking, and the fourth number is the usual incremental version number. All extensions and themes should be set to a maxversion of 1.5.0.* to guarantee maximum compatibility, but again, it depends on the author.

Don't blame Mozilla for the faults of third-party stuff.

Every single time Mozilla breaks wind it breaks extensions and themes, one of the features they beat their chest about.

In case you run into that problem in the future there's an extension you can add called Nightly Tester Tools that'll force broken extensions to believe they're compatible with the latest version.

Just in case that doesn't work though here's other steps you can try.