ZF-7158: No automatic creation of Zend_Application_Module_Autoloader for default module

Issue Type: Bug Created: 2009-06-29T20:34:00.000+0000 Last Updated: 2009-08-21T12:53:21.000+0000 Status: Resolved Fix version(s): - 1.9.2 (25/Aug/09)

Reporter: Phil Brown (philbrown) Assignee: Matthew Weier O'Phinney (matthew) Tags: - Zend_Application

Related issues: - ZF-6803



From the documentation {quote} When using module bootstraps with Zend_Application, an instance of Zend_Application_Module_Autoloader will be created by default for each discrete module, allowing you to autoload module resources. {quote}

Is there any reason this doesn't apply to the "default" module?

Either the documentation needs to be updated to exclude the default module or the default module autoloader should be automatically created.

On a related note, is it standard fare to prefix default module models / forms / acls / etc class names with "Default_"? The documentation seems lacking with respect to the default module and its resources.


Posted by Matthew Weier O'Phinney (matthew) on 2009-08-21T12:53:12.000+0000

ZF-6803 resolves this issue.

If you define your default module bootstrap using Zend_Application_Module_Bootstrap, and place it in a directory named 'default', then yes, you should prefix your various module resources with the verbiage 'Default_'. In most cases, and all examples in the ZF manual, the default module is also the home of the application bootstrap, and as such, this is something you need to define for yourself (i.e., whether you want your default module resources prefixed, and if so, with what prefix).

Have you found an issue?

See the Overview section for more details.


© 2006-2018 by Zend, a Rogue Wave Company. Made with by awesome contributors.

This website is built using zend-expressive and it runs on PHP 7.