Closed Bug 1210032 Opened 9 years ago Closed 9 years ago

Re-allow large GUIDs

Categories

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

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: andy+bugzilla, Unassigned)

Details

This is a reminder to ourselves. In this iteration, let's flip the right waffle "allow-long-addon-guid" as per bug 1203915 comment 4 so that add-ons can be submitted to the dev hub and they will work on stable releases of Firefox.
Iteration: --- → 44.3 - Nov 2
Done on prod.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Verified as fixed : http://screencast.com/t/qwZZKsYBZ
Status: RESOLVED → VERIFIED
Sorry , I reopened this too fast. Even if the validation passed I cant go to step 3 for a very lob guid (<em:id>assdasssdddassdasssdddassdasssdddassdasssdddassdasssdddassdasssdddassdasssdddassdasssdddassdasssdddassdasssdddassdasssdddassdasssdddassdasssdddassdasssdddassdasssdddassdasssdddassdasssdddassdasssdddasssadasdasdasdasdasssdddassdasssdddassdasssdddassdasssdddassdasssdddassdasssdddassdasssdddassdasssdddassdasssdddassdasssdddassdasssdddassdasssdddassdasssdddassdasssdddassdasssdddassdasssdddassdasssdddassdasssdddassdasssdddassdasssdddassdasssdddassdasssdddassdasssdddassdasssdddassdasssdddassdasssdddassdasssddd@assasa.com</em:id>). The "Oops..." page is displayed when trying to move to step 3 of submission.

Please note that this is NOT reproducible for Stage or -dev.
Status: VERIFIED → REOPENED
Resolution: FIXED → ---
http://sentry.mktmon.services.phx1.mozilla.com/mkt/addonsmozillaorg/group/20213/
Fair enough, there is a limit to the size of the guid in our database and its 255. We should probably add a new bug for that issue and stop it in the validator. 

This bug was to allow a guid of more than 64 to go through.
Status: REOPENED → RESOLVED
Closed: 9 years ago9 years ago
Resolution: --- → FIXED
https://github.com/mozilla/addons-validator/issues/214 opened.
Product: addons.mozilla.org → addons.mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.