Thanks Matthew, that pretty much what I'd surmised after taking the time to
look at the code code. I decided it was mostly a pathing thing that was
missing much like the controller directory function. Since this also seems
to affect module specific models for me as well what I did was set a
namespace and basepath in my bootstrap. I can then either get the front
controller instance and register the plugin or add the
resources.frontController.plugins[] = 'Authentication_Plugin_Acl' back in
the application.ini file and it works either way.
in /application/Bootstrap.php
protected function _initAutoload()
{
new Zend_Application_Module_Autoloader(array(
'namespace' => 'Authentication',
'basePath' => APPLICATION_PATH . '/modules/authentication',
));
}
I guess the question now is, is this a reasonable approach until such a time
as the autoloader can do this itself? If I were to add another namespace and
basepath for a plugin in another module will it understand these are
separate? I'm assuming all the above is really doing is expanding the
available search paths anyway. Thanks a bunch.
--
View this message in context:
http://zend-framework-community.634137.n4.nabble.com/Autoloading-models-plugins-via-ini-tp3731707p3733778.html
Sent from the Zend Framework mailing list archive at Nabble.com.
--
List: [email protected]
Info: http://framework.zend.com/archives
Unsubscribe: [email protected]
