nodereference

I need some help building a custom view for a new section of a portfolio site that will work as an index of Portfolio Projects. Currently I'm using the CCK, Image & Image Gallery, Node Reference URL, Views2, Views Attach, and other related or dependent modules.

As a sidebar, I also gave the SimpleViews module a try but could not get it to produce the page display I want. Perhaps this is still the way to go...maybe not?

Regardless, I'm having trouble getting a View built that will display the Portfolio Project content.

Inventory of needed pages

For an online magazine with several different article content types, rather than having editors type in byline info in field_byline for each article, I'd like the byline to be drawn from a related "content type," People. So, I'm obviously setting field_byline up as a nodereference field that draws from content type People. This will make it easy to select the writer of the article from a pull-down list (or an autocomplete field), easily keep links to author contact info updated universally across the site, etc.

There are several modules that help you list referencer nodes on the referencee node.

Two in particular take it seems the same approach of creating actual reverse nodereferences, so that each nodereference becomes a symmetrical relationship (rather than helping you see the implied relationship).

• Corresponding Node References
• BackReference

Hi,

This is about a problem I have found when trying to write a feature for a module that needs to provide back reference views to nodes based on CCK node reference fields.

What I would like this to work is that the module provides a base default view that is used to provide all back refence views. This view can be modified to add more fields, change the style, add and/or expose filters, and so on. The user can also clone this view and assign the customized clone to any particular back reference relation.

I have a node type A and node type B. B-nodes have a nodereference field that point to an A-node so that one A-node has many child B-nodes.

I need a link placed somewhere in the A-node (could be on a block as well) that says "Create a child B-node". This link should open the form to create a new B-node with the nodereference field:
1) hidden
2) pre-populated with the nid of the calling A-node

What is the best way to do that in Drupal 6?

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.