#6312: Validators should fall back to non UTF-8 regex modifiers if PCRE doesn't
have support compiled in.
---------------------------+------------------------------------------------
    Reporter:  KarlHungus  |          Type:  Enhancement
      Status:  new         |      Priority:  Medium     
   Milestone:  1.2.x.x     |     Component:  General    
     Version:  1.2 Final   |      Severity:  Normal     
    Keywords:              |   Php_version:  n/a        
Cake_version:              |  
---------------------------+------------------------------------------------
 Several production operating systems (Centos and RHEL for sure) do not
 ship PCRE with unicode properties support. This causes a number of
 validators to fail with the following warning:

 Warning (2): preg_match() [function.preg-match]: Compilation failed:
 support for \P, \p, and \X has not been compiled at offset 14
 [CORE/cake/libs/validation.php, line 847]

 It would be nice if there was a fallback set of validators that did not
 require unicode property support. This could be detected in bootstrap, or
 more ideally in a configuration option.

-- 
Ticket URL: <https://trac.cakephp.org/ticket/6312>
CakePHP : The Rapid Development Framework for PHP <https://trac.cakephp.org/>
Cake is a rapid development framework for PHP which uses commonly known design 
patterns like ActiveRecord, Association Data Mapping, Front Controller and MVC. 
Our primary goal is to provide a structured framework that enables PHP users at 
all levels to rapidly develop robust web applications, without any loss to 
flexibility.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"tickets cakephp" group.
To post to this group, send email to tickets-cakephp@googlegroups.com
To unsubscribe from this group, send email to 
tickets-cakephp+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/tickets-cakephp?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to