sort within tree

Previous topic

Setup & design

Next topic

Author	Message
Nick Ursa	Thursday 21 December 2006 4:31:25 am I'm having trouble getting ezpublish to respect the priority when using fetch content tree: When I do: {def $items=fetch( 'content', 'tree', hash( 'parent_node_id',$top_node_to_fetch, sort_by, array('priority', true()) )))} It doesn't sort each group of children but rather sorts the whole list after the initial search, destroying the hierarchy. What I would have expected is that, starting from the parent node, it sorts the subchildren, outputs the first item, and checks for children, then sorting those subchildren, etc, before output. Currently fetch-tree behaves exactly like list. All I want is to control the order of items within the tree. Any suggestions ?
Claudia Kosny	Thursday 21 December 2006 11:03:00 am Hi Nick If you check the SQL query that is created by this fetch function you can see that this is not possible. The result you want to have is only possible if you fetch the children of each child recursively with a separate query which is not possible with an eZ template function/operator (unless you write your own, which is fairly easy to do). The only difference between tree and list is that list fetches only direct children of a node, otherwise they are the same. Claudia
Piotrek Karaś	Wednesday 11 April 2007 3:24:39 pm To be honest, I don't quite grasp the difference (or any useful difference to be precise) between list and tree content fetches. Both use the depth parameter, which makes them even more alike. And the name 'tree' is definitely misleading since there's little that we can do with the result as a tree. Can anyone give a useful example of tree fetch implementation? Thanks! -- Company: mediaSELF Sp. z o.o., http://www.mediaself.pl eZ references: http://ez.no/partners/worldwide_partners/mediaself eZ certified developer: http://ez.no/certification/verify/272585 eZ blog: http://ez.ryba.eu

Author

Message

Nick Ursa

Thursday 21 December 2006 4:31:25 am

I'm having trouble getting ezpublish to respect the priority when using fetch content tree:

When I do:

{def $items=fetch( 'content', 'tree', hash( 'parent_node_id',$top_node_to_fetch,
                                            sort_by, array('priority', true())
                                             )))}

It doesn't sort each group of children but rather sorts the whole list after the initial search, destroying the hierarchy.

What I would have expected is that, starting from the parent node, it sorts the subchildren, outputs the first item, and checks for children, then sorting those subchildren, etc, before output. Currently fetch-tree behaves exactly like list.

All I want is to control the order of items within the tree. Any suggestions ?

Claudia Kosny

Thursday 21 December 2006 11:03:00 am

Hi Nick

If you check the SQL query that is created by this fetch function you can see that this is not possible. The result you want to have is only possible if you fetch the children of each child recursively with a separate query which is not possible with an eZ template function/operator (unless you write your own, which is fairly easy to do).

The only difference between tree and list is that list fetches only direct children of a node, otherwise they are the same.

Claudia

Piotrek Karaś

Wednesday 11 April 2007 3:24:39 pm

To be honest, I don't quite grasp the difference (or any useful difference to be precise) between list and tree content fetches. Both use the depth parameter, which makes them even more alike. And the name 'tree' is definitely misleading since there's little that we can do with the result as a tree. Can anyone give a useful example of tree fetch implementation?
Thanks!

--
Company: mediaSELF Sp. z o.o., http://www.mediaself.pl
eZ references: http://ez.no/partners/worldwide_partners/mediaself
eZ certified developer: http://ez.no/certification/verify/272585
eZ blog: http://ez.ryba.eu

eZ debug

Timing:	Jan 31 2025 01:35:51
Script start
Timing:	Jan 31 2025 01:35:51
Module start 'layout'
Timing:	Jan 31 2025 01:35:51
Module start 'content'
Timing:	Jan 31 2025 01:35:51
Module end 'content'
Timing:	Jan 31 2025 01:35:51
Script end

Main resources:

Total runtime	0.0233 sec
Peak memory usage	4,096.0000 KB
Database Queries	3

Timing points:

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0045	588.0313	151.1953
Module start 'layout'	0.0045	0.0042	739.2266	220.6563
Module start 'content'	0.0087	0.0130	959.8828	997.8984
Module end 'content'	0.0217	0.0016	1,957.7813	33.9922
Script end	0.0233		1,991.7734

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0027	11.4514	14	0.0002
Check MTime	0.0011	4.6257	14	0.0001
Mysql Total
Database connection	0.0007	2.8621	1	0.0007
Mysqli_queries	0.0025	10.6237	3	0.0008
Looping result	0.0000	0.0562	1	0.0000
Template Total	0.0011	4.8	1	0.0011
Template load	0.0009	3.7541	1	0.0009
Template processing	0.0002	1.0678	1	0.0002
Override
Cache load	0.0006	2.5668	1	0.0006
General
dbfile	0.0003	1.1608	8	0.0000
String conversion	0.0000	0.0337	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	Edit	Override
1	print_pagelayout.tpl	<No override>	extension/community/design/community/templates/print_pagelayout.tpl
Number of times templates used: 1 Number of unique templates used: 1

Time used to render debug report: 0.0001 secs