So sorry for the ultra-delayed response. It's been a crazy week(end)
relocating...
Just now getting some time to catch up on all 40K eMails :P
That means instead of adding the autoloader in my Bootstrap.php (extends
Zend_Application_Bootstrap_Bootstrap) I simply add a Bootstrap.php (extends
Zend_Application_Module_Bootstrap) in each module, right?
Yes. It would also be a good idea to make sure you have
`resources.modules[]=null` somewhere in your application.ini as well :)
This also seems to be the reason for the error message I posted:
'Invalid controller specified (content).
Can you correct my code this purpose?
I'd need to see things in a bit more context before providing suggestions.
For example, what's the directory structure of your modules?
Are you sure you have a controller and view available for use by
Zend_Controller_Front.
Are you sure you're routing to `content1' and not `content' ?
I thought about then moving the correct code into each module bootstrap
class.
But since ZF handles every bootstrap in a row the first module bootstrap
would overwrite the follwing ones, right? Again a good point to chose the
plugin?
I might agree with your first gut and suggest against this since each module's
bootstrap can have conflicting agendas.
However, a plugin is executed later than the bootstrap. By the time you get to
the preDispatch(), you've already got your routes in place and they've been
executed to decide the path of your application.
It would be better to use application/Bootstrap.php because you can modify
routes before they are evaluated, thus allowing you to determine the path of
your application early on in the process.
Hope this helps a bit,
-Kizano
//-----
Information Security
eMail: [email protected]
http://www.markizano.net/
--
List: [email protected]
Info: http://framework.zend.com/archives
Unsubscribe: [email protected]
