You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If a new user misses the account activation, it can be difficult to know why logging in is failing (e.g. if the email never arrives - for whatever reason - e.g. cheap email forwarding service).
When I tried to log in, after creating the account a while ago, I got the error: "The username or password was incorrect."
I then went to reset password, which I was able to do, but still got the same error.
I then created a new account, and still go the same error. But then I noticed the email about activating my account, which I did and then I was able to log in.
Suggestions:
Give a different message when the account is not yet activated, preferably with a link to send a new activation email.
(and / or) make the password reset activate the account (since it only works if email works).
Since the password reset email gives email addresses that can be contacted, this isn't a show-stopper.
The text was updated successfully, but these errors were encountered:
williford
changed the title
Improve message / experience when account isn't activated
Improve login message / experience when account isn't activated
Aug 30, 2024
If a new user misses the account activation, it can be difficult to know why logging in is failing (e.g. if the email never arrives - for whatever reason - e.g. cheap email forwarding service).
When I tried to log in, after creating the account a while ago, I got the error: "The username or password was incorrect."
I then went to reset password, which I was able to do, but still got the same error.
I then created a new account, and still go the same error. But then I noticed the email about activating my account, which I did and then I was able to log in.
Suggestions:
Since the password reset email gives email addresses that can be contacted, this isn't a show-stopper.
The text was updated successfully, but these errors were encountered: