Read up on the latest ideas and technologies from companies that sell hardware, software and services. Improving Sales Productivity: An Opportunity for Sales and IT Leadership
Revolutionising Back-up and Recovery
Solve Exchange Storage Problems Once and For All: A New Approach without Stubs or Links
Mimosa™ NearPoint™ for Microsoft® Exchange Server: Email Archiving 101
CRM your salespeople will love
How to Beef Up Your Sales Pipeline
Email Archiving Technical Overview
Web Security SaaS: The Next Generation of Web Security
Zones provide focussed content from Computerworld and leading technology partners.Newsletter Subscription
If you're like me, you've been playing around with the beta releases of Firefox 3.0. The new version of the open source browser is better-looking, uses less memory, and feels snappier all around. There's just one problem: Every time they release a new beta version, some of your extensions and add-ons are bound to stop working. With the release of Firefox 3.0rc1, almost none of them work.
Fortunately, there is a solution that will "fix" all of your extensions at once. But I caution you, it's not for the weak-hearted. The fix doesn't take longer than a few seconds, but when it comes to troubleshooting your browser afterward, you'll be on your own.
I can't repeat this enough. DO NOT TRY THIS unless you are comfortable editing the advanced preferences of your browser. And don't do anything until you've read through this entire post. Don't say I didn't warn you.
In my experience, extensions that worked with Firefox 3.0b5 will generally be stable with 3.0rc1. It is possible, however, that some of them will cause the new version of the browser to crash. It might even crash on startup -- which means, obviously, that you won't easily be able to undo the fix I'm about to describe.
The key to the fix is to prevent Firefox from checking its version number before it tries to load extensions. To do this, you will need to set a new preference value. Point your browser at the URL "about:config", then right-click on the preferences list to bring up the contextual menu. You should see an option that says "New." Select that, and choose "Boolean." When it asks you for the preference name, type "extensions.checkCompatibility" (without the quotes). You have to enter the name exactly. For the value, choose "false."
Now restart Firefox. When the browser comes back up, it should give you a warning that version checking is disabled. You can double-check under "Tools:Add-Ons" to make sure everything is activated once again.
If the worst case happens and the browser won't start after you add the new preference, you'll need to remove it by hand. Locate the file "prefs.js" within your Firefox profile directory and edit it with any text file editor to delete the line with the preference you just created. (If you're not comfortable doing that, then as I've said, this fix is probably not for you.)
Also, you'll want to remember to delete the preference once the final version of Firefox 3.0 is released, or else you'll never be certain that your installation is stable.
Good luck. As I've said before, I can't troubleshoot any individual Firefox installations. But hopefully this will help you keep your most-beloved add-ons running until their maintainers update them for the final Firefox 3.0.
Computerworld Member Login
Discover how SOA can create smarter outcomes for your business.
Attend and learn:
- How SOA is helping leading companies to become more agile
- Where you should be applying SOA processes in your company
- The top SOA implementation mistakes to avoid
Click here for more information.
- +
Computerworld Live Podcast #97: The Future of Enterprise Networking 25/07/2008 09:45:36
This week CW Live chats with Mark Thompson, global sales and marketing manager for HP ProCurve, on the future of the enterprise networking. Mark discusses the trends we can expect to see in the near future and how the right infrastructure can ensure your enterprise network is secure. - +
Computerworld Live Podcast #96: Security at the Edge 11/06/2008 09:22:22
CW Live speaks with Amol Mitra, HP ProCurve Director of Marketing for Asia Pacific and Japan. Today's topic: how enterprises are starting to shift away from simply controlling security via server logins, firewalls and moving to more adaptive security frameworks. - +
Data Management Edition #10: Multi-Petascale Systems 02/05/2008 09:12:33
This week we look at sustainability and the development of multicore technologies to build multi-petascale systems. - +
IT Security Edition #11: How to poison the Storm botnet 01/05/2008 08:51:55
This week CW Live presents a case study on how to poison the notorious Storm botnet . Plus we take a look at Cisco's plans for Ironport. - +
IT Security Edition #10: Cyber-battles fought and won 24/04/2008 11:09:47
Vendors bow to end user pressure to improve product security, and we take a look at the latest concepts shaping the cyber-battlefield of the future.
F-Secure achieves excellent results in Internet security suite comparison 2008-10-10 14:37:00+10
M2M Connectivity announces the new Sierra Wireless MC8792V embedded module for 900 MHz 3G/HSPA networks 2008-10-10 08:51:00+10
Pitney Bowes MapInfo Launches New Version of AnySite 2008-10-10 05:58:00+10
IOGEAR Gears Up in Australia 2008-10-09 20:18:00+10
Internet Service Providers offer new unlimited Online Backup from F-Secure 2008-10-09 19:42:00+10
Email Archiving 101—Customer Case Study
Join Lee Benjamin, a Microsoft Exchange MVP and Ryan Shipkowski, network administrator for Matthews, to discuss the process and ROI of implementing an email archiving solution, with emphasis on a case study from Matthews International.











Comments
Misleading title
Firefailed
Great news, unfortunately I shot first, didn't bother with the questions, and stuffed my Firefox. But I have an easy work-around.
The UK beta version I downloaded yesterday must be subtly different. The pref.js file, when opened in notepad, says you can't edit the preferences and directs you to the about:config page within the browser.
But the crash prevents you from opening the browser, so I ran Firefox in safe mode, ticked the box to reset preferences, restarted and it worked.
The problem wouldn't have occurred if I was less gun-ho and actually bothered to check version numbers, so a warning to others in my boat.