Hi Ralph, On Monday 15 Feb 2010 19:29:04 Ralph Schindler wrote: > 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. >
Now I know what was wrong with my so-called "cache" problem. I have several projects each having its own library folder; My_Tool_Project_Provider was found in that library. Inside project A, I enabled my own project provider. That worked fine until I switched to project B. That required a somewhat different provider, but didn't seem to work. I figured out that having another working directory, the enabled manifest (and so enabled providers) is from the working directory when you enabled the manifest. Can you confirm this or did I mess something up myself? (I know it's not the smartest move to have different providers having the same name for different projects. But it was the easiest way I could tackle a problem). > > 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. Glad I could remind you of it. I'm looking forward to see the updated docs :) > > -ralph > > (BTW, make sure your bin/zf.php is updated as well as the library in 1.10) Good point. Doing that right away! Regards, Jurian
