963796 - Unable to edit my own Add-on

Status: RESOLVED FIXED

(addons.mozilla.org Graveyard :: Add-on Validation, defect)

Description

[(not reading bugmail) Nick Desaulniers [:\n]]

I get the following when trying to do anything [0] with an app listed under my submissions:


Oops! Not allowed.

You tried to do something that you weren't allowed to.

[0] https://addons.mozilla.org/en-US/developers/addon/webgl-inspector/edit

Comment 1

[Jorge Villalobos [:jorgev] (he/him)]

Please try accessing that page in an hour or so and let us know if the problem persists.

Comment 2

[(not reading bugmail) Nick Desaulniers [:\n]]

No luck, :jorgev.  Can the add-on be deleted so that I may resubmit it?

Comment 3

[Jorge Villalobos [:jorgev] (he/him)]

Did you run into any problems creating your account initially? I know your email address is the same Nick Nguyen used before, and you admin page shows nicknguyen as your username.

Comment 4

[(not reading bugmail) Nick Desaulniers [:\n]]

Yes, I use the email alias nick at mozilla.  When I did the password reset for my account, I was able to get in.  So, using an alias for AMO submissions is probably a bad idea, since the aliases can change when MoCo employees come and go.  I'm still not sure how changing my username is preventing me from editing my own add on, maybe the database is somehow keyed on the old username (and this bug is related to changing your AMO username)???

Comment 5

[(not reading bugmail) Nick Desaulniers [:\n]]

If I go to account settings, my username is `nickdesaulniers`, which I believe I changed from nicknguyen.

Comment 6

[Jorge Villalobos [:jorgev] (he/him)]

Wil, any ideas why Nick can't access his own add-on listing? I suspect it has to do with the changes he did to a pre-existing account, but I don't know how to locate the reason behind the error message.

Comment 7

[Wil Clouser [:clouserw]]

That account was pretty messed up.  Maybe something to do with Marketplace/AMO/Persona interaction.  There was no dev agreement and the user id was null.  I fixed with these statements:

> mysql> update users set user_id=8889098, read_dev_agreement=NOW() where id=8889098 limit 1;
> Query OK, 1 row affected (0.00 sec)
> Rows matched: 1  Changed: 1  Warnings: 0
> 
> mysql> update auth_user set username="nickdesaulniers" where id=8889098 limit 1;
> Query OK, 1 row affected (0.00 sec)
> Rows matched: 1  Changed: 1  Warnings: 0

Worth noting that the two password fields don't match still.  I assume we're going to fix all this up when we fix the users vs auth_user debacle so calling this fixed for now.  CCing ashort just to keep him in the loop.  Thanks everyone.