Skip to major content
Route
ez.no / documentation / ez publish / technical manual / four.x / reference / template features / debugging / debug-accumulator
Written by:Balazs Halasy (21/03/2005 11:21 am)
Last updated by:Julia Shymova (11/09/2007 2:32 pm)
Maintainers:Balazs Halasy, Svitlana Shatokhina, Julia Shymova
Summary
Generates debug statistics for a block of template code.Usage
debug-accumulator [ id=id ] [ name=name ] ... /debug-accumulatorParameters
NameTypeDescriptionRequired id string A unique identifier string for an accumulator. No. name string A name that will be used in the debug output. No. Description
This mechanism generates some debug statistics based on the code that is encapsulated by "debug-accumulator" and "/debug-accumulator". The encapsulated code will be processed normally. The number of calls, total time and average time will be shown in the debug output.
The "id" and the "name" parameters are optional. The "id" parameter can be used to uniquely identify one accumulator. This means that if the same accumulator is used at multiple locations,
MicrosoftOffice.2010.Professional Plus 32bit Torrent Download, the values will be accumulated and appended. The "name" parameter can be used to assign a name which will be used in the debug output.
Examples Example 1
debug-accumulator
def $nodes=fetch( 'content', 'tree',
Microsoft Office Professional Plus, hash( 'parent_node_id', 2 ) )
foreach $nodes as $node
wash()
/foreach
/debug-accumulator
This example demonstrates how the "debug-accumulator" mechanism can be used to generate some debug statistics based on the encapsulated template code.