Email validation is always triggering on optional fields

I solved this issue with a small local patch, if someone will get in the same spot you can use it.

This is great, thanks. You're right, we shouldn't be attempting to validate empty email addresses.

A unit test on the affected method would be sufficient for this I think and then I'll happily commit it.

Ok so looking further into this, the validator's job is to validate a string as a valid email or not. So the response it is providing is correct. Where we need to fix this is in the user Constraint which triggers the validation - it should not be testing an empty result.

The thing is though, optional email addresses for Drupal users causes problems - like not being able to use the 'forgot password' system. What are you doing to make the email address optional?

This still requires testing, but is a better solution to the issue, per #4.

I have verified that the shared patch #5 is functioning correctly. However, it would be beneficial to enhance readability and adhere to Drupal coding standards by using empty() instead of negating the assignment within the if condition.

To address this, I have prepared an updated patch that implements the recommended changes. Kindly find the attached patch file.

Hi @darvanen, the user's email is optional because most of the flow with content management is inside the project. I'm agreed with you that better to use the email address and this is not the best flow, but I've been asked, to fix a problem of creating users with no email. And yes first I've added changes to the user Constraint too. But then I thought that maybe there can be other fields that have optional email(like forms with not required field email, leave contact information or something so I added this check to the advanced email validator) So if field is required it would not let to leave field be empty then. But I guess your approach is better. Anyway, thanks for your response I will replace my patch to patch #6.

@sumit-k can you reference where in the coding standards this is mentioned please? And did you test it out with a user that has an empty email address? Please be specific about what you did to manually test the patch.

@Vadym.Tseiko fair enough, requirements are strange beasts from time to time, I imagine you used a hook of some kind to alter the User entity and the login form?

For other optional fields to use this module they will need a special implementation - which would be the place to check whether the string is empty first.

I think what this needs is a test to ensure *our* constraint doesn't fail even if the required field one does.

Oh and this is NW for tests.

Here we go.

The last submitted patch, 11: 3365661-11-test-only.patch, failed testing. View results →

Committed.

Automatically closed - issue fixed for 2 weeks with no activity.