On 5/10/07, Mariano Iglesias <[EMAIL PROTECTED]> wrote: > > From http://manual.cakephp.org/chapter/plugins: > > "While it isn't required, it is recommended that you name your plugin > controllers something relatively unique in order to avoid namespace > conflicts with parent applications. Its not a stretch to think that a parent > application might have a UsersController, OrderController, or > ProductController: so you might want to be creative with controller names, > or prepend the name of the plugin to the classname"
Ugh! wonder how I missed it... But again IMO the framework should handle this gracefully. Prepending or appending classname is not an answer as it will lead to ugly/confusing/funny URLs or the developers will have to use routes which is not so bad BUT for apps where plugins are supposed to be plug and play expecting end users to edit routes is not an acceptable option. Hmmm... DB based routing anyone? Just my 2ps Tarique -- ============================================================= PHP for E-Biz: http://sanisoft.com Cheesecake-Photoblog needs you!: http://cheesecake-photoblog.org ============================================================= --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
