[QUOTE]I suggest removing all digits checks entirely.[/QUOTE]
I agree with you Jesse in that this would be the overall best way to handle this. Field validation certainly has it’s place, however, when it comes to phone numbers, flexibility in allowing a customer (from whatever country) to enter it the way it is best suited for them is needed.
[QUOTE]My english is bad, I know that but what I meant is that:[/QUOTE]
No, your English is pretty good and you communicate just fine Indy! Actually your English is far better than my foreign lanquage speaking abilities, Irish, or otherwise! Now, go make yourself a “Coma” and see how much better your English lanquage speaking abilities get!
[quote name=‘Struck’]I agree with you Jesse in that this would be the overall best way to handle this. Field validation certainly has it’s place, however, when it comes to phone numbers, flexibility in allowing a customer (from whatever country) to enter it the way it is best suited for them is needed.
No, your English is pretty good and you communicate just fine Indy! Actually your English is far better than my foreign lanquage speaking abilities, Irish, or otherwise! Now, go make yourself a “Coma” and see how much better your English lanquage speaking abilites get![/quote]
I think we need to specify boundaries for the fields. Maybe something like having the capability to either have no restrictions, the default syntax, if that is what you want, or to put in a custom regexp into the each field in the ADMIN, something like what we can do with text box, text field options.
I don’t like the field wide open to anything. I think code could be injected into fields if no restrictions. Also, I believe I may have problems when importing the telephone numbers into Quickbooks and Endicia (which enters phone number for international custom forms) and other programs which may not be able to handle excessive lengths and characters in some fields.
[quote name=‘jobosales’]You can find the phone # validation routines in /js/core.js. You will need to modify the code there:
phone: function(val)
{
var digits = '0123456789';
var valid_chars = '()- +';
var min_digits = 10;
var bracket = 3;
var brchr = val.indexOf('(');
var s = '';
[quote name=‘pbannette’]I think we need to specify boundaries for the fields. Maybe something like having the capability to either have no restrictions, the default syntax, if that is what you want, or to put in a custom regexp into the each field in the ADMIN, something like what we can do with text box, text field options. Business Telephone Systems
I don’t like the field wide open to anything. I think code could be injected into fields if no restrictions. Also, I believe I may have problems when importing the telephone numbers into Quickbooks and Endicia (which enters phone number for international custom forms) and other programs which may not be able to handle excessive lengths and characters in some fields.
Bob[/QUOTE]
Seems like it shouldn’t be a problem to just put very loose limits on teh field. The only problem with not having any kind of validation is that it won’t catch when someone makes a mistake entering their number (maybe 2 fields that get compared? for confirmation?)