Custom Tool Trouble

Next topic

Author	Message
Fraser Hore	Tuesday 13 December 2005 2:19:24 am I've created a new tool for the right toolbar to show related items based on a keywords attribute in the node object being viewed. I've also added a condition to show the toolbar only if there is a keywords attribute that is set. With a clear cache, the toolbar shows up when there are set keywords, it displays related items as intended, and clicking on an item takes you to its page. Let's say we clicked on item A in the toolbar and we are looking at item A's page. We can click on item B in the toolbar and go to item B's page. Now, if we click on item A's link in the toolbar again, we go to item A's page but there is no toolbar! The toolbar will never appear on item A's page again until we clear the cache. I suppose that it must have something to do with view caches but i'm not very familiar with how these work. Any suggestions would be much appreciated! Here's the code in the tool template: {* Toolbar - Related *} {if is_set($node.object.data_map.keywords.content)} <div class="toolbar-item {$placement}"> {def $related_nodes=$node.object.data_map.keywords.content.related_nodes} <div class="toollist"> <div class="toollist-design"> <h2>{$title}</h2> <div class="content-view-children"> {foreach $related_nodes as $related_node} <p>{node_view_gui view=listitem content_node=$related_node}</p> {/foreach} </div> </div> </div> </div> {/if} {undef $related_nodes} Cheers, Fraser
Bruce Morrison	Tuesday 13 December 2005 3:03:28 am Hi Fraser I think this is an with the cache. When you first view he page after the cache has been cleared $node is set. On the second viewing the cached version of the page is used. In the cached version $node is not retrieved (and not set) - this is the purpose of the cache, to save unnecessary database access. Of course this doesn't help you much ;) If you are viewing a page with a node (pages like search results or the shop do not have a node_id) you will have to retrieve it first. {* Toolbar - Related *} {if is_set($module_result.content_info)} {def $current_node = fetch(content,node,hash(node_id,$module_result.content_info.node_id))} {if is_set($current_node.object.data_map.keywords.content)} <div class="toolbar-item {$placement}"> {def $related_nodes=$current_node.object.data_map.keywords.content.related_nodes} <div class="toollist"> <div class="toollist-design"> <h2>{$title}</h2> <div class="content-view-children"> {foreach $related_nodes as $related_node} <p>{node_view_gui view=listitem content_node=$related_node}</p> {/foreach} </div> </div> </div> </div> {undef $current_node} {/if} {undef $related_nodes} {/if} Cheers Bruce My Blog: http://www.stuffandcontent.com/ Follow me on twitter: http://twitter.com/brucemorrison Consolidated eZ Publish Feed : http://friendfeed.com/rooms/ez-publish
Fraser Hore	Tuesday 13 December 2005 5:42:44 am Your code works great! Thanks a lot Bruce! I appreciate your help. I'm still a litte confused as to why the node isn't available in the tool template. When i use my old code in the node/view/full template it works fine. Fetching the node in the tool template did seem to slow things down a bit. Cheers, Fraser

Author

Message

Tuesday 13 December 2005 2:19:24 am

I've created a new tool for the right toolbar to show related items based on a keywords attribute in the node object being viewed. I've also added a condition to show the toolbar only if there is a keywords attribute that is set.

With a clear cache, the toolbar shows up when there are set keywords, it displays related items as intended, and clicking on an item takes you to its page. Let's say we clicked on item A in the toolbar and we are looking at item A's page. We can click on item B in the toolbar and go to item B's page. Now, if we click on item A's link in the toolbar again, we go to item A's page but there is no toolbar! The toolbar will never appear on item A's page again until we clear the cache. I suppose that it must have something to do with view caches but i'm not very familiar with how these work. Any suggestions would be much appreciated!

Here's the code in the tool template:

{* Toolbar - Related *}
{if is_set($node.object.data_map.keywords.content)}
<div class="toolbar-item {$placement}">
{def $related_nodes=$node.object.data_map.keywords.content.related_nodes}
<div class="toollist">
<div class="toollist-design">
<h2>{$title}</h2>
<div class="content-view-children">
{foreach $related_nodes as $related_node}
<p>{node_view_gui view=listitem content_node=$related_node}</p>
{/foreach}
</div>
</div>
</div>
</div>
{/if}
{undef $related_nodes}

Cheers,

Fraser

Bruce Morrison

Tuesday 13 December 2005 3:03:28 am

Hi Fraser

I think this is an with the cache. When you first view he page after the cache has been cleared $node is set. On the second viewing the cached version of the page is used. In the cached version $node is not retrieved (and not set) - this is the purpose of the cache, to save unnecessary database access. Of course this doesn't help you much ;)

If you are viewing a page with a node (pages like search results or the shop do not have a node_id) you will have to retrieve it first.

{* Toolbar - Related *}
{if is_set($module_result.content_info)}
  {def $current_node = fetch(content,node,hash(node_id,$module_result.content_info.node_id))}
  {if is_set($current_node.object.data_map.keywords.content)}
<div class="toolbar-item {$placement}">
    {def $related_nodes=$current_node.object.data_map.keywords.content.related_nodes}
<div class="toollist">
<div class="toollist-design">
<h2>{$title}</h2>
<div class="content-view-children">
      {foreach $related_nodes as $related_node}
<p>{node_view_gui view=listitem content_node=$related_node}</p>
      {/foreach}
</div>
</div>
</div>
</div>
    {undef $current_node}
  {/if}
  {undef $related_nodes}
{/if}

Cheers
Bruce

My Blog: http://www.stuffandcontent.com/
Follow me on twitter: http://twitter.com/brucemorrison
Consolidated eZ Publish Feed : http://friendfeed.com/rooms/ez-publish

Fraser Hore

Tuesday 13 December 2005 5:42:44 am

Your code works great! Thanks a lot Bruce! I appreciate your help.

I'm still a litte confused as to why the node isn't available in the tool template. When i use my old code in the node/view/full template it works fine.

Fetching the node in the tool template did seem to slow things down a bit.

Cheers,

Fraser

eZ debug

Timing:	Jan 31 2025 01:32:24
Script start
Timing:	Jan 31 2025 01:32:24
Module start 'layout'
Timing:	Jan 31 2025 01:32:24
Module start 'content'
Timing:	Jan 31 2025 01:32:24
Module end 'content'
Timing:	Jan 31 2025 01:32:24
Script end

Main resources:

Total runtime	0.0272 sec
Peak memory usage	6,144.0000 KB
Database Queries	3

Timing points:

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0048	588.0313	151.1953
Module start 'layout'	0.0048	0.0041	739.2266	220.6563
Module start 'content'	0.0089	0.0165	959.8828	1,001.8984
Module end 'content'	0.0254	0.0017	1,961.7813	33.9922
Script end	0.0271		1,995.7734

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0026	9.7259	14	0.0002
Check MTime	0.0011	4.0358	14	0.0001
Mysql Total
Database connection	0.0010	3.7639	1	0.0010
Mysqli_queries	0.0021	7.8225	3	0.0007
Looping result	0.0000	0.1035	1	0.0000
Template Total	0.0011	4.1	1	0.0011
Template load	0.0009	3.3007	1	0.0009
Template processing	0.0002	0.8096	1	0.0002
Override
Cache load	0.0006	2.3253	1	0.0006
General
dbfile	0.0003	0.9719	8	0.0000
String conversion	0.0000	0.0377	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