I agree. It would be a sweet feature.
With the default routes in place:
example.com/pizza/orders/
This url will already fall back on different actions to try to run. I
have this understanding:
1. look for a controller named pizza
2. look for a plugin named pizza and a controller named orders
3. look for a plugin named pizza and a controller named pizza and an
action named orders
This would be implemented as an optional 2.5 in the above list,
looking for a controller called {plugin}{Controller}.
I havent untangled the dispatcher in my head so I am not sure in
detail how Cake is doing this. Looks like "_restructureParams()" on
line 474 is called when Cake can't find a controller. I think that is
where one would need to add some code. I will give this a few more
hours and possible adding an enhancement ticket for it... I would just
like to have some code to go along with it :)
/Martin
On May 12, 6:05 pm, "Jonathan Snook" <[EMAIL PROTECTED]> wrote:
> > 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.
>
> Oh, were you hoping for something automatic such that every plugin
> request would automatically look for a controller with the plugin name
> attached? (in obvious hopes to avoid class name clashes.) That's an
> interesting thought and maybe one that should be presented to the core
> devs to consider (if it isn't already in the core, which I don't think
> it is).
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"CakePHP" 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
-~----------~----~----~----~------~----~------~--~---
