Closed Bug 523499 Opened 15 years ago Closed 15 years ago

Changing add-on listing type

Categories

(addons.mozilla.org Graveyard :: Developer Pages, defect, P1)

defect

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: fligtar, Assigned: wenzel)

References

()

Details

Attachments

(2 files)

Add-ons can be changed between hosted and listed status, but not without a process: If the add-on is currently hosted and wants to become listed-only: * using the Change Status page, the user chooses this option and is presented with a confirmation page that explains the following * all existing versions and files will be deleted, but please try to keep approval/review history * contributions will be turned off * access to the statistics dashboard will be lost * all fields that listed add-ons do not have access to will be cleared (EULA) If the add-on is currently listed and wants to become hosted: * using the Change Status page, the user chooses this option and is presented with a confirmation page. The user must then accept the Developer Agreement. * access to all of the hosted pages is enabled, and the add-on is moved to "Incomplete" status * the user is directed to the New Version page where they may upload the first file for their add-on and continue that process as normal Copy and layout for the confirmation pages and Change Status changes will be forthcoming.
Depends on: 523501
Attached image mockup
Here's a mockup of the Change Status page.
(In reply to comment #1) > Created an attachment (id=408144) [details] > mockup > > Here's a mockup of the Change Status page. Thanks Fligtar. One change on the second one, "Mozilla-hosted add-ons must upload their add-ons..." doesn't sound right.
Yeah, let's change that part to: Mozilla-hosted add-ons must be reviewed by an editor before...
Attached patch Patch, rev. 1Splinter Review
Here, try this. Do we need a new confirmation page / message for this where we explain what the user *should* do? When changing to "listed" for example, the "fake" version won't magically acquire compatibility information, the user *should* add it though. Likewise, they'll need to set their homepage field if they haven't done that already. On the other hand, we might not want to over-complicate it and leave it as-is. If the user wants their add-on to be found on the site, they'll probably add compatibility information. Opinions?
Attachment #409701 - Flags: review?(clouserw)
Status: NEW → ASSIGNED
Comment on attachment 409701 [details] [diff] [review] Patch, rev. 1 Please add a check for add-on type. I shouldn't be able to make a search engine self hosted.
Attachment #409701 - Flags: review?(clouserw) → review+
(In reply to comment #5) > (From update of attachment 409701 [details] [diff] [review]) r54853 > Please add a check for add-on type. I shouldn't be able to make a search > engine self hosted. Good catch, thanks! r54855 I'm marking this fixed for now, as it is feature-complete. Please reopen if anything is missing.
Status: ASSIGNED → RESOLVED
Closed: 15 years ago
Keywords: push-needed
Resolution: --- → FIXED
Thanks Fred. You raised some good points and I'll file separate bugs after a little experimentation.
Verified, FIXED.
Status: RESOLVED → VERIFIED
Product: addons.mozilla.org → addons.mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: