If you are uploading an Update, select from the radio buttons but don't pick the right one in the dropdown, it seems that it will create the entry with an ID of the wrong theme. For example, if I upload Doodle, but leave the dropdown on 708, it will create a new version of 708. If, as an author, I have 10 themes, this could get messy. Shouldn't we detect a GUID mismatch?

Yeah, mismatch should be detected, although the author should definitally be allowed to change the UID for their theme/extension.

Yeah, the mismatch should be.. Under what conditions would an author be allowed to change the UID though?

If for example an author used someone elses code as a template, then submited the extension, you'd have a problem. This could happen to extensions that aren't listed on U.M.O like TBE or Spellbound as examples. Or even the same author who has various extensions. As long as it's easy for the authors to delete one of their listings easily then perhaps this is not an issue (although the mismatch still is). just my 2 cents

In theory, that situation doesn't create a "we need to allow a change in GUID" case. That theme or extension should be rejected entirely. GUID/Author mismatch. As it'd also cause problems in Firefox that can't be solved by fiddling with DB data.

This affects extensions too. Modifiying summary.

As the add process now cares about the GUID and doesn't blindly believe the drop-down, this is fixed for non-legacy extensions/themes. Legacy items, it's basically not possible to fix. As there's no way to know what the file is in an intelligent manner.

In which case do we still provide a dropdown? Does that dropdown show those that we have a GUID for, or just those we do not? What if someone adds a GUID to a legacy? How will that be handled?

Bulk Moving Developer Control Panel bugs to new component. (Filter: massdevcpspam)

Mass-resolving bugs that have been fixed on trunk.

Sorry for the bugspam, reopening bugs wrongly marked as resolved.