Closed Bug 434540 Opened 12 years ago Closed 12 years ago

Submitting an empty login form leads to bogus error

Categories

(addons.mozilla.org Graveyard :: Public Pages, defect, minor)

defect
Not set
minor

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: wenzel, Assigned: rdoherty)

References

()

Details

Submitting a completely empty login form on AMO leads to a page stating "Please confirm your user account first with the code you received by email.".

That of course makes little sense and we should tell the user to fill in the blanks correctly, instead.
Btw. we already have a "this field must not be empty" string, so we don't even need new l10n for this. Woot.
Assignee: nobody → rdoherty
We're getting this error because someone, somehow, entered no email address when registering. ??

I'll create the sql query to remove it and file an IT bug.
Depends on: 445662
Hmmm..I was curious if maybe our user edit form allows users to somehow delete their email address...trying to remove one's address from https://addons.mozilla.org/en-US/firefox/users/edit then clicking save replies with "Profile Updated" but then clicking "My Account" takes you back and fills in the value. We should probably warn about that. Created bug 445664 to cover that.

Changing the value will generate a change-of-address confirmation email.
"Wrong username or password!" -> FIXED
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Duplicate of this bug: 446360
Since this isn't fixed, does bug 446360 cover it?  If so, we should just mark this a dup of that bug.
NM, this is really that "preview's DB isn't updated" bug that I always gets tripped up on, sigh.  I'll verify this in production, then?
(In reply to comment #7)
> I'll verify this in production, then?

Yes, please.
Verified FIXED; I get the "Wrong username or password!" text on https://addons.mozilla.org/en-US/firefox/users/login
Status: RESOLVED → VERIFIED
Product: addons.mozilla.org → addons.mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.