Closed
Bug 615139
Opened 14 years ago
Closed 13 years ago
Add-on 404 pages should be more informative
Categories
(addons.mozilla.org Graveyard :: Public Pages, defect, P5)
addons.mozilla.org Graveyard
Public Pages
Tracking
(Not tracked)
VERIFIED
FIXED
6.0.12
People
(Reporter: idrug.oy, Assigned: andy+bugzilla)
References
()
Details
Attachments
(1 file)
229.32 KB,
image/png
|
Details |
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:2.0b8pre) Gecko/20101128 Firefox/4.0b8pre Build Identifier: Here is an example: https://addons.mozilla.org/en-US/firefox/addon/3002/ this is "Stop Autoplay" add-on, it's last version was uploaded to AMO at 20th of sept. Then it just disappeared with no explanations why. There are also other examples, like http://releases.mozilla.org/pub/mozilla.org/addons/3698/ (this disappeared long ago, but still - the reasons are unknown for users). Add some kind of notes on why the extensions were removed from AMO, if you delete them from there. Reproducible: Always
Comment 1•14 years ago
|
||
In both of those cases, the developer chose to make the add-on inactive. But you're right about these pages not being clear about the reason. I'm not sure if this has been considered for the current redesign, so I'm keeping it open.
Severity: major → minor
Status: UNCONFIRMED → NEW
Component: Blocklisting → Public Pages
Ever confirmed: true
QA Contact: blocklisting → web-ui
Summary: Why the extension keep disappearing from AMO? Add some kind of notes explaining the reasons to those pages. → Add-on 404 pages should be more informative
Target Milestone: --- → 4.x (triaged)
Updated•14 years ago
|
Whiteboard: [ddn]
Comment 2•14 years ago
|
||
I'm fine with being a little more specific: "This add-on has been removed by its author." "This add-on has been disabled by an administrator." and then using the current default for any other reason (incomplete, etc.)
Updated•14 years ago
|
Whiteboard: [ddn]
Comment 3•13 years ago
|
||
Add-on authors and admins should have some more pages here too.
Priority: -- → P4
Target Milestone: 4.x (triaged) → Q2 2011
Comment 4•13 years ago
|
||
We can use the standard message box if it looks decent on the page. It's worth noting that PHP is still serving up our 404 pages in production. I'll see if we can switch that. Either way though, this will be there when we can use it.
Assignee: nobody → amckay
Priority: P4 → P5
Target Milestone: Q2 2011 → 6.0.12
Assignee | ||
Comment 5•13 years ago
|
||
https://github.com/jbalogh/zamboni/commit/b87c33c26beeac247742fbc9e5e97a2c79339b69
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Comment 6•13 years ago
|
||
QA: You'll need to be on /z/ to see this
Comment 7•13 years ago
|
||
(In reply to comment #6) > QA: You'll need to be on /z/ to see this I didn't have to do that. verified that * admin-disabled add-ons show https://addons.allizom.org/en-US/firefox/addon/bwfb/ * user-disabled add-ons show https://addons.allizom.org/en-US/firefox/addon/he-heha-ha-182409/ adding junk characters to the URL loads the remora page https://addons.allizom.org/en-US/firefox/addon/he-heha-ha-182411/
Status: RESOLVED → VERIFIED
Comment 8•13 years ago
|
||
Updated•8 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
•