Infobox behaviour modification

Next topic

Author	Message
Sander van den Akker	Friday 01 August 2008 7:07:10 am Currently I'm working on a new project where I took the new website interface design as a starting point. By default this design displays child objects of the infobox class on the right side. I want to modify this behaviour but I'm not sure what is the best way to do so. I would like to display all infoboxes in the current path, so not just the child infobox objects of the current node, but also child infobox objects of it's parent, and further ancestors. Should I iterate through the $module_result.path variable and fetch infobox children for each element or is there a better way to accomplish this? And, according to the documentation a content/list_count fetch does not support multiple parent_node_id's like a content/list fetch does. Is that correct? Thanks for any help in advance! eZ Publish certified developer http://auth.ez.no/certification/verify/392313
Andrew Duck	Wednesday 17 September 2008 12:29:19 pm Hi Sander, You could iterate through and run multiple fetches as you have mentioned, another alternative is to start your fetch higher up the node tree and use the depth parameter to search deeper into the tree looking for infoboxes. Each approach obviously has performance issues associated with it, especially as you increase the total number of objects in the tree, searching with depth starts to become hazardous. If this happens to be the case then you would potentially look at writing a simple module fetch to run your own optimised sql fetch for the appropriate infoboxes. Although this may not be an issue, depending on the size of the node tree. Regards, Andrew. Andrew Duck, Executive Director, Quiqcorp Limited eZ Certified Developer and Trainer. Member of the Community Project Board http://quiqcorp.com \| http://twitter.com/andrewduck

Author

Message

Friday 01 August 2008 7:07:10 am

Currently I'm working on a new project where I took the new website interface design as a starting point. By default this design displays child objects of the infobox class on the right side. I want to modify this behaviour but I'm not sure what is the best way to do so.

I would like to display all infoboxes in the current path, so not just the child infobox objects of the current node, but also child infobox objects of it's parent, and further ancestors.

Should I iterate through the $module_result.path variable and fetch infobox children for each element or is there a better way to accomplish this?

And, according to the documentation a content/list_count fetch does not support multiple parent_node_id's like a content/list fetch does. Is that correct?

Thanks for any help in advance!

eZ Publish certified developer
http://auth.ez.no/certification/verify/392313

Andrew Duck

Wednesday 17 September 2008 12:29:19 pm

Hi Sander,

You could iterate through and run multiple fetches as you have mentioned, another alternative is to start your fetch higher up the node tree and use the depth parameter to search deeper into the tree looking for infoboxes.

Each approach obviously has performance issues associated with it, especially as you increase the total number of objects in the tree, searching with depth starts to become hazardous.

If this happens to be the case then you would potentially look at writing a simple module fetch to run your own optimised sql fetch for the appropriate infoboxes. Although this may not be an issue, depending on the size of the node tree.

Regards,
Andrew.

Andrew Duck, Executive Director, Quiqcorp Limited
eZ Certified Developer and Trainer.
Member of the Community Project Board
http://quiqcorp.com | http://twitter.com/andrewduck

eZ debug

Timing:	Jan 19 2025 04:28:31
Script start
Timing:	Jan 19 2025 04:28:31
Module start 'layout'
Timing:	Jan 19 2025 04:28:31
Module start 'content'
Timing:	Jan 19 2025 04:28:32
Module end 'content'
Timing:	Jan 19 2025 04:28:32
Script end

Main resources:

Total runtime	0.8658 sec
Peak memory usage	4,096.0000 KB
Database Queries	54

Timing points:

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0062	590.2891	152.6250
Module start 'layout'	0.0062	0.0030	742.9141	39.4609
Module start 'content'	0.0092	0.8551	782.3750	536.6563
Module end 'content'	0.8643	0.0015	1,319.0313	12.1641
Script end	0.8658		1,331.1953

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0035	0.4007	16	0.0002
Check MTime	0.0015	0.1771	16	0.0001
Mysql Total
Database connection	0.0007	0.0778	1	0.0007
Mysqli_queries	0.8148	94.1061	54	0.0151
Looping result	0.0006	0.0678	52	0.0000
Template Total	0.8317	96.1	2	0.4158
Template load	0.0020	0.2333	2	0.0010
Template processing	0.8296	95.8194	2	0.4148
Template load and register function	0.0001	0.0159	1	0.0001
states
state_id_array	0.0010	0.1175	1	0.0010
state_identifier_array	0.0009	0.1070	2	0.0005
Override
Cache load	0.0016	0.1886	17	0.0001
Sytem overhead
Fetch class attribute can translate value	0.0013	0.1461	2	0.0006
Fetch class attribute name	0.0013	0.1550	4	0.0003
XML
Image XML parsing	0.0016	0.1847	2	0.0008
class_abstraction
Instantiating content class attribute	0.0000	0.0008	4	0.0000
General
dbfile	0.0012	0.1442	25	0.0000
String conversion	0.0000	0.0012	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
2	content/datatype/view/ezimage.tpl	<No override>	extension/sevenx/design/simple/templates/content/datatype/view/ezimage.tpl
2	content/datatype/view/ezxmltext.tpl	<No override>	extension/community_design/design/suncana/templates/content/datatype/view/ezxmltext.tpl
3	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: 10 Number of unique templates used: 6

Time used to render debug report: 0.0001 secs