Mozilla Firefox 3.6.7

[jofre]

Found this, tried and IDM CC is enabled again ( Mine is WinXP Pro - 32 bits )

QUICK FIX** for all "Internet Download Manager" users.....

1.) Type in Firefox address bar --» about:config

2.) Search for « extensions.blocklist.enabled » and change it to --» false.

Restart firefox

[DreamHaters]

Or you can disable "extensions.blocklist.enabled"

Change it to false.

This is only a temporary measure till firefox updates a fix for it.

Found this, tried and IDM CC is enabled again ( Mine is WinXP Pro - 32 bits )

QUICK FIX** for all "Internet Download Manager" users.....

1.) Type in Firefox address bar --» about:config

2.) Search for « extensions.blocklist.enabled » and change it to --» false.

Restart firefox

Thanks :D

[Night Owl]

For me Firefox didn't blocked IDM extension. Its working fine with FIrefox 3.6.7 :D Windows 7 x64 Ultimate

THE IDM extension is blocked only if the update is performed internally through the Firefox program and not if done through the installer.

Yes, I did an internal update to Firefox 3.6.7.

My Firefox just recently updated to 3.6.7. Everything seemed fine until I got this notice:

How do I get Internet Download Manager back? :fear:

EDIT: BEEEEEEEEEEEEEEEP. Gadzooks, I've been censored!!

Check if this works for you:-

Navigate to "C:\Program Files\Internet Download Manager" you'll see 'idmmzcc.xpi' - it should allow installation to 6.9.8 (do let us know.)

That file was in my "Program Files (x86)" folder. No, it didn't work. Firefox 3.6.7 won't allow IDM at all just like the Firefox developers said:

:frusty: Grrrr. Let me read further in this thread.

[Night Owl]

Or you can disable "extensions.blocklist.enabled"

Change it to false.

This is only a temporary measure till firefox updates a fix for it.

That worked! IDM CC 6.9.8 is back in business. :dance2:

So this shows us that the IDM blocklist was absolutely untested by even the developer!! :wtf: Unbelievable. They wanted to blocklist old versions of IDM for only Firefox 4.0 Beta 1 and up, but instead they blocklisted ALL versions of IDM if your Firefox version is below 3.7 (i.e. all current non-Beta versions of Firefox). Unbelievable. It would be nice if Firefox would test their fixes. :rolleyes:

Thanks for the workaround, KotaXor. :D

EDIT:

@jofre: Thanks for confirming that the quick fix worked for you. :D

[Night Owl]

Here is the latest news directly from the Firefox and IDM developers. IDM CC 6.9.9 was issued to work around a Firefox bug (according to IDM's software engineer). All of this nonsense because Firefox has a bug and simply blocklisted instead of fixing their problem. :frusty: Hopefully, the IDM software engineer will open an official bug report.

Comment 30 Dave Townsend (:Mossop) 2010-07-20 20:39:32 PDT

(In reply to comment #27)

> What I see in the blocklist

> snip...

I can confirm this. This means that all versions of IDM are blocked for all

versions of Firefox up to 3.7 right now.

Comment 31 Jorge Villalobos [:jorgev] 2010-07-20 20:52:46 PDT

I reopened the IT bug that was filed to do this. Hopefully it will be dealt

with soon.

Comment 32 Michael Morgan [:morgamic] 2010-07-20 21:44:39 PDT

Block was rolled back; I messed up the min/max.

Looks like it should be:

<versionRange minVersion="3.7a1pre" maxVersion="4.0"/>

Sorry folks.

Comment 33 Adrian 2010-07-20 21:50:36 PDT

So, then how do you get FF to unblock it? Mine is still blocked.

Comment 34 Michael Morgan [:morgamic] 2010-07-20 21:58:52 PDT

It'll ping again and update the blocklist.xml within 24 hours but a quicker

alternative is to update the blocklist.xml file manually to remove the invalid

range.

Info on the blocklist file is here:

https://wiki.mozilla.org/Extension_Blocklisting:Testing#The_Blocklist_File

You'd want to remove the bad XML section, which is as follows:

<versionRange>

<targetApplication id="{ec8030f7-c20a-464f-9b0e-13a3a9e97384}">

<versionRange minVersion=" " maxVersion="3.7"/>

</targetApplication>

</versionRange>

Comment 35 Robert Strong [:rs] (do not email) 2010-07-21 00:02:57 PDT

You can also do the following to make the blocklist service update immediately

Open Tools -> Error Console

In the code box paste the following line (all of it should be one line from

Components to (null);.

Components.classes["@mozilla.org/extensions/blocklist;1"].getService(Components.interfaces.nsIBlocklistService).QueryInterface(Components.interfaces.nsITimerCallback).notify(null);

Press enter

Comment 36 tdba.316 2010-07-21 02:40:07 PDT

the latest version of IDM CC at

http://www.internetdownloadmanager.com/idmmzcc/4.02b/idmmzcc.xpi (6.9.9) fixed

the issues and compatibility problems with firefox 4.

Comment 37 Charles Jones 2010-07-21 02:46:02 PDT

I'm really tired to write to Firefox forums that

1. IDM CC 6.9.9 has a workaround and Firefox 3.7 and 4.0 DO NOT crash anymore

with this version of extension

2. The reason of crash is FIREFOX BUG inside nsISeletion::ToString()

implementation! Please FIX your bug instead of blacklisting!

Best regards,

Charles Jones

Software engineer

Tonec Inc.

641 Lexington Avenue, 15th fl.

New York, NY, 10022

Comment 38 Reed Loden [:reed] (sporadically busy until Aug. 6th) 2010-07-21 03:09:51 PDT

(In reply to comment #37)

> 2. The reason of crash is FIREFOX BUG inside nsISeletion::ToString()

> implementation! Please FIX your bug instead of blacklisting!

As you were informed in comment #23, you should file a bug on the issue you're

seeing. Commenting here doesn't get anything fixed if there is some type of bug

in Gecko.

Source

[*dcs18]

@ Night Owl

Glad you got back your browser integration. ;)

[Night Owl]

@dcs18: Thanks. :)

Hmmm, somebody this morning told the Firefox developers what they can do and should do. :whistle: I wonder who it was. :whistle:

(In reply to comment #32)

> Block was rolled back; I messed up the min/max.

>

> Looks like it should be:

> <versionRange minVersion="3.7a1pre" maxVersion="4.0"/>

>

> Sorry folks.

As admitted in comment 32 (and other comments), the blocking code was

completely wrong. Obviously, it was not even tested by the developer.

Is it possible that all future blocklists will have to be tested by the

developer as well as a test team to ensure that such an obvious bug doesn't

affect a lot of users again?

I am still in disbelief that Firefox developers make code changes without any developer testing and without any testing from a test team. :eek: The developer corrected his huge mistake by saying 'Looks like it should be' without any testing yet again. :o Shame on Firefox. :bag: