nodereference

Hi.

On a panels_page, I'm trying to pass the values of a Nodereference CCK field with multiple values to a panel_view, using a Relationship in the context system.

The nodereference relationship only seems to support passing the first value to the view. Looking at other relationships (term_from_node, user_from_node, etc) they all seem to pass only one object.

I'm aware of:

• Subform - http://drupal.org/project/subform - 4.7
• Add and Reference - http://drupal.org/project/add_n_reference - 4.7
• Addnode - http://drupal.org/project/addnode - 5.x
• Noderefferer Create - http://drupal.org/project/nodereferrer_create - 6.x available, depends on nodereferrer which doesn't seem to have 6.x available?

Addnode and Nodereferrer look like the leading candidates, and assuming that NR is going to be available for D6 soon, I'd use that. BUT, creating items on the same form page as Addnode does seems the most elegant.

Hi there,

a lot of requests in drupal forums address the backlinking of nodes being referenced by node reference (which is part of CCK). This can be achieved by nodereferrer or with views and additional argument handling code (which is in my opinion much more flexible).

While nodereferrer is by design read only i'm looking for a smart solution which extends the list of referencing nodes with a button „Link it!“.

Hi All,
Thanks for a great module. I'm trying to make pathauto construct hierarchical urls using cck-nodereference fields for the hierarchical relationships. And I have some questions about the tokens that are created for nodereference fields. As far as I can see the only usable token is [fieldname]-nid. Is this correct, or are the *-title and *-link tokens populated in certain circumstances?

(Please see the attached 4 sketches)

The basic idea of cck_emailer is to create a cck field type that lets you define an email address to which to mail any new node created that implements the specific cck_emailer field type.

How could CCK replace webform, and would you want to even do this? The purpose of this post is to vet an idea. There is no working code yet. This is also not an attack of any kind on the webform module, I'm just using it for comparison of what this would recreate and in order to tell if this would be any better than what the webform module already does.