On 04/05/2011 10:53, Mark Harris wrote:
Hi Simon,
I need to be able to do some tests and then if the requirements are
not met, disable the module so
that it cannot be used.
I think, then a good solution would be:
Zend_Controller_Front::getInstance()->removeControllerDirectory($module);
That would effectively remove all controllers associated with that
module, thereby allowing you to disable the module :)
That sounds good. Thanks Mark!
From looking at some of the module related methods of
Zend_Controller_Front, I'm wondering if the dispatcher(?) scans *all*
the module directories and does some bootstraping or loading of all
modules regardless of if they are being accessed. Or if it is *only* the
module specified in the route/URL?
--
List: [email protected]
Info: http://framework.zend.com/archives
Unsubscribe: [email protected]
