Drupal Association members fund grants that make connections all over the world.
I'm hoping this is a relatively easy question (perhaps I'm looking in the wrong place for the data I seek). I am creating a site that depends heavily on using cck and contemplate to manipulate node contents on the display end; that is, a relatively basic set of fields (including node references) are in play but I manipulate their contents with a content template to display the field data in a number of different ways to the end user on the node page.
As such I've found the nid data generated in by the node_ref field very helpful - it is made available in an array in the $node:
$node->field_noderef (array) $node->field_noderef (array) $node->field_noderef['nid'] 5 $node->field_noderef['view'] <a href="/wire/asset/5">Title</a>
However, there's nothing similar I can iterate through coming from the back-reference nodes... It appears that out of the box, this module is heavily dependent on washing the data through a view, first, which doesn't then pass node id data on to the $node I can pull from in contemplate. Hence:
$node->field_backref_6039a7d891c2aa4a4e (array) $node->field_backref_6039a7d891c2aa4a4e (array) $node->field_backref_6039a7d891c2aa4a4e['view'] <dd><div class="view view-noderelationship...[more view-generated code]
Put another way, how could I also get $node->field_backref_6039a7d891c2aa4a4e['nid'] and possibly also ['title']? In the above example?
The goal is to basically combine the outgoing node ref ID's and the incoming back-reference ID's, remove duplicates, and present them all in a "related content" list of nodes. The directionality of the references is inconsequential for my application. An inbound link from other content is just as "related" in our scenario as an outgoing one.