Forums / Setup & design / Sharing settings between "twinned" siteaccesses

"Please Note:

At the specific request of Ibexa we are changing this projects name to "Exponential" or "Exponential (CMS)" effective as of August, 11th 2025.
This project is not associated with the original eZ Publish software or its original developer, eZ Systems or Ibexa".

Sharing settings between "twinned" siteaccesses

Previous topic

Setup & design

Next topic

Author	Message
Luigi Spagnolo	Wednesday 22 July 2009 3:58:43 am A recommended practice for implementing multi-language sites with Exponential is using several public siteaccesses. The problem is that in many cases, multiple multi-language sites must be supported by the same Exponential installation, each one with its own design. This mean that, if I support two languages for each site, I will have a pair of siteaccesses for each site, e.g. in my case: - ita and eng for the main front-end - json_ita and json_eng for creating JSON feeds of nodes - mobile_ita and mobile_eng for a mobile version of the website. Obviously ita and eng share the same design, while json_ita and json_eng share another design, and the same for mobile_ita and mobile_eng. The problem is thay I cannot figure out a way to make those pairs of siteaccesses share the same settings, e.g. the same override.ini, simplifying their maintenance. So, I ask you: is there a way to achieve this,i.e. making siteaccesses that differ only for the language share at least part of the settings?
Heath	Wednesday 22 July 2009 4:16:23 am Hello, Here are some extensions which relate to this topic. http://projects.ez.no/mirror_ini http://projects.ez.no/noveniniupdate Cheers, Heath 7x \| https://se7enx.com/ Brookins Consulting \| https://brookinsconsulting.com/ Certified \| http://web.archive.org/web/201012...th.ez.no/certification/verify/380350 Solutions \| https://projects.exponential.earth/users/community/brookins-consulting eZpedia community documentation project \| http://ezpedia.se7enx.com
Peter Keung	Thursday 23 July 2009 9:39:48 am You could also create "settings" extensions, that contain nothing but settings. Then activate the same extension in whatever siteaccesses you want to share those settings. Of course, be mindful of the order of the loading of INI files: Default Extensions enabled for that siteaccess Siteaccess Extensions enabled globally Override http://www.mugo.ca Mugo Web, eZ Partner in Vancouver, Canada

Author

Message

Luigi Spagnolo

Wednesday 22 July 2009 3:58:43 am

A recommended practice for implementing multi-language sites with Exponential is using several public siteaccesses.
The problem is that in many cases, multiple multi-language sites must be supported by the same Exponential installation, each one with its own design.
This mean that, if I support two languages for each site, I will have a pair of siteaccesses for each site, e.g. in my case:
- ita and eng for the main front-end
- json_ita and json_eng for creating JSON feeds of nodes
- mobile_ita and mobile_eng for a mobile version of the website.

Obviously ita and eng share the same design, while json_ita and json_eng share another design, and the same for mobile_ita and mobile_eng.
The problem is thay I cannot figure out a way to make those pairs of siteaccesses share the same settings, e.g. the same override.ini, simplifying their maintenance.

So, I ask you: is there a way to achieve this,i.e. making siteaccesses that differ only for the language share at least part of the settings?

Heath

Wednesday 22 July 2009 4:16:23 am

Hello,

Here are some extensions which relate to this topic.

http://projects.ez.no/mirror_ini
http://projects.ez.no/noveniniupdate

Cheers,
Heath

7x | https://se7enx.com/
Brookins Consulting | https://brookinsconsulting.com/
Certified | http://web.archive.org/web/201012...th.ez.no/certification/verify/380350
Solutions | https://projects.exponential.earth/users/community/brookins-consulting
eZpedia community documentation project | http://ezpedia.se7enx.com

Peter Keung

Thursday 23 July 2009 9:39:48 am

You could also create "settings" extensions, that contain nothing but settings. Then activate the same extension in whatever siteaccesses you want to share those settings. Of course, be mindful of the order of the loading of INI files:

Default
Extensions enabled for that siteaccess
Siteaccess
Extensions enabled globally
Override

http://www.mugo.ca
Mugo Web, eZ Partner in Vancouver, Canada