Kind of "public_override" and "admin_override"

Next topic

Author	Message
Nicolas Steinmetz	Tuesday 07 September 2010 1:18:26 am For the context : In one single instance of eZ Publish (in fact there are four for technical, legal and timezone reasons), we host around 25 town websites (with 1 main siteaccess + 1 admin + 0 to n for translations if any). So far, settings are versionned in SVN and I have 3 structures (one for each environement : UAT / Preprod / Prod). So nothing new here I guess for most of you :-) My issue is that, for each new release, I have to update settings for each town. I use the /settings/override/* sometimes but I can't use it always as we may have some conflicts between frontend/backend siteaccess. So I was thinking about a kind of "public_override" and "admin_override". What do you think about ?
Matthieu Sévère	Tuesday 07 September 2010 1:36:45 am This kind of override would be very nice, there is discussion on this on the issue tracker but I can't find back the issue, if someone remenber... Currently for this problem I use the ActiveAccessExtension settings which allows you to load an extension for a specific site access. Thus, I can load one extension for front end siteaccess and another one for backend extension and I put my override and front end settings there. Cheers -- eZ certified developer: http://ez.no/certification/verify/346216
Nicolas Steinmetz	Tuesday 07 September 2010 1:51:37 am Thanks Matthieu for your reply, If I understand well, for a given town : On my main public siteaccess : I load the generic "frontend" extension which contains generic settings In my siteaccess, I can override the generic settings from my "frontend" extension On my secondary siteaccess (for translation purpose) : I load the generic "frontend" extension which contains generic settings In my siteaccess, I can override the generic settings from my "frontend" extension On my admin siteaccess : I load the generic "backend" extension which contains generic settings In my siteaccess, I can override the generic settings from my "backend" extension So if I undertand well, it leads to something like settings/override/* > settings/siteaccess/<town>/* > extension/<my extension>/settings/* ? It reminds me that sometimes there were troubles with settings within extensions. Is it now safe/solved (we use 4.0.6 so far, should use 4.3 by the end of the year).
Matthieu Sévère	Tuesday 07 September 2010 2:07:32 am Yes, but be carefull with loading order and override of ini file you should have a look at this issue : http://issues.ez.no/13382 -- eZ certified developer: http://ez.no/certification/verify/346216
André R.	Tuesday 07 September 2010 3:03:13 am With ActiveAccessExtension this should work in all versions, it's been cleanedup slightly in 4.4 but the basics are the same, the order is: settings/ ActiveAccessExtension siteaccess ActiveExtension settings/override/ eZ Online Editor 5: http://projects.ez.no/ezoe \|\| eZJSCore (Ajax): http://projects.ez.no/ezjscore \|\| eZ Publish EE http://ez.no/eZPublish/eZ-Publish-Enterprise-Subscription @: http://twitter.com/andrerom
Matthieu Sévère	Tuesday 07 September 2010 4:26:33 am " With ActiveAccessExtension this should work in all versions, it's been cleanedup slightly in 4.4 but the basics are the same, the order is: settings/ ActiveAccessExtension siteaccess ActiveExtension settings/override/ " By the way, what has been done in 4.4 around ini : use of eZ Components for ini management ? Is there any plan to change loading order in futur release ? Thanks for your heads up André -- eZ certified developer: http://ez.no/certification/verify/346216
Nicolas Steinmetz	Wednesday 08 September 2010 1:40:01 am Solved on a theorical point of view - Let's now see how to implement it for real in my context.
Jean Voye	Wednesday 08 September 2010 1:44:34 am " Solved on a theorical point of view - Let's now see how to implement it for real in my context. " Let us know how this goes Nicolas. Cheers ! -- Nicolas