Re: Potential bug with _cake_core_ caching

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 <frank.fo...@googlemail.com> 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 http://tv.cakephp.org
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
cake-php+unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php