Description

I'm following the manual for creating a custom Zend_Tool_Framework provider [1] in Zend Framework 1.10 (tested both beta1 and rc1)
My custom provider is never found although my provider and manifest are in the include_path.

This seems to be because Zend_Tool_Framework_Client_Console is now forcing the use of the BasicLoader in
Zend_Tool_Framework_Registry.
Previous zf version (I checked both 1.9.7 and 1.9.6) defaulted to the IncludePathLoader.

The documentation however does not mention this and still talks about the IncludePathLoader

Posted by Guillermo Thiemann (guille) on 2010-03-11T02:23:04.000+0000

I would say that the environment-level configuration .zf.ini is a bad location to put custom providers anyway.

What if I have project-specific Providers and more than one Project running in one server?

Posted by James Stuart (jstuart) on 2010-03-23T12:54:02.000+0000

I agree. Causing Zend Tool extensions to be loaded globally (per user) significantly diminishes their usefulness for project based tasks.

We have many developers, each with multiple workstations, working on many projects. Having your configuration based on the user account (and workstation) that you're using and not the application that you're working on is a hurdle that will prevent us from using Zend Tool at all.

On the server side, our hosting setup causes us to have many applications on the same server running as the same user. We obviously cannot use the same configuration for each application, so the environment-level configuration doesn't work here either.

Posted by Ralph Schindler (ralph) on 2010-10-21T08:14:27.000+0000

Fixed in r23201 in trunk & r23202 in release branch 1.11 (as part of ZF-9397)