Settings override order

Next topic

Author	Message
Bertrand Dunogier	Wednesday 13 July 2005 2:40:06 am I'm setting up a multilingual site with ezp, and either I don't understand something, either something doesn't make sense. The current settings override order: - settings/x.ini - settings/siteaccess/y/x.ini.append - settings/override/x.ini.append doesn't sound logical to me. Initially, I thought it would have been global => global override => siteaccess. That way for instance, you can setup all the common stuff in global overrides, then finetunes for each siteaccess in the respective ini files. In my multilanguage website example, I could have done: override/site.ini.append: [SiteSettings] LoginPage=embedded then in siteaccess/foo/site.ini.append [SiteSettings] SiteName=... SiteURL=... And so on. Now I have to totally replicate the siteaccess folder and edit all files everytime. I'm not even sure how i'm gonna handle my overrides, actually :) <b>suggestion:</b> I was thinking about an additionnal setting like AdditionnalSiteSettingsList which would let you specify an override folder where settings would be loaded for that siteaccess. Thoughts ? And maybe suggestions if I'm doing something wrong... :) Thanks !
David Eriksson	Wednesday 13 July 2005 3:46:12 am Well, as the name suggest, override settings override other settings. Which would explain it being placed last in the list. How I have solved sharing common settings, is simply to put all global settings in override/.ini, and then place site-specific settings in the siteaccess folder. That way you shouldn't have to replicate anything. That said, I can understand what you mean, and it would be nice. The only way I can think of to do that right now, is to place your "default" values in settings/site.ini, and place more specialized values in the settings/siteaccess/ folders, leaving override/site.ini.append empty regarding these values. But modifying the "original" site.ini isn't a good solution in my eyes, so... /David
Bertrand Dunogier	Wednesday 13 July 2005 4:32:13 am Yeah, I'm doing something similar. But what I feel is missing is an additionnal level of override. When you have 2 siteaccess, a user one and an admin one, the current system is perfect. But when you have several user siteaccess, you can not use the global override for everything... for instance RequireUserLogin, SiteDesign, etc. They will be similar for every user siteaccess, but different for the admin one, so you can't use the global override files for those.

Author

Message

Wednesday 13 July 2005 2:40:06 am

I'm setting up a multilingual site with ezp, and either I don't understand something, either something doesn't make sense.

The current settings override order:
- settings/x.ini
- settings/siteaccess/y/x.ini.append
- settings/override/x.ini.append

doesn't sound logical to me. Initially, I thought it would have been global => global override => siteaccess.

That way for instance, you can setup all the common stuff in global overrides, then finetunes for each siteaccess in the respective ini files.

In my multilanguage website example, I could have done:

override/site.ini.append:

[SiteSettings]
LoginPage=embedded

then in siteaccess/foo/site.ini.append
[SiteSettings]
SiteName=...
SiteURL=...

And so on.

Now I have to totally replicate the siteaccess folder and edit all files everytime. I'm not even sure how i'm gonna handle my overrides, actually :)

<b>suggestion:</b>
I was thinking about an additionnal setting like AdditionnalSiteSettingsList which would let you specify an override folder where settings would be loaded for that siteaccess.

Thoughts ? And maybe suggestions if I'm doing something wrong... :)

Thanks !

David Eriksson

Wednesday 13 July 2005 3:46:12 am

Well, as the name suggest, override settings override other settings. Which would explain it being placed last in the list.

How I have solved sharing common settings, is simply to put all global settings in override/.ini, and then place site-specific settings in the siteaccess folder. That way you shouldn't have to replicate anything.

That said, I can understand what you mean, and it would be nice. The only way I can think of to do that right now, is to place your "default" values in settings/site.ini, and place more specialized values in the settings/siteaccess/ folders, leaving override/site.ini.append empty regarding these values. But modifying the "original" site.ini isn't a good solution in my eyes, so...

/David

Bertrand Dunogier

Wednesday 13 July 2005 4:32:13 am

Yeah, I'm doing something similar.

But what I feel is missing is an additionnal level of override. When you have 2 siteaccess, a user one and an admin one, the current system is perfect.

But when you have several user siteaccess, you can not use the global override for everything... for instance RequireUserLogin, SiteDesign, etc. They will be similar for every user siteaccess, but different for the admin one, so you can't use the global override files for those.

eZ debug

Timing:	Jan 31 2025 06:18:05
Script start
Timing:	Jan 31 2025 06:18:05
Module start 'layout'
Timing:	Jan 31 2025 06:18:05
Module start 'content'
Timing:	Jan 31 2025 06:18:06
Module end 'content'
Timing:	Jan 31 2025 06:18:06
Script end

Main resources:

Total runtime	1.3425 sec
Peak memory usage	4,096.0000 KB
Database Queries	57

Timing points:

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0068	588.1250	151.2109
Module start 'layout'	0.0068	0.0030	739.3359	36.6484
Module start 'content'	0.0099	1.3317	775.9844	897.4844
Module end 'content'	1.3415	0.0009	1,673.4688	11.8594
Script end	1.3424		1,685.3281

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0032	0.2388	16	0.0002
Check MTime	0.0013	0.0938	16	0.0001
Mysql Total
Database connection	0.0009	0.0658	1	0.0009
Mysqli_queries	1.2877	95.9162	57	0.0226
Looping result	0.0007	0.0554	55	0.0000
Template Total	1.3052	97.2	2	0.6526
Template load	0.0021	0.1581	2	0.0011
Template processing	1.3030	97.0618	2	0.6515
Template load and register function	0.0017	0.1274	1	0.0017
states
state_id_array	0.0021	0.1551	1	0.0021
state_identifier_array	0.0030	0.2253	2	0.0015
Override
Cache load	0.0017	0.1270	31	0.0001
Sytem overhead
Fetch class attribute can translate value	0.0005	0.0338	2	0.0002
Fetch class attribute name	0.0043	0.3173	3	0.0014
XML
Image XML parsing	0.0002	0.0161	2	0.0001
class_abstraction
Instantiating content class attribute	0.0001	0.0112	3	0.0000
General
dbfile	0.0006	0.0458	10	0.0001
String conversion	0.0000	0.0009	4	0.0000
Note: percentages do not add up to 100% because some accumulators overlap

Templates used to render the page:

Usage	Requested template	Template	Template loaded
1	node/view/full.tpl	full/forum_topic.tpl	extension/sevenx/design/simple/override/templates/full/forum_topic.tpl
3	content/datatype/view/ezxmltext.tpl	<No override>	extension/community_design/design/suncana/templates/content/datatype/view/ezxmltext.tpl
6	content/datatype/view/ezxmltags/paragraph.tpl	<No override>	extension/ezwebin/design/ezwebin/templates/content/datatype/view/ezxmltags/paragraph.tpl
3	content/datatype/view/ezxmltags/line.tpl	<No override>	design/standard/templates/content/datatype/view/ezxmltags/line.tpl
1	content/datatype/view/ezxmltags/literal.tpl	<No override>	extension/community/design/standard/templates/content/datatype/view/ezxmltags/literal.tpl
1	print_pagelayout.tpl	<No override>	extension/community/design/community/templates/print_pagelayout.tpl
Number of times templates used: 15 Number of unique templates used: 6

Time used to render debug report: 0.0001 secs