I have several options to solve this issue:
1) My own library has a My_Controller_Action, extending
Zend_Controller_Action. This controller provides basic functionality used
through the whole application (extending the __call to access action helpers
directly, for example).
2) Inside e.g. a pr
What's the deal with haters hatin' on our old friend the base class? Maybe
you can implement base class functions like getAction using a dispatch level
plugin, but how is that better than a simple abstract class to base your
controllers around? My actual controllers are 80% method free, it's all do
'Twas brillig, and Taha Bayrak at 22/12/09 06:23 did gyre and gimble:
> What is the best practice for placing the base controller classes?
Ideally, don't use them at all. You can use action helpers to group up
common tasks into one handy call...
You can also have plugins work at the dispatch loop
