Press Ctrl / CMD + C to copy this to your clipboard.
This post will be reported to the moderators as potential spam to be looked at
In Umbraco 7.2.1MembershipHelper.RegisterMember returns Invalid email for an email with one letter domain, example "[email protected]".
"[email protected]" is totally valid email. Is it possible to fix it?
Thanks,
Alex
Hi Alex,
the actual MembershipHelper and MembershipProvider work with one letter domains if uses directly.
I think the problem is with the registration model used by the 'CreateRegistrationModel' function that has a lovely bit of RegEx on the email address ,which is i suspect where the problem lies, (see https://github.com/umbraco/Umbraco-CMS/blob/8c815554da8905bc205219465ada6f8d40667173/src/Umbraco.Web/Models/RegisterModel.cs#L50)
If you roll your own Model and Registration controller - Then the underling services are fine. (they use System.ComponentModel.DataAnnotations - which is a simple check for an @ sign nonot at the begginging as far as i can tell https://github.com/Microsoft/referencesource/blob/master/System.ComponentModel.DataAnnotations/DataAnnotations/EmailAddressAttribute.cs)
Thanks, Kevin, just fixed the issue
is working on a reply...
Write your reply to:
Upload image
Image will be uploaded when post is submitted
MembershipHelper.RegisterMember returns Invalid email for email with one letter domain
In Umbraco 7.2.1MembershipHelper.RegisterMember returns Invalid email for an email with one letter domain, example "[email protected]".
"[email protected]" is totally valid email. Is it possible to fix it?
Thanks,
Alex
Hi Alex,
the actual MembershipHelper and MembershipProvider work with one letter domains if uses directly.
I think the problem is with the registration model used by the 'CreateRegistrationModel' function that has a lovely bit of RegEx on the email address ,which is i suspect where the problem lies, (see https://github.com/umbraco/Umbraco-CMS/blob/8c815554da8905bc205219465ada6f8d40667173/src/Umbraco.Web/Models/RegisterModel.cs#L50)
If you roll your own Model and Registration controller - Then the underling services are fine. (they use System.ComponentModel.DataAnnotations - which is a simple check for an @ sign nonot at the begginging as far as i can tell https://github.com/Microsoft/referencesource/blob/master/System.ComponentModel.DataAnnotations/DataAnnotations/EmailAddressAttribute.cs)
Thanks, Kevin, just fixed the issue
is working on a reply...