Cache-block problem

Thursday 03 May 2007 7:05:43 am

Hi Salvatore,

You're facing the very unfamous $node availibility issue.
Until you fetch the <b>$node</b> by yourself, with something like :

 {def $node=fetch( content , node , hash( node_id , $module_result.node_id ) 

you should <b>never</b> use the $node variable in pagelayout. It is an issue that has been <i>solved</i> in recent eZpublish releases by totally removing the $node variable thus making it no longer possible to do what you're trying.
In previous versions, the $node was available on first-time access of a node that's why your piece of code works on your 3.7.2 eZpublish version.

So here, as I've suggested earlier, you'll need to fetch the $node before using it.

:)

Best regards.

My blog : http://www.starnab.com/ezpublish / http://www.starnab.com/ / http://www.assiki-consulting.com
eZ Publish Freelance developper. Feel free to contact me +33 674 367 057
nabil at assiki d0t fr

Thursday 03 May 2007 9:26:30 am

Salvatore,

I meant that you need to fetch the node with something similar to the piece of code I pasted up there. Try this :

{cache-block keys=$uri_string}

{def  $node=fetch( 'content' , 'node' , hash( node_id , $module_result.node_id ) ) 
       $section=fetch( 'section', 'object', hash( 'section_id', $node.object.section_id ) )}
   <div id="topcontent-{$section.name|wash}">
...
  </div>
{/cache-block}

In case you need to access the $node somewhere else in your template, you should put the node fetch outside of the cache-block.

:)

My blog : http://www.starnab.com/ezpublish / http://www.starnab.com/ / http://www.assiki-consulting.com
eZ Publish Freelance developper. Feel free to contact me +33 674 367 057
nabil at assiki d0t fr