291024 - UMO has broken links to XPIs (.../extensions/undefined)

Status: RESOLVED WORKSFORME

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

Description

[J. Penn]

User-Agent:       Mozilla/5.0 (Macintosh; U; PPC Mac OS X; en-us) AppleWebKit/125.5.7 (KHTML, like Gecko) Safari/125.12
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.6) Gecko/20050317 Firefox/1.0.2

I keep getting an error message, from FireFox's built-in extensions manager quite frequently on some 
of the extensions that I'm attempting to download:

MESSAGE:
"Firefox could not download the file at
https://addons.update.mozilla.org/extension/undefined

because: Not a valid install package

END MESSAGE

I'm able to consistently reproduce this problem, and I'm not sure who to address this error to, but I'm 
running Mac OSX version 10.3.8.
on an

SOFTWARE/HARDWARE PALTFORM:
Apple Dual G5 1.8 (1.5 GB DDR SDRAM) and



Reproducible: Always

Steps to Reproduce:
1. Open FireFox browser

2.  Goto MENU> TOOLS> Extentions  (Extensions window opens)

3. Click on "Get More Extensions"  (takes me to URL: https://addons.update.mozilla.org/extensions/?
application={ec8030f7-c20a-464f-9b0e-13a3a9e97384}

4.  Click on Miscellaneous" in Left-hand Navigation Menu then select Adsense Notifier 0.3.1and click on 
"INSTALL" > window drops down and verifies URL source of extension in this case: https://
addons.update.mozilla.org/extensions/undefined

5. Click on "INSTALL NOW" the message appears in a 2x5 inch box with the aforementioned error 
message.

6. I click O.K. to escape & close message window

Actual Results:  
6. I click O.K. to escape & close message window

MESSAGE:
"Firefox could not download the file at
https://addons.update.mozilla.org/extension/undefined

because: Not a valid install package

END MESSAGE


Expected Results:  
The extension would download and show up in the download manager (window)

Also, the extension found on an outside website for FireFox called "infoRSS vers 0.8.7 found at URL:  
http://inforss.mozdev.org/installation.html
has download to my desktop as an .xpi file, but I can find instructions on how to add that to FireFox 
extensions...

Thanks in advance for you help and quick reply!

Comment 1

[Nickolay_Ponomarev]

Can't reproduce on Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b2)
Gecko/20050412 Firefox/1.0+

In step 4 I get to this page:
https://addons.update.mozilla.org/extensions/showlist.php?application=firefox&category=Miscellaneous

And the URL to the XPI is
http://ftp.mozilla.org/pub/mozilla.org/extensions/adsense_notifier/adsense_notifier-0.3.1-fx.xpi
not https://addons.update.mozilla.org/extension/undefined as it seems to be for
you. Care to try again?

You can install XPI files by dragging them to Firefox window or to the Extension
Manager window (not sure if it works on Mac); also you can open XPIs with File >
Open

Comment 2

[Nickolay_Ponomarev]

btw: This is similar to bug 277556; that one is reported on WinXP

Comment 3

[littlej007]

Same error message when using a PC.  I can no longer install Extensions, but
used to be able to do so.

Comment 4

[Nickolay_Ponomarev]

Okay, bug 277556 is confirmed as a xpinstall bug (wrong error code), moving this
one to UMO, it shouldn't ever hand out "a.u.m.o/extensions/undefined" URL for
XPI. I could not reproduce this, but it's not a EM bug.

Comment 5

[alanjstr]

When a page serves up a 404 error instead of an XPI, Firefox should detect that
it is a file not found before it tries to actually install it.

Comment 6

[Nickolay_Ponomarev]

Yeah, and as I understand, bug 277556 will fix it (if not, a follow-up will be
required). But UMO shouldn't serve 404 XPIs in first place. See also bug 285105.

Comment 7

[Cameron]

AMO has just been revaqmped. Are you still able to reproduce?

Comment 8

[Michael Morgan [:morgamic]]

Mass change - bugs to be read / (re)confirmed.

Comment 9

[Cameron]

Unable to reproduce on Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1a3) Gecko/20060526 BonEcho/2.0a3. Things have changed a lot since you reported this bug. Bug 254632 is known, but the whole /undefined bit I'm not sure about. if you're still able to reproduce this, please reopen.