Closed
Bug 390695
Opened 19 years ago
Closed 19 years ago
Front page install links show incomplete versions
Categories
(addons.mozilla.org Graveyard :: Public Pages, defect)
Tracking
(Not tracked)
VERIFIED
FIXED
People
(Reporter: morgamic, Assigned: wenzel)
Details
Attachments
(2 files)
|
29.35 KB,
image/jpeg
|
Details | |
|
761 bytes,
patch
|
morgamic
:
review+
|
Details | Diff | Splinter Review |
I was recently talking to Tony (tchung) about a bug he found with Firebug's feature on the front page. I found that firebug had an incomplete version (no files) that had a blank hash yet it was being linked to in the front page install link. This was producing a hash error as you could imagine.
However, the add-ons detail page had the correct install link as well as the recommended page. We need to figure out the difference between details page install boxes and feature install boxes -- in particular the query that gets us the file id used in the download controller URL. They should not be different.
Comment 1•19 years ago
|
||
I ran into the exact same thing with the Facebook App that Stephen caught - have to use Version->getVersionByAddonId().
Comment 2•19 years ago
|
||
| Assignee | ||
Updated•19 years ago
|
Assignee: nobody → fwenzel
| Assignee | ||
Comment 3•19 years ago
|
||
This patch should fix it: As fligtar suggested, we have a function to find the latest (valid) version, so I am using it.
Attachment #275228 -
Flags: review?(morgamic)
| Reporter | ||
Comment 4•19 years ago
|
||
Comment on attachment 275228 [details] [diff] [review]
patch using getVersionByAddonId
Looks good.
Attachment #275228 -
Flags: review?(morgamic) → review+
| Assignee | ||
Comment 5•19 years ago
|
||
I committed this to SVN r5657. Happy happy, joy joy.
Status: NEW → RESOLVED
Closed: 19 years ago
Resolution: --- → FIXED
Comment 6•18 years ago
|
||
Verified FIXED; haven't run into this problem in my >=3.2 testing.
Status: RESOLVED → VERIFIED
Updated•10 years ago
|
Product: addons.mozilla.org → addons.mozilla.org Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•