I _think_, if you're going to make this work the way you expect it to,
you should specify the other controllers in routes above the final
routing.
So in your example you'd have:
$Route->connect('/members', array('controller' => 'members'));
Or something along those lines...
On Feb 8, 8:54 am, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>
wrote:
> Hi
>
> I'm new to Cake, but loving it so far. I've been following the "Taking
> advantage of Pages Controller" article on the bakery, but I'm confused
> at the routing suggested there. I want to make the url's simpler by
> removing the /pages/ but the way they suggest seems to break it for
> the controllers. The article suggests putting:
>
> $Route->connect('/*', array('controller' => 'pages', 'action' =>
> 'display'));
>
> at the bottom of your routes.php so that it is a catch all route that
> maps any root level url to a page. My problem is whilst this works
> perfectly for pages, it overrides the controllers e.g: site.com/about
> correctly goes to the About Page, but site.com/members throws up an
> error saying that there isn't a page called members - this is correct,
> it's a controller but it's trying to load it as a page!
>
> I'm sure there must be another line that you need to put into it to
> make it work, but I can't find detailed info on the routes.php syntax
> so I'm a bit stuck! Can any one advise me on this? FYI: I'm using a
> fresh routes.php file from Cake 1.1.13.4450
>
> Ian
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Cake
PHP" group.
To post to this group, send email to cake-php@googlegroups.com
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
-~----------~----~----~----~------~----~------~--~---
