Pattern validator

svendecabooter,

I too look at regular expressions and see punctuation barf. A Google search on this problem has not revealed an answer. However, the people who dream in regular expressions have assembled a library of patterns you could use to create dozens of specialized validations (e.g. Danish phone number, Austrian postal code, etc.)

Here is a patch that adds this feature.

I chose to use the replacement characters @ and # because this is what the Geonames module gets from the Geonames.org database of international postal code patterns. I had ideas of integrating this with Webform Validation, but it requires a Postal Code field to be dependent on Country field, similar to #917020: Make component(s) required depending on the value of another field

Replaced my ugly PHP version detection hack.

I have re-done this patch as sub-module rather than patching Webform Validation code.

Here is a version of the Pattern sub-module for Drupal 7

Liam,

There is a D6 version (comment #4) that implements this in Webform Validation core. However, I got the impression that svendecabooter intended new validators to be separate modules.

Usually applications just make up their own wildcard languages. The only one I know that is an official standard is Wildmat which is now part of NNTP. Good catch on the Geonames use of the OR operator. I missed that.

Thoughts?

Here is the patch as reqested above.

This version of the patch passes Coder Code Review. I wanted to keep at least the UK Postal Code example in the help text because it is a real world example of the use of the OR operator.

The whitespace removal around the "|" is essential. All validation tests fail without it. Consider "pattern1 \| pattern2". Directly substituting "\|" wtih "|" leaves a space after pattern1 and a space before pattern2. Regex treats these spaces being included in the pattern. The user's form entry will never include them, so validation always fails.

The brackets are my abundance of caution owing to the low order of precedence of the OR operator. It might be possible to omit them, but I didn't feel like risking it.

I guess there is no End of Line character at the end of webform_validation_validators.inc. I'll put in a feature request ;)

It is not possible to submit form data with a leading or trailing space. Webform trims them, even for textarea fields.

Is the EOL a blocker issue to committing this patch?

Right about space trimming. Thanks.

I know this is a day late and a dollar short but further testing on whitespace trimming showed something interesting. Even though form data ends up trimmed in Webform's output, it arrives into Webform Validator un-trimmed. However, I don't think this has any implications for the Pattern validator.

D6 backport patch

This backport has a dependency on
#1122982-6: Words blacklist regex restriction