• Resolved virtre

    (@virtre)


    Hi it seems at present the validation of user email input just checks for the @ symbol and at least one alphanumeric after that. So yo@x is accepted as a valid email address and the submission is accepted.

    Some users do get their own email address wrong, pushing up the % of submissions that aren’t completed/confirmed.

    Could a more thorough validation script be used here? Or made an option?

    Could there be an option to add a second email field so user has to enter their email address twice?

    Very happy with the plugin, just seeking to give feedback and seek improvement, thanks.

Viewing 5 replies - 1 through 5 (of 5 total)
  • In installation SpeakOut doesn’t do even this validation – it accepts any input.
    So above mentioned improvement would be appreciated.

    Plugin Author SpeakOut!

    (@123host)

    Thanks for your message.

    If you can find a method of validating emails that includes the hundreds of gTLDs e.g. .golf, .catering etc, I am very happy to implement it.

    Once upon a time it was easy, domains had either a 2 or 3 letter extension. Nowadays chevking extension length is irrelevant.

    User names can have a + or a . in them and who knows what else is permitted.

    The plugin used to vidate emails but people weren’t happy with it. Disabling that seemed like a solution.

    It seems to be impossible to keep everyone happy :o)

    I thought that email confirmation would be a solution, that way addresses must be entered twice and then a confirmation email clicked.

    If you would kindly implement additional option to check against template [email protected], that would do. ??

    Plugin Author SpeakOut!

    (@123host)

    That is _way_ too narrow.

    What if their email is [email protected] e.g. [email protected]? Or [email protected] e.g. [email protected]?

    This is the problem, nowadays there are so many possible combinations of numbers and letters that the only thing to be certain it is an email address is if there is an @ or a . in it.

    Even then, it only shows that the format is valid, not that the email address is, if someone wants to enter something like [email protected] it will pass but be meaningless.

    Please understand that I would love to solve this but I have done a bit of research and couldn’t find the global solution.

    Plugin Author SpeakOut!

    (@123host)

    Nothing else heard about this so I am marking it resolved

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘Enhanced validation of user email address input’ is closed to new replies.