$node / $module_result / $DesignKeys question

Next topic

Author	Message
Vivienne van Velzen	Thursday 25 September 2003 1:42:55 am Hi, I've searched through the site to find caching-related articles, seeing as I've succeeded in creating a really slow website. Some of the documentation is contradictory, however. I've read that it doesn't matter if you use $node in templates while using caching (<quote>Don't worry about view caching or not: when cached, the template isn't used anyway</quote> ). This was said in: http://www.ez.no/developer/ez_publish_3/documentation/customization/custom_design/template_variables_set_by_ezpublish Everywhere else tells me to use $module_result when using caching. But I'm working with a development server (caching off) and a production server (caching on). So I need a solution that will work with caching on or off. Is this possible by using the $DesignKey variable to get the node_id and then do a fetch? Or would this slow my site down even more? I really could use any advice here. TIA, Vivienne
Paul Borgermans	Thursday 25 September 2003 6:04:23 am Hi Vivienne, You van use $node in view templates for nodes: like /node/view/[full\|line\|...].tpl or in your overrides for this. When you use $node here, it will work regardless of caching: when it is cached, it won't call the template at all. It is not valid in pagelayout templates. Here you have to use $module_result... from which you can grab the nodeid and do a fetch for the node if you need that. This is also always valid (as far as I tested it) hth -paul eZ Publish, eZ Find, Solr expert consulting and training http://twitter.com/paulborgermans
Vivienne van Velzen	Thursday 25 September 2003 11:36:07 pm Thanks Paul, This certainly helped clear things up for me. Now I can bring some structure into my pages, as I was using $node and $module_result willynilly throughout the site. Vivienne

Author

Message

Thursday 25 September 2003 1:42:55 am

Hi,

I've searched through the site to find caching-related articles, seeing as I've succeeded in creating a really slow website.
Some of the documentation is contradictory, however.
I've read that it doesn't matter if you use $node in templates while using caching (<quote>Don't worry about view caching or not: when cached, the template isn't used anyway</quote> ). This was said in:
http://www.ez.no/developer/ez_publish_3/documentation/customization/custom_design/template_variables_set_by_ezpublish

Everywhere else tells me to use $module_result when using caching.
But I'm working with a development server (caching off) and a production server (caching on). So I need a solution that will work with caching on or off.
Is this possible by using the $DesignKey variable to get the node_id and then do a fetch? Or would this slow my site down even more?
I really could use any advice here. TIA,

Vivienne

Paul Borgermans

Thursday 25 September 2003 6:04:23 am

Hi Vivienne,

You van use $node in view templates for nodes:

like /node/view/[full|line|...].tpl or in your overrides for this.

When you use $node here, it will work regardless of caching: when it is cached, it won't call the template at all.

It is *not* valid in pagelayout templates. Here you have to use $module_result... from which you can grab the nodeid and do a fetch for the node if you need that. This is also always valid (as far as I tested it)

hth

-paul

eZ Publish, eZ Find, Solr expert consulting and training
http://twitter.com/paulborgermans

Vivienne van Velzen

Thursday 25 September 2003 11:36:07 pm

Thanks Paul,

This certainly helped clear things up for me. Now I can bring some structure into my pages, as I was using $node and $module_result willynilly throughout the site.

Vivienne

eZ debug

Timing:	Jan 19 2025 00:36:21
Script start
Timing:	Jan 19 2025 00:36:21
Module start 'layout'
Timing:	Jan 19 2025 00:36:21
Module start 'content'
Timing:	Jan 19 2025 00:36:22
Module end 'content'
Timing:	Jan 19 2025 00:36:22
Script end

Main resources:

Total runtime	0.8353 sec
Peak memory usage	4,096.0000 KB
Database Queries	57

Timing points:

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0110	588.0313	152.6406
Module start 'layout'	0.0110	0.0027	740.6719	39.4766
Module start 'content'	0.0137	0.8203	780.1484	535.3438
Module end 'content'	0.8339	0.0014	1,315.4922	12.1250
Script end	0.8353		1,327.6172

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0035	0.4193	16	0.0002
Check MTime	0.0016	0.1870	16	0.0001
Mysql Total
Database connection	0.0011	0.1354	1	0.0011
Mysqli_queries	0.7841	93.8621	57	0.0138
Looping result	0.0005	0.0636	55	0.0000
Template Total	0.7886	94.4	2	0.3943
Template load	0.0022	0.2658	2	0.0011
Template processing	0.7864	94.1366	2	0.3932
Template load and register function	0.0002	0.0193	1	0.0002
states
state_id_array	0.0068	0.8111	1	0.0068
state_identifier_array	0.0017	0.1999	2	0.0008
Override
Cache load	0.0019	0.2220	26	0.0001
Sytem overhead
Fetch class attribute can translate value	0.0007	0.0780	2	0.0003
Fetch class attribute name	0.0008	0.1004	4	0.0002
XML
Image XML parsing	0.0008	0.0979	2	0.0004
class_abstraction
Instantiating content class attribute	0.0000	0.0012	4	0.0000
General
dbfile	0.0008	0.0952	17	0.0000
String conversion	0.0000	0.0009	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
3	content/datatype/view/ezxmltext.tpl	<No override>	extension/community_design/design/suncana/templates/content/datatype/view/ezxmltext.tpl
5	content/datatype/view/ezxmltags/paragraph.tpl	<No override>	extension/ezwebin/design/ezwebin/templates/content/datatype/view/ezxmltags/paragraph.tpl
2	content/datatype/view/ezxmltags/line.tpl	<No override>	design/standard/templates/content/datatype/view/ezxmltags/line.tpl
1	content/datatype/view/ezimage.tpl	<No override>	extension/sevenx/design/simple/templates/content/datatype/view/ezimage.tpl
1	print_pagelayout.tpl	<No override>	extension/community/design/community/templates/print_pagelayout.tpl
Number of times templates used: 13 Number of unique templates used: 6

Time used to render debug report: 0.0001 secs