gt; Firefox > How To Future-Proof Your Firefox Extensions > September 28, 2005 Want to test-drive the Firefox 1.5 beta and bring most of your favorite extensions along for the ride? We'll show you how to make your brand new Firefox update less picky about installing extensions -- and explain why doing so isn't always a good idea. I'm a big fan of Firefox extensions, and it shows: I have 40 extensions installed on one of my PCs, and on the others -- including Windows 2000, Linux, and Mac OS X systems -- I rarely run Firefox without at least 20 of my favorites installed, sometimes together, other times spread across two or three different profiles. Like many Firefox power uses, I also installed the Firefox 1.5 beta not long after Mozilla released it. And when I ran the beta for the first time, I discovered that just 10 of those 40 extensions ran, too. Firefox 1.5 found the rest "incompatible" when it started for the first time and disabled them. These numbers reflect the value of minVersion and maxVersion in each extension's resource.rdf file. 1 of 2 More Insights
IE NetRenderer - Browser Compatibility Check - Sherlock & OpenSearch Search Engine Plugins Geek to Live: Manage multiple Firefox profiles I just posted this to digg, realized i should post it at the source (with your kind permission). Pardon the cut&paste... The method the author listed for shortcuts won't work in OS X, because (as far as i have been able to determine), there is no way to manually edit the path for a shortcut (love OS X but that's incredibly weak). So far the only solution i have found is a little wonky to implement, but unless you're planning on making lots of different profiles, it's not that bad. 1. Create a profile, we'll use "webdev" as an example. 2. #! /Applications/Firefox.app/Contents/MacOS/firefox -P "webdev" and save it as Firefox.webdev (if your editor adds a .txt extension, delete it). 3. 4. I also copy the icon from Firefox to the script, but this isn't essential. Like i said, a bit wonky, but it's the only way i know of to create a shortcut to an app with command-line parameters (in this case, -P for profile manager).