-- RustedBucket <[email protected]> wrote (on Wednesday, 10 August 2011, 09:20 AM -0700): > Nope didn't work but I have narrowed it a bit to the actual plugin loader.. > roughly line 117 in /Zend/Application/Resource/FrontController.php > > $plugin = new $pluginClass(); > > This is where it fails.
Is the plugin within a module? If so, you've got a precedence issue -- basically, the module-specific autoloader hasn't been created yet, which means you can't instantiate a resource within it. If this is the case, the solution is to add an _init*() method in your application bootstrap in order to setup specific autoloaders early. _init*() methods are run before resource plugins, *unless* a call to bootstrap($someResourcePlugin) is made. So, if you make such a method the first in your bootstrap, the autoloading should be in place for when the front controller attempts to instantiate its plugins. -- Matthew Weier O'Phinney Project Lead | [email protected] Zend Framework | http://framework.zend.com/ PGP key: http://framework.zend.com/zf-matthew-pgp-key.asc -- List: [email protected] Info: http://framework.zend.com/archives Unsubscribe: [email protected]
