Closed
Bug 945265
Opened 11 years ago
Closed 11 years ago
Submitted apps are incomplete after Content Rating is added
Categories
(Marketplace Graveyard :: Developer Pages, defect, P1)
Tracking
(Not tracked)
VERIFIED
FIXED
2013-12-17
People
(Reporter: julian.mozbugs, Assigned: kngo)
References
Details
Steps to reproduce: 1. Load Submit a New App page https://marketplace-dev.allizom.org/developers/submit/ 2. Submit a free app 3. Add Content Rating certificate 4. Go to the Status page of the app. Expected results: App status is Pending Approval. Actual results: The app status is Incomplete. Also, "Please complete your app." link takes the user to the Edit Listing page and does not give a clear message why the app is incomplete. If we click the "Edit" button from the Content Rating page, and then Submit the actual ID and Code, "Oops!" page is displayed. Notes/Issues: Verified on FF28 (Win 7). Screencast for this issue http://screencast.com/t/0FVIQl5YeQS
Comment 1•11 years ago
|
||
I'm guessing these are related? http://sentry.dmz.phx1.mozilla.com/addons/marketplace-dev/group/17228/
Comment 2•11 years ago
|
||
https://github.com/mozilla/zamboni/commit/e25a2c8
Assignee: nobody → robhudson.mozbugs
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Reporter | ||
Comment 3•11 years ago
|
||
The "Oops" page is no longer displayed after submitting the actual ID and Code, but the App remains incomplete after submission and Content Rating already set up. Only after we Edit and Submit the actual ID and Code for Content Rating, the app changes its state to Pending Approval. Please see screencast http://screencast.com/t/xLN0GHOX
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Comment 4•11 years ago
|
||
It looks like possibly the pingback API isn't updating the app completion status.
Assignee | ||
Comment 5•11 years ago
|
||
Couldn't get to the bottom of this. Here's what I found: - ContentRating has a post_save to update the app status. - set_content_ratings calls ContentRating.safer_get_or_create, which calls the post_save. - calling set_content_ratings in the shell updates the app's status, for a submitted app that hasn't yet gotten content rating. - tests on the pingback API correctly update the status - the actual pingback API sets the content ratings, but fails to update the status
Updated•11 years ago
|
Priority: -- → P1
Assignee | ||
Comment 6•11 years ago
|
||
https://github.com/mozilla/zamboni/pull/1494/
Assignee: robhudson.mozbugs → kngo
Status: REOPENED → RESOLVED
Closed: 11 years ago → 11 years ago
Resolution: --- → FIXED
Target Milestone: 2013-12-03 → 2013-12-10
Reporter | ||
Comment 7•11 years ago
|
||
Issue is still reproducing in https://marketplace-dev.allizom.org/developers/ on FF28 (Win 7). See app https://marketplace-dev.allizom.org/developers/app/test-app-automatikb/status
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Assignee | ||
Comment 8•11 years ago
|
||
Whoops, put the code in the wrong file. https://github.com/mozilla/zamboni/commit/fc5c2f0aa9be1534b81e4bb19603ec698a233e80
Status: REOPENED → RESOLVED
Closed: 11 years ago → 11 years ago
Resolution: --- → FIXED
Assignee | ||
Comment 9•11 years ago
|
||
The JS is refreshing the page, killing the connection, before the status is updated.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Comment 10•11 years ago
|
||
Can we please consider moving this out of the submission flow?
Assignee | ||
Comment 11•11 years ago
|
||
Well, it's not in the main submission flow. Just something that is required to be done afterwards. It sucks, but apps need to get a content rating to be approved. Maybe an alternative flow would to be require apps to have content rating to be listed, but not approved?
Assignee | ||
Comment 12•11 years ago
|
||
https://github.com/mozilla/zamboni/pull/1532
Status: REOPENED → RESOLVED
Closed: 11 years ago → 11 years ago
Resolution: --- → FIXED
Target Milestone: 2013-12-10 → 2013-12-17
Reporter | ||
Comment 13•11 years ago
|
||
Verified as fixed in https://marketplace-dev.allizom.org/developers/ on FF29 (Win 7). Closing bug.
Status: RESOLVED → VERIFIED
Assignee | ||
Comment 14•11 years ago
|
||
Thanks, Rob for the sleuthing.
You need to log in
before you can comment on or make changes to this bug.
Description
•