Very useful module! However there are times when the reference node link would be for a one-to-one relationship instead of a one-to-many. For instance I have a 'part image' node that references to a specific 'part' node. Currently once I add a 'part image' node for a certain part by going to its 'part' node page I would like from then on to have the reference node link go to the node/*/edit page instead of adding another new 'part image' node. In otherwords a one-to-one relationship. I thought that maybe some check boxes called one-to-one and one-to-many could trigger the action wanted for that particular node reference. Maybe there is someway to easily do this already with your module but have not found.

Comments

quicksketch’s picture

quicksketch
he/him
commented

This feature probably won't be added. It's possible to do what you're describing through a custom module that checks if a particular node has already been referenced and then update the link being displayed, but I don't think that's going to make it into this module, as it is intended for a more generic purpose than this.

Conradical’s picture

Conradical commented

I was also looking for this behavior. In many places it is possible to specify the number of objects that may be added. Generally it is an option grouped together with "Required". I would find it useful to be able to specify "Unlimited" or 1 through 10 like the functionality provided by other CCK objects. IMHO -Thank you.

quicksketch’s picture

quicksketch
he/him
commented
Status: Active » Closed (won't fix)

Not going to happen in this module.