ISSUES THAT DO NOT FOLLOW THIS TEMPLATE WILL BE CLOSED IMMEDIATELY.
Expected Behavior
For the login form. If the email of a not existing user is in the correct format (for example xx@xx.com) and a fake password is provided the error notification says: "Email is not valid".
(rdbg) @user_session # ruby
#<UserSession: {:email=>"xx@xx.com", :password=>"<protected>"}>
(rdbg) @user_session.errors # ruby
#<ActiveModel::Errors [#<ActiveModel::Error attribute=email, type=is not valid, options={}>]>
Additionally, the error message can't be translated using official translation keys. Other errors can be translated successfuly.
pl:
authlogic:
error_messages:
...
email_invalid: xxx should look like an email address.
...
Actual Behavior
The actual error message should be of type general_credentials_error because the email is valid. It simply doesn't exist in the database, but that information should not be exposed.
ISSUES THAT DO NOT FOLLOW THIS TEMPLATE WILL BE CLOSED IMMEDIATELY.
StackOverflow.
guide
for instructions.
responding promptly to feedback.
Expected Behavior
For the login form. If the email of a not existing user is in the correct format (for example xx@xx.com) and a fake password is provided the error notification says: "Email is not valid".
Additionally, the error message can't be translated using official translation keys. Other errors can be translated successfuly.
Actual Behavior
The actual error message should be of type
general_credentials_errorbecause the email is valid. It simply doesn't exist in the database, but that information should not be exposed.