$node.node_id doesn't work in ez publish 3.4

Thursday 10 June 2004 3:26:15 am

Hi,

Is it just me who has this problem? I've found that I have to replace $node.node_id with $module_result.node_id in my templates, as $node.node_id no longer works in 3.4! Does anyone know if this is this intentional, or should I report it as a bug?

Regards,

James

Thursday 10 June 2004 8:43:54 am

I was viewing a folder node. This is an upgrade from ez 3.3, could this be something to do with it?

Thursday 10 June 2004 1:34:34 pm

I am having the same problem. I am using it primarily in pagelayout.tpls or in .tpls that are included in the main pagelayout. I tried disabling the view cache, but it was still a problem. It has broken one of my fetch functions to the point that it calls nothing.

I tested the template variables and found that only DesignKeys and and Module_result had any variable set. None of the node variables worked.

I spent 8 hours trying to rewrite this one fetch without using $node, and I have found it to be impossible (or so obtuse that it would not be worth it).

I also upgraded (though from 3.2-4). However, I tried it on several of my installations, including one that I updated from 3.3-4 and one clean 3.4-0 install. $node.name does not work in any of them. The documentation clearly seems to show that this should work.

Very frustrating. Paul - under what circumstances are you using the $node variables?

http://www.thinkcreative.com
Turning Ideas Into Strategic Solutions

Friday 11 June 2004 12:31:04 am

Just to clear things up.

The <i>$node</i> variable you accessed earlier was a leftover of the module that was run (in the case content/view), it was set before the module fetched it's template and was passed over to the pagelayout.
However this variable was never intended to be accessed globally (pagelayout.tpl) after the module is done, for instance it will not be available when caching is on since the template system is not used in that case.

We created the <i>$module_result</i> variable for this cause, it contains all information from the module even in cached made. Replace your <i>$node.node_id</i> with <i>$module_result.content_info.node_id</i> and it will work.

--
Amos

Documentation: http://ez.no/ez_publish/documentation
FAQ: http://ez.no/ez_publish/documentation/faq

Friday 11 June 2004 12:51:00 am

Jan,

Could someone from eZ update the documents to cover the $module_result.content_info variable? The main doc:

http://ez.no/ez_publish/documentation/customization/custom_design/template_variables_set_by_ezpublish

doesnt mention it so i assume its new...

paul

--
http://www.visionwt.com

Friday 11 June 2004 2:51:35 am

$node is to be used in view templates only
$module_result is to be used in pagelayout templates only

Best regards

-paul

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

Friday 11 June 2004 6:16:06 am

Actually some elements are available right trough <em>$module_result</em>.
So

$module_result.node_id

will work (just tested it myself).

So the doc page is correct.

Allthough it should probably mention <em>content_info</em> as well.

--
Amos

Documentation: http://ez.no/ez_publish/documentation
FAQ: http://ez.no/ez_publish/documentation/faq

Friday 11 June 2004 6:59:41 am

Is there an equivalent to $node.main_node_id in the $module_result? I could not find one when I viewed the attributes. The problem that I am facing is that some of my content which is displayed from an alternate location needs to display the children of the main location. I was using the main_node_id to pull the children of the main location of the node.

http://www.thinkcreative.com
Turning Ideas Into Strategic Solutions

Friday 11 June 2004 7:20:45 am

This thread might be of use too:

http://ez.no/community/forum/setup_design/search_engine_optimisation_more_efficient_use_of_the_title_tag

There is sample code, plus mention of this suggestion...

http://ez.no/community/bug_reports/always_have_a_valid_node_object_available

paul

--
http://www.visionwt.com

Friday 18 June 2004 1:40:22 am

Sorry,should have put the code in instead:

{let current_node=fetch('content','node',hash(node_id,$module_result.node_id))}

Will give you a variable called $current_node.

Regards,

James