Sub-classing Yaf_Controller_Abstract about yaf

[laruence]

sorry, I am not sure what are you meaning here, can you give me a test script about that?

[SpiderMatt3825U]

Sure, it's real simple. Take the following two custom controller classes for example:

class SharedController extends Yaf_Controller_Abstract {}
class ContactController extends SharedController {}

So when I have a route that points to the "ContactController" I receive the following error message:

Controller must be an instance of Yaf_Controller_Abstract

My goal is quite simple and is perfectly inline with the long running fundamentals of OOP and more specifically abstraction. I am simply trying to create a shared custom controller for all my site's controllers to extend so that some functionality common to every request may be only written one time. Also, to save time, this is not a scenario where the use of an external action class would make sense nor solve the problem.

[laruence]

It should work, could you please verify that no auto-loading fails ?

[SpiderMatt3825U]

I already confirmed that the auto-loading is working as the middle class (the one containing the abstracted custom functionality) resides in the same location as the child class. I have tested this in the most basic of examples and still suffered the failure. Unfortunately, due to the overwhelming lack of documentation I have had to discard my current efforts in implementing the Yaf framework in my current project. I really hope it catches up relatively soon as I love the performance benchmarks of this framework but I am finding myself making far too many sacrifices compared to my normal framework environment.

[laruence]

what's your yaf version?
I confirmed this works well .

not sure what's wrong there, maybe you can send me your own demo?

thanks