$node.data_map.(...) versus $node.object.data_map.(...) ?

Thursday 07 April 2005 9:44:07 am

Can someone clarify for me:

1) The conceptual difference between accessing a particular content item's data map via $node.data_map.(...) and accessing it via $node.object.data_map.(...) ?

2) The practical effects of doing things one way or the other...?

Thanks in advance.

--
chirsch{AT}gmail{d.t}com

Friday 08 April 2005 12:11:16 am

1)
The conceptual difference is that the node does not have a data_map. The node "contains" the object, so $node.object.data_map is the correct way. $node.data_map is a shortcut.

2)
Should be no practical difference.

Kristian

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

Friday 08 April 2005 12:54:18 am

I was ofcourse just thinking of using $node in the view templates in my little head. Must still early in the morning ;)

Thanks for your comment Hans!

Kristian

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

Friday 08 April 2005 9:31:52 am

I will also add this to the discussion - right now, using $node.object is very dangerous when referencing images, because of the PHP bug noted here (whose cause I still don't really comprehend):

http://www.ez.no/community/bugs/call_to_undefined_function_storedata

Working around this bug prompted my question originally -- after two solid long days of working I have finally eliminated all reference to $node.object.data_map.(image datatype attribute)[original] in my code, replacing it with $node.data_map.(...).

So.. it would seem that for all template development the safest bet by far is to use $node.data_map rather than $node.object.data_map, given the bug and Hans' TemplateOptimization comments.

Does everyone agree?

--
chirsch{AT}gmail{d.t}com

Monday 11 April 2005 4:16:28 am

I agree with you Xavier that using $node.object.data_map is conceptually better and clearer (and less confusing).

I think the reason that this was implemented was to reduce the overhead for getting the data_map. (Less calls to functional attributes.)

Kristian

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