#5647: cache helper should take defined custom routes in consideration
-------------------------------+--------------------------------------------
    Reporter:  edmnc           |         Owner:       
        Type:  Bug             |        Status:  new  
    Priority:  Low             |     Milestone:       
   Component:  Cache           |       Version:       
    Severity:  Minor           |    Resolution:       
    Keywords:  cache           |   Php_version:  PHP 5
Cake_version:  1.2.0.7692 RC3  |  
-------------------------------+--------------------------------------------
Comment (by barduck):

 This also prevents using view caching when creating shortcut routes for
 the default action:

 {{{
 Router::connect('/items/:item/', array('action' => 'view'));
 }}}

 I can't figure out what value to put in $cacheAction to make caching work
 for this route since

 {{{
 var $cacheAction = array(
    'view/' => 3600,
 );
 }}}

 Doesn't work.[[BR]]
 [[BR]]

 The documentation in the cake book is misleading since it says the
 $cacheAction is based on controller's actions and says nothing about the
 entire route path should match.

-- 
Ticket URL: <https://trac.cakephp.org/ticket/5647#comment:1>
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