Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-sales domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the better-click-to-tweet domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-amazon domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-stats domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wordpress-seo domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114
[Feature Request] Sanitize/Standardize Phone Number Inputs | Event Espresso - Staging Server

Support

Home Forums Event Espresso Premium [Feature Request] Sanitize/Standardize Phone Number Inputs

[Feature Request] Sanitize/Standardize Phone Number Inputs

Posted: May 13, 2013 at 10:28 am

Viewing 4 reply threads


Kris Baur

May 13, 2013 at 10:28 am

This would help anyone extending EE working with the phone numbers.


Jonathan Wilson

  • Support Staff

May 13, 2013 at 4:00 pm

Hi Kris,

We appreciate your input. I will add your vote for this feature to our feature request list.

Thanks!


Marko Geisler

May 13, 2013 at 11:01 pm

In Germany, we have this format here:
040 / 219 46 27
or
04131 – 219 46 27

it starts everytime with a “0”, then 2 to 4 numbers follow, then a minus or slash, and then numbers as needed. No brackets in use.

Mobile Numbers use 4 or 5 digits as area code, then minus/slash, then numbers as needed :)


Josh

May 16, 2013 at 9:46 am

Hi Marko,

There’s a jQuery validation plugin you can try adding that uses some regular expressions to validate the German phone number format:

https://github.com/posabsolute/jQuery-Validation-Engine/issues/265


Kris Baur

May 16, 2013 at 11:17 am

Great suggestion for a temporary fix Josh, though a server-side validation will ensure no one messes with the post values.

Viewing 4 reply threads

The support post ‘[Feature Request] Sanitize/Standardize Phone Number Inputs’ is closed to new replies.

Have a question about this support post? Create a new support post in our support forums and include a link to this existing support post so we can help you.

Event Espresso - Staging Server