#5737: Router::connect issues with underscores in the regex
------------------------------------------+---------------------------------
    Reporter:  jne                        |          Type:  Bug               
      Status:  new                        |      Priority:  Medium            
   Milestone:  1.2.x.x                    |     Component:  Routing/Dispatcher
     Version:  RC3                        |      Severity:  Major             
    Keywords:  Router, underscore, regex  |   Php_version:  PHP 5             
Cake_version:  RC3                        |  
------------------------------------------+---------------------------------
 Using a specially crafted routing scheme with underscores in it, make the
 parsing of fields erratic.

 I am trying to use this
 Router::connect('/download_:slug_:id.html', array('controller' =>
 'movies', 'action' => 'view'), array('pass' => array('id'), 'id' =>
 '[0-9]+'));

 with a URL like /download_blabla_1234.html only the last digit is passed
 (ie : 4 in the example)

 Using - instead of _ in both URL and Routeur::connect does not suffer the
 same issue (in this case id is passed and equals 1234)

-- 
Ticket URL: <https://trac.cakephp.org/ticket/5737>
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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/tickets-cakephp?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to