> 3. wait for this to be fixed in cake core?
I don't think that will happen unless:
1) It doesn't break something the Core Devs are concerned about (like
backwards compatibility or something)
2) A ticket was opened with a test case, a patch and a good argument
This is just my speculation, of co
I guess I was thinking along the lines of pointing both routes to the
same controller then using passed params in shared methods:
Route::connect('/db1/users/*' => array('controller' =>
'controllerForBoth'));
function myControllerMethod() {
if($this->params['url']['url'] ==
> 2. some routes
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
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 t
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
t
Hey bakers,
I am building an application that has 6 databases. Some of the tables
are called the same name. I have organized my controllers/views into
sub directorys for each database.
eg.
controllers/
db1/
users_controller.php
db2/
users_controller.php
The Problem:
