Zend Framework

loader warnings when using class resource for a specific module

Details

  • Type: Bug Bug
  • Status: Resolved Resolved
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 1.8.4, 1.9.0
  • Fix Version/s: 1.9.1
  • Component/s: Zend_Application
  • Labels:
    None

Description

I use main autoloader with enabled warnings and fallback autoloader. I also use modules bootstrap with Zend_Application_Resource_Modules.
When I try to define routes for my module via module prefix as it's desribed in the manual e.g.

blog.resources.router.routes.blogIndex.route = blog
blog.resources.router.routes.blogIndex.defaults.module = blog
blog.resources.router.routes.blogIndex.defaults.controller = index
blog.resources.router.routes.blogIndex.defaults.action = index
blog.resources.router.routes.blogIndex.type = Zend_Controller_Router_Route_Static

I get these warnings

Warning: include(router.php) [function.include]: failed to open stream: No such file or directory in blabla/zendframework/library/Zend/Loader.php on line 83

Warning: include() [function.include]: Failed opening 'router.php' for inclusion (include_path='blalba;....') in blabla/zendframework/library/Zend/Loader.php on line 83

Maybe cause is same as in ZF-6658

if (class_exists($plugin))

in Zend_Application_Bootstrap_BootstrapAbstract::getPluginResource()

Issue Links

Activity

Hide
Miroslav Kubelik added a comment -

There is a patch, it solves also ZF-6658 and ZF-6672 I think, please consider to apply this one.

Show
Miroslav Kubelik added a comment - There is a patch, it solves also ZF-6658 and ZF-6672 I think, please consider to apply this one.
Hide
Miroslav Kubelik added a comment -

still presented in 1.9.0

Show
Miroslav Kubelik added a comment - still presented in 1.9.0
Hide
Matthew Weier O'Phinney added a comment -

Patch applied to trunk and 1.9 release branch.

Show
Matthew Weier O'Phinney added a comment - Patch applied to trunk and 1.9 release branch.

People

Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved: