Problems with cache-blocks and layout/set link generation?

Thursday 20 July 2006 10:13:28 am

Hi,

I am encountering some problems which I cannot diagnose: see the following piece of code.

{set-block scope=root variable=cache_ttl}0{/set-block}
...........
...........

{cache-block keys=$node.node_id subtree_expiry='content/view/full/60' expiry=86400}
								<ul>
								{set $links = fetch(content, list, hash(parent_node_id, 60,
																		sort_by, array('priority', true())))}
								{foreach $links as $link}
								{if $link.node_id|eq($node.node_id)}
									<p class="orange_no_link"><img src={'arrows_no_linksx.gif'|ezimage} border="0">{if $link.object.data_map.nome_abbreviato.data_text|count|gt(0)}{attribute_view_gui attribute = $link.object.data_map.nome_abbreviato}{else}{attribute_view_gui attribute = $link.object.data_map.nome}{/if}</p>
								{else}
									<li><a href={$link.url_alias|ezurl}>{if $link.object.data_map.nome_abbreviato.data_text|count|gt(0)}{attribute_view_gui attribute = $link.object.data_map.nome_abbreviato}{else}{attribute_view_gui attribute = $link.object.data_map.nome}{/if}</a></li>
								{/if}
								{/foreach}
								</ul>							
........


{/cache-block}

It displays the names of some fetched nodes or some short name, depending on whether the short name is set or not, and makes the link clickable or not based on which node I am viewing.

I am encountering this problem: when caches are generated after a manual deletion via admin interface, everything works well. but it happens that sometimes, the links generated by this code contain a layout/set/print part which makes the template be displayed as if it were a print layout. this template has no provisions for generating print layout links, so I am wondering what causes this problem.

Has anyone had this problem?
Cheers,

Max

Wednesday 26 July 2006 9:48:35 am

Hello Kristian

Is there a way to add $eZSys->AccessPath (see eZSys::addAccessPath used by the layout/set view) to the cache block keys?

independent eZ Publish developer and service provider | http://blog.coomanskristof.be | http://ezpedia.org

Wednesday 26 July 2006 10:26:02 am

In the pagelayout you can ofcourse use $module_result.requested_uri_string (if i remember the correct name of the variable) as a cache key, but that does not work inside the node-view-template which is what he is using here.

Kristian

http://ez.no/ez_publish/documenta...tricks/show_which_templates_are_used
http://ez.no/doc/ez_publish/techn...te_operators/miscellaneous/attribute

Thursday 27 July 2006 2:34:04 am

I tried the $link but it seems it is not defined in nodeview templates. I don't seem to be able to access that info anywhere else in the $node variable. any help?