Closed Bug 1028908 Opened 10 years ago Closed 10 years ago

Content rating can't be set on stage

Categories

(Marketplace Graveyard :: Developer Pages, defect, P2)

Avenir
x86_64
Windows 7
defect

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 1041446
2014-06-24

People

(Reporter: madalin.cotetiu, Unassigned)

References

()

Details

Steps to reproduce: 1.Open developer hub and submit a new app or open content rating for an app without content rating set: https://marketplace.allizom.org/developers/app/test-app-seal1717/content_ratings/edit 2. Click on Create an IARC Ratings Certificate 3. Fill the forms in Global Rating Tool and click the confirm button Expected results: The rating for the app is set, the submission process is completed Actual results: The rating is not set, the GET request for the rating fails with a 404 Notes/Issues: Reproducible on stage and dev Verified on FF33 (Win 7). Screencasts for this issue: http://screencast.com/t/ZnswBijN0DFz
Krupa - is this still a thing? Kevin - is this related to the Australian stuff? Are we set up to not fail now if new ratings get added that we don't know about?
Priority: -- → P2
(In reply to Wil Clouser [:clouserw] from comment #1) > Krupa - is this still a thing? > > Kevin - is this related to the Australian stuff? Are we set up to not fail > now if new ratings get added that we don't know about? I still can reproduce it. here is the screencast: http://screencast.com/t/PZbGOzqCavi
After my last comment this issue stopped reproducing but now I can reproduce it again screencast: http://screencast.com/t/BpL2ARXR Also when trying to complete in the "Already Have Your App Rated?" section with the security code and the submission id sent via email the "Invalid submission ID or security code" message is displayed. screencast: http://screencast.com/t/pSIooYEbur
This looks like a duplicate of bug 1041446
Summary: Content ratting can't be set on stage → Content rating can't be set on stage
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.