Closed
Bug 282144
Opened 20 years ago
Closed 16 years ago
[Submission] Detect change of GUID
Categories
(addons.mozilla.org Graveyard :: Developer Pages, defect)
Tracking
(Not tracked)
VERIFIED
FIXED
3.5
People
(Reporter: Bugzilla-alanjstrBugs, Assigned: fligtar)
Details
Attachments
(1 file)
|
145.57 KB,
image/png
|
Details |
At least 3% of authors change their GUID, perhaps without understanding its purpose. We should detect whether the same author has submitted an extension by the same name with a different GUID and give them the opportunity to cancel their update. There is currently no indication that the GUID has changed today. The only way I notice is that I am an Admin and it tries to create it under my email address.
Comment 1•19 years ago
|
||
In some case the GUID change is necessary (e.g. when a valid GUID in firefox is
refused by deer park - try {ff1f5c85-cc94-de02-c1f-423e25cca685}).
When this happens, the author should be able to remove the previous version and
then upload the new one.
If this is not possible, there should be at least a way to desupport an
extension (a delete button on the site?).
You should be able to delete the extension from the site. However, this need does arise occasionally, due to conflicts and problems with the original upload.
Severity: normal → minor
Target Milestone: 1.0 → 2.0
Summary: Detect change of GUID → [Submission] Detect change of GUID
Comment 3•19 years ago
|
||
Mass change - bugs to be read / (re)confirmed.
Assignee: Bugzilla-alanjstrBugs → nobody
Priority: -- → P5
AMO bugspam. Correcting QA contacts on OLD bugs (mozilla.update@update.bugs) -> Correct QA contact (developers@add-ons.bugs) Filtermeplzkthx
QA Contact: mozilla.update → developers
reconfirming, authors should be notified of this, although still allowed to actually do it probably.
Priority: P5 → --
Target Milestone: 2.0 → ---
| Assignee | ||
Updated•18 years ago
|
Target Milestone: --- → Future
| Assignee | ||
Comment 7•16 years ago
|
||
I'm going to call this fixed in 3.5. Until now, there was no real difference between the submit new add-on page and the update add-on page. If you submitted a new add-on as an update to another add-on with a different GUID, it just switched modes automatically. In 3.5, this is not the case, and if you are uploading an update to an existing add-on with a different GUID, you are told that the GUID doesn't match. In order to upload that new GUID, you have to explicitly go to the Submit New Add-on page and go through an intro and developer agreement that should make it pretty clear to anyone that you're about to submit a brand new add-on.
Assignee: nobody → fligtar
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → FIXED
Target Milestone: Future → 3.5
Comment 8•16 years ago
|
||
fligtar: that's the correct error message, right? https://bugzilla.mozilla.org/show_bug.cgi?id=282144#c7 states that it'll say the GUIDs "don't match", but this message just notes that it's invalid. Still, verified FIXED?
| Assignee | ||
Comment 9•16 years ago
|
||
Not the right message. That means your GUID isn't properly formatted. Looks like it might be missing { }Yeah, sorry; here we go: https://remora-3.5.php5stage.mozilla.com/en-US/developers/versions/add/7522 "Oops! There seems to be a problem with this file... The add-on GUID used in this file ({4fd24fd7-d31f-4a87-a001-cc1a5f72aa26}) does not match the existing GUID for this add-on (stephend2@mozilla.com). Please correct this problem and upload your file again." Verified FIXED
Status: RESOLVED → VERIFIED
Updated•9 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
•