I agree with Erik. I think this is a major problem when programming a large site with hundreds of tables across many databases.
So to sum up, my options are: 1. create unique models and controller name? 2. some routes + controller magic - (can you explain more on this Tim?) 3. wait for this to be fixed in cake core? Does anyone else have any suggestions? On May 8, 5:05 am, Esoteric <[EMAIL PROTECTED]> wrote: > I don't even see a point to organizing your controllers if the URL > isn't going to change, seems pointless because your controllers can > still conflict. I think the ticket in question almost makes the > "feature" request worse by not changing the URL and allowing the > organization of controllers, but then again I could be > misunderstanding. > > -Erik > > On May 7, 12:22 pm, "Sliv (Tim MacAleese)" <[EMAIL PROTECTED]> wrote: > > > If you look here:https://trac.cakephp.org/ticket/3567 > > > You'll see Gwoo stating that you can organize your code into folders, > > but the URL will not change. > > > I gather this means you may want to try either unique controllers, or > > a combination of routes and method logic in your controllers to handle > > that situation. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
