How do the controller names create conflict? If, as an example, I have /app/controllers/orders_controller.php and /app/plugins/pizza/ controllers/orders_controller.php, I can only access one with site.com/ APP/orders/ and the other with site.com/APP/pizza/orders/. Both of them are loaded properly by cakePHP without problems, so why the fear of conflicting class names if they exist in different contexts?
On May 12, 12: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 everyplugin > request would automatically look for a controller with thepluginname > 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 -~----------~----~----~----~------~----~------~--~---
