Could you please clarify how do we deal with "Content types that can be referenced" setting ? If I understand it right this CCK setting is shared between all instances of field, so if we attach same field to 2 content types we need to check them both. So there will be possible situation where you have articles and authors, and need to enable both articles and authors to be referenced in single field, which can lead to one article node mis-reference another article node instead of an author.

Comments

jcfiala’s picture

Status: Active » Closed (won't fix)

That's part of the nodereference field, it's not something that's added by backreference.

And although it's true that the CCK setting is shared between all instances of a given field, that doesn't mean that all nodereferences share the same settings. You can set up a reference from articles that point to authors, and a different reference field from authors that point to articles, and that will work better than sharing the same field.

crea’s picture

Well project page makes impression that it only works for single field shared between content types, that's why I was asking:

Backreference Module provides a nodeapi interface to maintain 1-1 relationships between all shared instances of a nodereference field.

Could you please update module description then ?

crea’s picture

Title: Content types that can be referenced » Make it clear on project page that the module doesn't require shared nodereference field
Category: support » task
Status: Closed (won't fix) » Active
victorcoder’s picture

subscribing, it's not clear

"This means that given a field instance of field_reference1, if you add a reference to NodeBeta to NodeAlpha's field_reference1 and NodeBeta has an instance of field_reference1, then NodeAlpha will be added to NodeBeta's instance of field_reference1."

So, what to user then? 2 different fields or share one to the 2 content types?

summit’s picture

Subscribing, greetings, Martijn

thedavidmeister’s picture

subscribing, i made the same mistake.