Thanks for your input Snook.
Class name conflicts is exactly why I wanted to try for something more
like prefixing. (I think the naming in the pizza example is pretty
sound if only I can hide it when it is time for launch.)
Doing a "normal" route as you suggest works but will quickly become
tiresome when the number of controllers and plugins start to grow.
But I guess what I am looking for is not something that the router can
do (at present at least)? I have not found any documentation or
examples of any general rewriting of names, only the admin and prefix
routing.
I'll go with your suggestion for now and also do a little poking
around in the router to see if I can make sense of it.
Thanks.
/Martin
On May 12, 3:59 pm, "Jonathan Snook" <[EMAIL PROTECTED]> wrote:
> On Mon, May 12, 2008 at 9:31 AM, [EMAIL PROTECTED]
>
> <[EMAIL PROTECTED]> wrote:
> > default plugin routing for index action on PizzaOrders controller in
> > pizza plugin:
> > www.example.com/pizza/pizzaOrders/index
>
> > Small change to:
> > www.example.com/pizza/orders/index
>
> The pizza example is a little confusing because it uses pizza for the
> controller name as well, which isn't necessary. To have the URL
> structure you're looking for, just create a controller named
> OrdersController. It'll automatically pull from the right place.
>
> Alternatively, to help avoid class name conflicts, you can keep your
> original class name and change it like so:
>
> Router::connect('/pizza/orders/*', array('plugin'=>'pizza',
> 'controller' => 'pizza_orders'));
>
> -Jonathan Snook
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"CakePHP" 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
-~----------~----~----~----~------~----~------~--~---
