lightflowmark wrote:
>
> 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.
>
>
Basically it's looking towards having my lib have the core functions and
then the module is created by each application, I was originally thinking
modules would be the core, but in reality it's probably the lib that's the
core. Or I need a way to extend my modules without causing too many
problems.
For instance if I extend the content module I don't want it accessible via
/content or I want /content to access the extend module content2 (or there
abouts!), that could result in a lot of routes!
How do people generally configure base modules to be run independently on
different sites?
Simon
-----
Simon
http://www.ajb007.co.uk/
--
View this message in context:
http://www.nabble.com/Handling-different-view-scripts.-tp22670429p22678501.html
Sent from the Zend Framework mailing list archive at Nabble.com.
