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) without harming your project
just make sure that there are no collisions in your naming of other
classes (models, helpers, ...), though.
On 26 Feb., 20:05, y2k_2000 <y2k2...@xxxxxxxxx> wrote:
> Plugin objects should be placed under the `Plugin` key of the cache
> See App::_map() line 775 (cakephp 2.1)
> Unfortunately, cakephp team keep saying that it's not a bug...
> "duplicated class names...bla bla"...and more contradictory arguments
> (see App:._loadVendor() line 746)
> So you will have to fix it by your self,
> Just find this line:
> Core/App.php (line ~550)
> self::_map($file, $className);
> and replace for this one:
> self::_map($file, $className, $plugin);
> On 26 feb, 16:46, worthy <frank.fo...@xxxxxxxxxxxxxx> wrote:
> > 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 is stored as only
> > "SettingsController" and not "Pluginxxx.SettingsController".
> > So what happens is: If you visit another plugins settings edit action
> > the request is routed to the cached SettingsController which is from a
> > different plugin.
> > If you disable the _cake_core_ caching the request is routed properly.
Our newest site for the community: CakePHP Video Tutorials
Check out the new CakePHP Questions site http://ask.cakephp.org and help others
with their CakePHP related questions.
To unsubscribe from this group, send email to
[email protected] For more options, visit this group at