Position of overrides in override.ini.append should not affect the application of the overrides

Next topic

Author	Message
Alex Jones	Wednesday 17 September 2003 6:34:54 am Okay, that was a long title. I'm not sure how to put it more succinctly. Sorry. Anyway, I propose that the order of overrides in the override.ini.append files should not be taken into account when presenting a page to the user. It is an unnecessary, and often confusing state of affairs. Right now, if I happen to place a class override at line 10 of my override.ini.append and a node override (which is of class 10) on line 15, the class override will be used instead of the override that applies to the specific node. That really doesn't make sense. This additional dimension doesn't provide any real benefit that I can see. Please correct me if I am missing something. While I am aware that we can place the overrides to avoid this situation, we shouldn't have to. We as developers should be able to structure the document as we wish. Ultimately, I feel that the specificity of the override itself should take precedence. So, a node override would be used instead of a class override. Section overrides would also be used over a class override, though not over a node override. Overrides should follow the example of Cascading Style Sheets as they are much the same in principle. The only reason I could see this not working would be due to additional processing of the override.ini.append file to check the specificity of the override, but surely that could be worked out in the long run. Alex Alex [ bald_technologist on the IRC channel (irc.freenode.net): #eZpublish ] <i>When in doubt, clear the cache.</i>
Alex Jones	Monday 05 January 2004 11:35:38 am Anyone else have any thoughts on this topic? Alex Alex [ bald_technologist on the IRC channel (irc.freenode.net): #eZpublish ] <i>When in doubt, clear the cache.</i>
Paul Borgermans	Monday 05 January 2004 12:18:56 pm Hi Alex, I think this will lead to a debate on what should have precedence over something else. On the other hand, what you propose sounds reasonable: node > section > class But personally, I don't care much now (3.3) that we can specify the order (precedence) in the admin interface regards -paul eZ Publish, eZ Find, Solr expert consulting and training http://twitter.com/paulborgermans
Marco Zinn	Monday 05 January 2004 5:07:08 pm I agree to both of you ;) With 3.3, priority of override in the override.ini can be changed via web. I couldn't test this yet, so i don't know, if the priority will just move the blocks in the .ini OR of the blocks get a new "priority" attribute, which determined the order. While this will be enough for me, an "intelligent" approach would keep the priority problem away from the user (admin). Yes, and this will lead to the discussion of "what is more important than some other thing?". Marco http://www.hyperroad-design.com

eZ debug

Timing:	Jan 18 2025 10:40:53
Script start
Timing:	Jan 18 2025 10:40:53
Module start 'layout'
Timing:	Jan 18 2025 10:40:53
Module start 'content'
Timing:	Jan 18 2025 10:40:54
Module end 'content'
Timing:	Jan 18 2025 10:40:54
Script end

Main resources:

Total runtime	0.6252 sec
Peak memory usage	4,096.0000 KB
Database Queries	62

Timing points:

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0069	589.8516	152.6875
Module start 'layout'	0.0069	0.0032	742.5391	39.6172
Module start 'content'	0.0101	0.6137	782.1563	598.3672
Module end 'content'	0.6238	0.0014	1,380.5234	16.0156
Script end	0.6251		1,396.5391

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0032	0.5183	16	0.0002
Check MTime	0.0013	0.2102	16	0.0001
Mysql Total
Database connection	0.0011	0.1760	1	0.0011
Mysqli_queries	0.5644	90.2735	62	0.0091
Looping result	0.0008	0.1320	60	0.0000
Template Total	0.5879	94.0	2	0.2939
Template load	0.0020	0.3161	2	0.0010
Template processing	0.5859	93.7104	2	0.2929
Template load and register function	0.0001	0.0151	1	0.0001
states
state_id_array	0.0017	0.2676	1	0.0017
state_identifier_array	0.0020	0.3250	2	0.0010
Override
Cache load	0.0017	0.2692	29	0.0001
Sytem overhead
Fetch class attribute can translate value	0.0007	0.1073	3	0.0002
Fetch class attribute name	0.0009	0.1481	7	0.0001
XML
Image XML parsing	0.0016	0.2503	3	0.0005
class_abstraction
Instantiating content class attribute	0.0000	0.0022	8	0.0000
General
dbfile	0.0010	0.1584	29	0.0000
String conversion	0.0000	0.0014	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
4	content/datatype/view/ezimage.tpl	<No override>	extension/sevenx/design/simple/templates/content/datatype/view/ezimage.tpl
4	content/datatype/view/ezxmltext.tpl	<No override>	extension/community_design/design/suncana/templates/content/datatype/view/ezxmltext.tpl
4	content/datatype/view/ezxmltags/paragraph.tpl	<No override>	extension/ezwebin/design/ezwebin/templates/content/datatype/view/ezxmltags/paragraph.tpl
1	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: 15 Number of unique templates used: 6

Time used to render debug report: 0.0001 secs