Hey Jurian,

There were many issues for people when Zend_Tool used a scanning approach to finding providers. For background it worked like this: Zend_Tool would scan every file in the include_path and check to see if it matched the *Manifest.php or *Provider.php pattern.

This caused many issues on all different platforms. Now we've opted to go the specify your providers approach. For this, simply run the command

zf --info

and

zf --setup

commands. Then, to make your providers work as they have done before, you can add them to the zf.ini file that is created during setup. For example, if you have MyNamespace_MyProvider provider, you'd add this to the zf.ini

basicload.classes[] = "MyNamespace_MyProvider"

This will then make itself known to the Zend_Tool framework and you will be able to dispatch them.

series (from 1.9.7 to 1.10.1). It seems there are several BC breaks, but none of them are listed in the changelog (1.10.0 nor 1.10.1).

You are correct, I apologize for that, I will have an updated changelog this week as I have already completed this documentation locally. It got lost in the shuffle of changes I had made.

Thanks for the heads up, and let me know if that helps you get your providers working again.

-ralph

(BTW, make sure your bin/zf.php is updated as well as the library in 1.10)

Reply via email to