Package home | Report new bug | New search | Development Roadmap Status: Open | Feedback | All | Closed Since Version 0.5.4

Bug #9242 Error in telephone checking
Submitted: 2006-11-06 11:25 UTC
From: webmaster at webit dot co dot uk Assigned: arpad
Status: Closed Package: Validate_UK (version 0.5.2)
PHP Version: Irrelevant OS:
Roadmaps: (Not assigned)    
Subscription  
Comments Add Comment Add patch


Anyone can comment on a bug. Have a simpler test case? Does it work for you on a different platform? Let us know! Just going to say 'Me too!'? Don't clutter the database with that please !
Your email address:
MUST BE VALID
Solve the problem : 36 + 13 = ?

 
 [2006-11-06 11:25 UTC] webmaster at webit dot co dot uk (James Nunnerley)
Description: ------------ I've noticed an error in the checking of the UK telephone numbers. In the error check, it does indeed go through and check that numbers should be 11 characters long, however outside of London, 10 character numbers are still allowed. One example being 01905 22222 - which is actually an estate agents! Test script: --------------- n/a Expected result: ---------------- 10 character numbers, that don't start 02 should be accepted. Actual result: -------------- They fail.

Comments

 [2007-02-23 14:34 UTC] ash at hexmen dot com (Ash Searle)
Ofcom dictates the UK numbering scheme, and provides downloadable files detailing precisely which area codes contain 10-digit numbers. http://www.ofcom.org.uk/telecoms/ioi/numbers/numbers_administered/ A 'good enough' fix should be to accept 10-digits for numbers beginning '01' and '08'. All other numbers should be 11-digits. Note: at the present-time (Feb 2007) UK numbers cannot begin '04' or '06' A patch to fix this bug is available here: http://hexmen.com/code/patches/pear-9242.diff
 [2007-04-21 13:17 UTC] arpad (Arpad Ray)
This bug has been fixed in CVS. If this was a documentation problem, the fix will appear on pear.php.net by the end of next Sunday (CET). If this was a problem with the pear.php.net website, the change should be live shortly. Otherwise, the fix will appear in the package's next release. Thank you for the report and for helping us make PEAR better.