On Feb 25, 2:22 am, AD7six wrote:
> On Feb 25, 7:36 am, adam wrote:
>
> > That's a shame, that makes a user plugin (half) pointless since you
> > would still have to have the beforeFilter code outside the plugin
>
> Or entirely useful, since the code you're talking about would be in a
> componen
On Feb 25, 7:36 am, adam wrote:
> That's a shame, that makes a user plugin (half) pointless since you
> would still have to have the beforeFilter code outside the plugin
Or entirely useful, since the code you're talking about would be in a
component, not the plugin app controller. Why would yo
That's a shame, that makes a user plugin (half) pointless since you
would still have to have the beforeFilter code outside the plugin
On Feb 24, 9:45 am, majna wrote:
> To call AppController beforeFilter
> form
> PluginAppController:
>
> plugin_name_app_controller:
> function beforeFilter(){
>
To call AppController beforeFilter
form
PluginAppController:
plugin_name_app_controller:
function beforeFilter(){
parent::beforeFilter();
}
On Feb 24, 8:48 am, Adam Royle wrote:
> Due to the way plugin controllers work with inheritance, you can only
> access the plugin's beforeFilter logic
Due to the way plugin controllers work with inheritance, you can only
access the plugin's beforeFilter logic when the page is requested
through the plugin (ie. /plugin/controller/action/)
From what I can tell you want to execute plugin logic from your base app?
The proper way to do this is by
How do I call the app_controller beforeFilter logic from a plugin?
Such as plugin_name/plugin_name_app_controller from the app/
app_controller.php?
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"CakePHP" group.
To p
