292711 - Need to disable auto update for Flashblock extension on a.u.m.o ASAP

Status: RESOLVED FIXED

(addons.mozilla.org Graveyard :: Public Pages, defect)

Description

[Philip Chee]

User-Agent:       Mozilla/5.0 (X11; U; SunOS i86pc; en-US; rv:1.8a6) Gecko/20050111 MultiZilla/1.8.0.0a Mnenhy/0.7.2.0
Build Identifier: Mozilla/5.0 (X11; U; SunOS i86pc; en-US; rv:1.8a6) Gecko/20050111 MultiZilla/1.8.0.0a Mnenhy/0.7.2.0

Due to current bugs in the Firefox EM, flashblock needs to be manually
uninstalled before a new version is installed. Otherwise with autoupdate the
following error will occur:

Chrome Registration failed for Extension
'{3d7eb24f-2740-49df-8937-200b1cc08f8a}' when calling
nsIXULChromeRegistry::installPackage with this chrome path:
jar:file:///home/xavier/.firefox/default/7csoq75a.slt/extensions/%7B3d7eb24f-2740-49df-8937-200b1cc08f8a%7D/chrome/flashblock.jar!/content/flashblock/
(profile extension = true). Perhaps this path does not exist within the chrome
JAR file, or the contents.rdf file at that location is malformed?

And chrome may sometimes be messed up.

EM bug that affects flashblock is fixed on trunk so keep autoupdate disabled
until FF 1.1 is out.

Reproducible: Always

Comment 1

[Xavier Mouton-Dubosc]

Better with the faulty browser ID:
Firefox 1.0.3
Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.7) Gecko/20050414 Firefox/1.0.3

Comment 2

[alanjstr]

We are unable to disable automatic updates for extensions.  The only way to not
push an update is to remove it from the site.

Comment 3

[Cameron]

Could you create a simple update for the extension that simply brings up a box
saying "Flashblock needs to be uninstalled in order to install the next version.
Please uninstall flashblock by clicking [here] and then download the latest
version from [here]. It's very important that you do this in order to keep up
with development. The next version solves bugs with this and that, improves such
and such a feature, etc. etc." 

or something like that?

Comment 4

[Philip Chee]

> Could you create a simple update for the extension that simply brings up a box
> saying "Flashblock needs to be uninstalled in order to install the next version.

In firefox, before a dummy extension can bring up any box it has to be installed
first. However, I think that any update including a dummy extension will cause
chrome registration errors if an existing flashblock.jar already exists.

In mozilla with the install.js script method this is doable, however mozilla
does not have the autoupdate function which is causing this problem. For mozilla
a warning on the extension info page would be sufficient. However I don't know
when Lorenzo is able to update the Flashblock info page on a.u.m.o and the rest
of the developers have no modify/write rights to that page.

Comment 5

[Cameron]

I have reviewed your extension and added a short note about not using
auto-update. Strictly this should be in the "developer comments" section, so
could you please get Lorenzo to add it there? Please reply to this bug or email
me when this has been done.

Comment 6

[Lorenzo Colitti]

(In reply to comment #5)
> I have reviewed your extension and added a short note about not using
> auto-update. Strictly this should be in the "developer comments" section, so
> could you please get Lorenzo to add it there? Please reply to this bug or email
> me when this has been done.

Done. Sorry for not being more on the ball on this, but I'm out of town at a
conference...

Comment 7

[Cameron]

(In reply to comment #6)

No worries mate, I've now removed the note from the editor's review :) 

Comment 8

[Chris Blore]

Has this issue now been resolved?

Comment 9

[Philip Chee]

It should be. Flashblock 1.5 is only compatible with Firefox 1.5 upwards so those still using Firefox 1.0.7 should not get any autoupdates right? Lorenzo, please confirm.

Comment 10

[Lorenzo Colitti]

(In reply to comment #9)
> It should be. Flashblock 1.5 is only compatible with Firefox 1.5 upwards so
> those still using Firefox 1.0.7 should not get any autoupdates right? Lorenzo,
> please confirm.

Yep, that was the intention, anyway...