I would think it depends on how much customisation you want to do. If it really is just the views you need to change, setting the view path seems like a viable solution.
If you want to do something more complex, maybe alter some actions, then having your site controllers inherit from a generic content controller would be the way forward? my_generic_controller extends Zend_Controller_Action my_site1_controller extends my_generic_controller. Simon Corless wrote: > > I am interested in peoples thoughts on how to best achieve the following. > > I have a generic content module, I don't want to change this directly in > the sites I create, however I want the views to be different (more than > just CSS changes). I have so far decided to setup another view directory > in my skin (a Zend_Layout implementation) so the view paths would be: > > skin/views/scripts/content/index > module/views/scripts/content/index > > So if there's a custom template it finds it, is this good pactice or is > there a better way? I feel you shouldn't have too many vie paths/ Is it > checking if the file exists every time? Should I just specify the template > directory and force it to render from there? > > Thanks > Simon > -- View this message in context: http://www.nabble.com/Handling-different-view-scripts.-tp22670429p22677246.html Sent from the Zend Framework mailing list archive at Nabble.com.
