Thanks for all the replies :).
The posts from the lighthouse ticket describe the exact same situation i
was running into. Thanks for the link and the info to fix it.
For the topic to not be a bug:
Of course duplicate class names in a non namespaced environment are a bad
idea, but in CakePHP ter
thing is - the core team is kinda right for all types of classes.
well, everything except for controllers.
those cannot be used twice in one request of a sane project (assuming
there arent any requestActions)
so the limitation can probably be modified as y2k_2000 suggested (for
controllers) withou
http://cakephp.lighthouseapp.com/projects/42648-cakephp/tickets/1884-appload-no-plugin-mapping
Plugin objects should be placed under the `Plugin` key of the cache
array.
See App::_map() line 775 (cakephp 2.1)
Unfortunately, cakephp team keep saying that it's not a bug...
"duplicated class names..
this is a known limitation of cake2.
I don't like it either. but thats how App::uses() works...
cake3 with namespaces will probably not have issues with this anymore.
but until then you need to name the controllers differently.
On 26 Feb., 16:46, worthy wrote:
> Hi folks,
> take the following e
Hi folks,
take the following example:
x different plugins with a SettingsController and an edit action
-> /pluginone/settings/edit
-> /plugintwo/settings/edit
-> /pluginthree/settings/edit
...
I took a look at the _cake_core_ cache and noticed, that a key for the
first visited SettingsController
