Comments on: A Better Postal/Zip Code Validation Method for CakePHP 1.2

By: Schaffer Riggs

Schaffer Riggs — Thu, 07 Jan 2010 22:32:23 +0000

I found your blog on technorati and read a couple of of your previous posts. Keep up the good work. I just added up your RSS feed to my Yahoo News Reader. Looking forward to reading more from you down the road!

By: Ken Guest’s Blog: A response to “Better Postal/Zip Code Validation Method for CakePHP 1.2″ | Development Blog With Code Updates : Developercast.com

Thu, 17 Dec 2009 18:20:57 +0000

[...] response to a different post he read on a postal/zip code validation topic, Ken Guest has points out other resources that can be [...]

By: Ken Guest’s Blog: A response to “Better Postal/Zip Code Validation Method for CakePHP 1.2″ | Webs Developer

Thu, 17 Dec 2009 18:01:07 +0000

[...] response to a different post he read on a postal/zip code validation topic, Ken Guest has points out other resources that can be [...]

By: Jamie

Jamie — Thu, 17 Dec 2009 04:38:41 +0000

Thanks for the heads up, Mark – I admit I haven’t had much time to check out 1.3 yet. I was planning to wait until it came out of beta to upgrade, at least on the high traffic production servers we have at work. But I guess that means I don’t have to do a lighthouse ticket now.

By: mark

mark — Thu, 17 Dec 2009 04:23:05 +0000

check out the new cake1.3 branches
there localized validation is already supported by using different classes
they can be stored in app/libs/localized/XY_validation.php
whereas XY would be your country code

By: Jamie

Jamie — Tue, 15 Dec 2009 16:15:31 +0000

Abba – good call on the lighthouse ticket. I just might do that today (if you haven’t already).

By: Jamie

Jamie — Tue, 15 Dec 2009 16:14:58 +0000

Hi Ken – I posted almost the same response on your blog, but I wanted to repeat much of what I said for the benefit of the readers here.

As my post implies, I was addressing a deficiency with the CakePHP framework’s postal validation code. So, my solution is based on the existing Validation::postal() method that comes with CakePHP. While PEAR is a good solution, it was beyond the scope of my article to suggest scrapping Cake’s entire Validation class in favour of another library. I used the existing regular expressions (from the Cake method), which is why 000000 validates as a US postal code. I might suggest it’s beyond the scope of a data format validator to decide whether a postal code is ‘real’ anyway.

By: A response to “Better Postal/Zip Code Validation Method for CakePHP 1.2″ « Ken Guest’s online diary

Tue, 15 Dec 2009 13:59:40 +0000

[...] a few minutes ago I read Jamie Nay’s A Better Postal/Zip Code Validation Method for CakePHP 1.2 blog [...]

By: Ken Guest

Ken Guest — Tue, 15 Dec 2009 13:35:23 +0000

Would it not make more sense, and save you time implementing, debugging and updating your own solution, by utilising PEAR’s Validate class ( http://pear.php.net/package/Validate) and other associated classes such as Validate_UK, Validate_US etc?

Also, you’ve a bug in your code – it allows for US zipcodes that the United Stated Postal Service tool at http://zip4.usps.com/zip4/citytown_zip.jsp does not recognise, such as ’00000′ – unless this weak level of validation is intentional?

By: Abba Bryant

Abba Bryant — Mon, 14 Dec 2009 22:03:55 +0000

Thanks for this, I had solved the same problem ( my company has clients in Canada and the United States and validating either type was a pain) in much the same way. Our code even looks 90% similar, which as I based mine on the original function I guess it should be expected.

Consider opening a ticket in the new cakephp lighthouse to allow for the validation of more than one localized piece of data. Would work for phone, postal codes, etc. Might be a worthwhile addition.