Impact of extension order on templates and settings

Next topic

Author	Message
Hakim Bouras	Tuesday 06 October 2009 8:38:39 am Hi, I am using EZ 4.1.3, and in my settings/override/site.ini I have two extensions, declared in the following order : [ExtensionSettings] ActiveExtensions[]=extension1 ActiveExtensions[]=extension2 I noticed that <b>the templates are overriden in the oposite order than the settings</b> in these extensions. so extension2/templates/myTemplate.tpl is used while settings in extension1/settings/site.ini are used ... Is it a normal / expected behaviour ? Thanks, Hakim
Gaetano Giunta	Tuesday 06 October 2009 8:44:47 am It depends on your definition of 'normal', I guess... It is unfortunately to be expected. Principal Consultant International Business Member of the Community Project Board
Hakim Bouras	Tuesday 06 October 2009 8:52:14 am Thanks for your reply. Well, I was expecting I was doing something wrong... So to summary, does it mean that we have to choose between using "settings override" or "template override" ? Hakim
Gaetano Giunta	Tuesday 06 October 2009 9:27:58 am There's a lot of ways to get to the results you want, usually, albeit with a maintenance burden bigger than expected. If extension A declares his templates as part of design A, you can code extension B to put his ones in design B. Then in the design fallback chain you put design B first, and the designs of extension B will always become before the ones from extension A, regardless of the order of extension loading. As for the override.ini file itself, I usually try to keep it whole in a siteaccess, and not to split it between settings/override,settings/siteaccess and extension/xxx/settings, because it is hard enough to maintain it when it is a single block (it is the only one where the order of configuration blocks matters). Note: most of the time the extensions ADD new settings, so the cases where the order of loading is important should not be many (such cases might be eg. the reset of array-valued settings as the tabs shown in the admin interface or the active login handlers). If you have many conflicts, it is generally a sign of a layering problem within your extensions. The same applies to the templates fallbacks and overrides. Principal Consultant International Business Member of the Community Project Board
Hakim Bouras	Tuesday 06 October 2009 9:48:02 am I made a mistake : settings and templates are overriden in the same order. By reading you, I realised that I used different design as you explain because I had an overriding order issue between templates and stylesheets... Having all the override mechanisms working in the same order would be easier to manage... Thanks for your help. Hakim

eZ debug

Timing:	Jan 31 2025 01:19:03
Script start
Timing:	Jan 31 2025 01:19:03
Module start 'layout'
Timing:	Jan 31 2025 01:19:03
Module start 'content'
Timing:	Jan 31 2025 01:19:04
Module end 'content'
Timing:	Jan 31 2025 01:19:04
Script end

Main resources:

Total runtime	1.1349 sec
Peak memory usage	8,192.0000 KB
Database Queries	63

Timing points:

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0043	588.2813	151.2266
Module start 'layout'	0.0043	0.0038	739.5078	220.7188
Module start 'content'	0.0081	1.1259	960.2266	4,475.6719
Module end 'content'	1.1340	0.0009	5,435.8984	15.8125
Script end	1.1348		5,451.7109

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0036	0.3178	16	0.0002
Check MTime	0.0012	0.1075	16	0.0001
Mysql Total
Database connection	0.0006	0.0497	1	0.0006
Mysqli_queries	1.0432	91.9184	63	0.0166
Looping result	0.0006	0.0503	61	0.0000
Template Total	1.0901	96.1	2	0.5451
Template load	0.0018	0.1572	2	0.0009
Template processing	1.0883	95.8974	2	0.5442
Template load and register function	0.0012	0.1083	1	0.0012
states
state_id_array	0.0015	0.1365	1	0.0015
state_identifier_array	0.0018	0.1589	2	0.0009
Override
Cache load	0.0015	0.1338	37	0.0000
Sytem overhead
Fetch class attribute can translate value	0.0020	0.1750	2	0.0010
Fetch class attribute name	0.0022	0.1951	7	0.0003
XML
Image XML parsing	0.0021	0.1848	2	0.0010
class_abstraction
Instantiating content class attribute	0.0000	0.0023	10	0.0000
General
dbfile	0.0021	0.1884	22	0.0001
String conversion	0.0000	0.0005	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
5	content/datatype/view/ezimage.tpl	<No override>	extension/sevenx/design/simple/templates/content/datatype/view/ezimage.tpl
5	content/datatype/view/ezxmltext.tpl	<No override>	extension/community_design/design/suncana/templates/content/datatype/view/ezxmltext.tpl
9	content/datatype/view/ezxmltags/paragraph.tpl	<No override>	extension/ezwebin/design/ezwebin/templates/content/datatype/view/ezxmltags/paragraph.tpl
1	content/datatype/view/ezxmltags/literal.tpl	<No override>	extension/community/design/standard/templates/content/datatype/view/ezxmltags/literal.tpl
3	content/datatype/view/ezxmltags/line.tpl	<No override>	design/standard/templates/content/datatype/view/ezxmltags/line.tpl
1	print_pagelayout.tpl	<No override>	extension/community/design/community/templates/print_pagelayout.tpl
Number of times templates used: 25 Number of unique templates used: 7

Time used to render debug report: 0.0001 secs