I haven't had any issues with configuration so far and I don't think there are any that won't allow you to do what you're planning to.
In case you want to have per route configuration then you would need to extend/replace Zend\Mvc\RouteListener and provide your own logic for handling route and other configurations. The functionality provided by Evan to be able to use different layout per module has been implemented to ease that specific requirement only. If you know how to configure your routes then there won't be any problems with overriding them by different modules. You just need to use different names or group them using different types of routes provided. If you need to change so many things between your frontend and backend modules then maybe you should consider them rather as two separate applications rather than modules. Not sure what are your specific requirements though. To help you with understanding more about modules separation in a practical way you may want to read this post written by Matthew: http://mwop.net/blog/267-Getting-started-writing-ZF2-modules.html http://mwop.net/blog/267-Getting-started-writing-ZF2-modules.html You need to start thinking more granular in terms of modules. Frontend and Backend do not sound like a good example of modules. In my opinion they are more like 2 separate applications tha can share the same modules. For ie. they may have common User, Content or Pages modules. If you need more specific help please ask. ghola wrote > > I've been toying with ZF2 lately and hit some configuration issues. > ghola wrote > > Looking into the code a little deeper it started to make sense: module > configs are used for bootstrapping, and there is no correlation between > the module bootstrapping and route bootstrapping (because what i actually > want is per route configuration). > ghola wrote > > So one could define a whole new config namespaced under the module name, > but applying this config requires code which has most likely already been > written to apply the main merged config (on the boostrap event). So how > about a feature to support this module namespacing to config, in order to > avoid having your module config overwritten by another module. > > Now i also have the feeling that i got this whole thing wrong. That the > modules in ZF2 are completely different in intent and usage from the ones > in ZF1 and my mind just didn't adjust yet to the new approach, and is > trying to apply old techniques to the new framework. If this is the case, > please make an attempt at explaining the correct way of thinking and > implementing a basic website with a frontend and a backend, each having > one single route (so /controller/action for frontend and > /backend/controller/action for backend) with a different config for each > route (different in default tempaltes, layout, doctypes ... pretty much > different in everything view related). > ----- Cheers, -- Luke Mierzwa -- View this message in context: http://zend-framework-community.634137.n4.nabble.com/ZF2-per-route-or-module-configuration-tp4656844p4656879.html Sent from the Zend Framework mailing list archive at Nabble.com. -- List: [email protected] Info: http://framework.zend.com/archives Unsubscribe: [email protected]
