Displaying folder description

Next topic

Author	Message
Roxanna Samii	Tuesday 02 March 2004 9:14:17 am Here is my code. I would like to display the folder description of a child folder to the Links folder. Is it possible? <h1>Useful links</h1> {let children=fetch( content, list, hash( parent_node_id, $node.node_id, sort_by, $node.sort_array, limit, 7, class_filter_type, include, class_filter_array, array( 'folder','link') ) )} {* LOOP: For each child of the node... } {section name=Child loop=$children} { Display the content of the child using a line-view template. } {node_view_gui view=line content_node=$Child:item} <hr> { End of loop. } {/section} { End of namespace. *} {/let}
Alex Jones	Tuesday 02 March 2004 9:25:36 am Yes, it is possible try using: {attribute_view_gui attribute=$:item.data_map.description} Also, a really useful tool when trying to figure out how to display parts of an item is <i>\|attribute()</i>. For example, try adding the following code to a template to see information about the currently viewed node: {$node\|attribute()} If you want more information than a single level of information you can change it to <i>attribute(2)</i> which would show a couple of levels, or <i>attribute(show)</i> which will show everything. This can seem like information overload until you realize that it will allow you to figure out sometimes-complex paths to information. Hope this helps, Alex Alex [ bald_technologist on the IRC channel (irc.freenode.net): #eZpublish ] <i>When in doubt, clear the cache.</i>

Author

Message

Tuesday 02 March 2004 9:14:17 am

Here is my code. I would like to display the folder description of a child folder to the Links folder. Is it possible?
<h1>Useful links</h1>

{let children=fetch( content, list, hash( parent_node_id, $node.node_id,
sort_by, $node.sort_array,
limit, 7,
class_filter_type, include,
class_filter_array, array(
'folder','link') ) )}

{* LOOP: For each child of the node... *}

{section name=Child loop=$children}
{* Display the content of the child using a line-view template. *}

{node_view_gui view=line content_node=$Child:item}
<hr>
{* End of loop. *}
{/section}
{* End of namespace. *}
{/let}

Alex Jones

Tuesday 02 March 2004 9:25:36 am

Yes, it is possible try using:

{attribute_view_gui attribute=$:item.data_map.description}

Also, a really useful tool when trying to figure out how to display parts of an item is <i>|attribute()</i>. For example, try adding the following code to a template to see information about the currently viewed node:

{$node|attribute()}

If you want more information than a single level of information you can change it to <i>attribute(2)</i> which would show a couple of levels, or <i>attribute(show)</i> which will show everything.

This can seem like information overload until you realize that it will allow you to figure out sometimes-complex paths to information.

Hope this helps,

Alex

Alex
[ bald_technologist on the IRC channel (irc.freenode.net): #eZpublish ]

<i>When in doubt, clear the cache.</i>

eZ debug

Timing:	Jan 18 2025 22:29:58
Script start
Timing:	Jan 18 2025 22:29:58
Module start 'layout'
Timing:	Jan 18 2025 22:29:58
Module start 'content'
Timing:	Jan 18 2025 22:29:59
Module end 'content'
Timing:	Jan 18 2025 22:29:59
Script end

Main resources:

Total runtime	0.6222 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.0084	587.9063	152.6250
Module start 'layout'	0.0084	0.0034	740.5313	39.4453
Module start 'content'	0.0118	0.6092	779.9766	527.3438
Module end 'content'	0.6210	0.0012	1,307.3203	8.1641
Script end	0.6222		1,315.4844

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0033	0.5319	16	0.0002
Check MTime	0.0013	0.2117	16	0.0001
Mysql Total
Database connection	0.0015	0.2390	1	0.0015
Mysqli_queries	0.5737	92.2058	54	0.0106
Looping result	0.0004	0.0696	52	0.0000
Template Total	0.5876	94.4	2	0.2938
Template load	0.0021	0.3446	2	0.0011
Template processing	0.5854	94.0905	2	0.2927
Template load and register function	0.0001	0.0184	1	0.0001
states
state_id_array	0.0015	0.2367	1	0.0015
state_identifier_array	0.0008	0.1287	2	0.0004
Override
Cache load	0.0018	0.2900	30	0.0001
Sytem overhead
Fetch class attribute can translate value	0.0005	0.0876	2	0.0003
Fetch class attribute name	0.0008	0.1325	3	0.0003
XML
Image XML parsing	0.0006	0.0897	2	0.0003
class_abstraction
Instantiating content class attribute	0.0000	0.0011	3	0.0000
General
dbfile	0.0008	0.1210	16	0.0000
String conversion	0.0000	0.0013	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/ezxmltext.tpl	<No override>	extension/community_design/design/suncana/templates/content/datatype/view/ezxmltext.tpl
4	content/datatype/view/ezxmltags/line.tpl	<No override>	design/standard/templates/content/datatype/view/ezxmltags/line.tpl
7	content/datatype/view/ezxmltags/paragraph.tpl	<No override>	extension/ezwebin/design/ezwebin/templates/content/datatype/view/ezxmltags/paragraph.tpl
1	content/datatype/view/ezimage.tpl	<No override>	extension/sevenx/design/simple/templates/content/datatype/view/ezimage.tpl
2	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: 18 Number of unique templates used: 7

Time used to render debug report: 0.0001 secs