Ok, So it's basically treating /home the same as /? So I need to NOT use the global Cache.check and setup the caching in each controller as I have done before?
Does this mean that I will have to copy the pages class from the core to control the pages caching? d//t. On Feb 22, 3:39 pm, John Andersen <j.andersen...@gmail.com> wrote: > The Dispatcher class has a method in which it checks for whether or > not it should use a cached version of the URL, when the Cache.check > configuration is set to true. > > So in your case it works as it should, you have told the Dispatcher to > use cached versions. The Dispatcher uses "/home" whenever the "/" is > specified. > > Enjoy, > John > > On 22 Feb., 15:22, "designv...@gmail.com" <designv...@gmail.com> > wrote:> I have used caching before on controllers I have created and it's not > > been a problem, and it works fine for the controllers in this site. > > > I am familiar with setting the cache configuration options and > > creating new ones in the core. > > > I am just stumped over this issue regarding caching pages and the '/' > > route... I do not know where to set options for it. > > > Cheers, > > > d//t > > [snip] -- Our newest site for the community: CakePHP Video Tutorials http://tv.cakephp.org Check out the new CakePHP Questions site http://ask.cakephp.org and help others with their CakePHP related questions. To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php
