Hi, I am trying to migrate a legacy application to ZF and got stuck in one point. The current application is used by different users and for each user basically we have a copy of all php/tpl files to a separate directory, edit a config file with the user ID and start to customize the tpl (most of the time just the CSS). The database is the same with a UserID column to separate the records.
Sometimes we have an user with special needs so this or that php is tweaked, a separate table id created and so on. So what I'd like to achieve with the ZF migration is to be able to avoid this copy process for all except those that need special features. I was considering creating a default module where I could add 'submodules' (such as registration, recommend this page to a friend, product, survey etc) and create a different module whenever I'd have a special user. /default/product /default/registration /SpecialUserA/product In this example when someone tries to access the product submodule of the special user A it will be handled by the proper controller and not the default one. www.mydomain.com/foo/product (default product) www.mydomain.com/bar/product (bar's version of product since bar is a special user) www.mydomain.com/bar/registration (get the default version since there is no special version of registration in bar's module) I was wondering if a) is this the better way to avoid the duplication I mentioned ? b) the strategy I am defining for ZF (the module/submodule) is adequate c) how can I do this with the routing defined in ZF's MVC thanks.
