I don't think it's a good idea to to extend Zend_Controller_Action for this purpose. It has specific responsibilities. You shouldn't augment it with functions relating to auth, session, etc. You could put some initialization in it and assign common variables across all you controllers. But still, I recommend you avoid this kind of inheritance if you can, you lose on flexibility.
Jack, you can use class autoloader if you put your custom classes on the include path. Karol Jack Sleight wrote: > > I solve this by creating an ApplicationController which extends > Zend_Controller_Action, and then all my other controllers extend that. > Just make sure to include the file, because ZF wont include it > automatically. > > Dan Rossi wrote: >> Hi there I meant a common class the controllers can extend to reuse >> some functionality, ie getting the registries set in the bootstrap , >> etc. Then it means its only editable in one spot. Maybe via a plugin ? >> >> Karol Grecki wrote: >> >> > > -- > Jack > > -- View this message in context: http://www.nabble.com/project-baseclass-for-all-controllers-tf4203756s16154.html#a11962581 Sent from the Zend Framework mailing list archive at Nabble.com.
