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
Describe the bug
Any error registering seems to simply state "Server Responded: Please check the server logs for more details." which is out of the ability of most users. In this specific case, it was that the user had already registered with that same email.
To Reproduce
Steps to reproduce the behavior:
Register a new account
Register another new account with that same email
Unhelpful server response.
Expected behavior
Tell the user what's up.
Screenshots
Reported by an end user, this is the best I have:
In this case server logs had a much clearer answer: Key (email)=([snip]) already exists.
Additional context
I understand the potential want for security through keeping registered addresses secret, but this really just adds frustration to the registration process.
The text was updated successfully, but these errors were encountered:
Describe the bug
Any error registering seems to simply state "Server Responded: Please check the server logs for more details." which is out of the ability of most users. In this specific case, it was that the user had already registered with that same email.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Tell the user what's up.
Screenshots

Reported by an end user, this is the best I have:
In this case server logs had a much clearer answer:
Key (email)=([snip]) already exists.
Additional context
I understand the potential want for security through keeping registered addresses secret, but this really just adds frustration to the registration process.
The text was updated successfully, but these errors were encountered: