On Jan 14, 2008 4:22 PM, b logica <[EMAIL PROTECTED]> wrote: > > Here's one: > > http://bakery.cakephp.org/articles/view/taking-advantage-of-the-pages-controller > > -- snip -- > Route placement > Just for reference, you should place the /* route LAST in your routes file > or it will override all of the other routes. posted Sun, Oct 22nd 2006, > 18:44 by Luke Sheridan > -- snip --
Hrm, I hadn't seen that before. Thanks for pointing it out. I know that some other frameworks do that sort of thing, where URL's filter down through a chain of custom routes. > Should I be using a "/*" route? Do I need to specify "/about/*" goes to > pages? If so, is there some way that I can keep those views nested like > this: > > views > pages > about > something > something deeper > > With the structure like this, if I try a route like "/about/*" I run into > problems because Cake no longer sees the view inside the about dir. I have a > lot of static pages and I'd really like to be able to keep them organised, > rather than dumping everything in the /app/views/pages/ dir. Hrm...sounds like you will need a lot of custom routes to make it happen, but that's because I've never done what you're trying to do (with respect to having a huge collection of static pages). -- Chris Hartjes Internet Loudmouth Motto for 2008: "Moving from herding elephants to handling snakes..." @TheKeyBoard: http://www.littlehart.net/atthekeyboard --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Cake PHP" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~----------~----~----~----~------~----~------~--~---
