Re: [fw-general] registering plugins per module/controller

2007-08-06 Thread Matthew Weier O'Phinney
-- Hoopes [EMAIL PROTECTED] wrote (on Saturday, 04 August 2007, 03:59 PM -0400): I'm looking for a way to register plugins for the front controller based on what module (or controller) i'm being routed to. Basically, i'd like a subset of controllers throughout my app to all have certain data

Re: [fw-general] registering plugins per module/controller

2007-08-05 Thread Ian Warner
Hi I use the config file, place this config array in config.ini.php or whatever you use, call it DEFAULT [default] plugins.Auth= true plugins.Translation = true Then for each project, controller or whatever delimiter you use, ie for admin you can dedide to remove a plugin, ie below

Re: [fw-general] registering plugins per module/controller

2007-08-05 Thread Hoopes
ian, that's a cool idea, but i guess my question is, how do i tell what module/controller/action i'm working with when i'm in the bootstrap index.php file? what does the colon in the config section header do? I couldn't find anything about it in the parse_ini_file php.net page. thanks for the

Re: [fw-general] registering plugins per module/controller

2007-08-05 Thread Stefan Pettersson
2007/8/5, Hoopes [EMAIL PROTECTED]: that's a cool idea, but i guess my question is, how do i tell what module/controller/action i'm working with when i'm in the bootstrap index.php file? You could always use the request object: Zend_Controller_Front::getInstance()-getRequest()-getParams()

[fw-general] registering plugins per module/controller

2007-08-04 Thread Hoopes
Hey, I'm looking for a way to register plugins for the front controller based on what module (or controller) i'm being routed to. Basically, i'd like a subset of controllers throughout my app to all have certain data before they get started, without having to put the logic in preDispatch of