We updated the module to its dev version recently, because of the issue - https://www.drupal.org/node/1545226.
But then we faced another problem. The situation is that we have node type A with unlimited node reference field to node type B. And B has a single node reference field related to A.

We have the case when there are:
node A1 referenced to B1
node A2 referenced to B2
node B1 referenced to A1
node B2 referenced to B2
When we try to refer B2 to A1 we get the Overloading message which is right(because there the node reference field has limitation to have only one value). The problem is that this does not prevent B2 node to be referenced to A1 node. And still B2 refers only to A2, which is fine, too.

I am sorry if my explanation is a bit confusing.

CommentFileSizeAuthor
#1 cnr-prevent-creation-of-overloading-references-2511436-1.patch1.02 KBmartichka5
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

martichka5’s picture

martichka5 CreditAttribution: martichka5 commented
FileSize
cnr-prevent-creation-of-overloading-references-2511436-1.patch1.02 KB

I think the reason for the case is that node_save is called before the update/save hook in the cnt module. So, the new references are first created and than validated from cnr. But although there is a message for overloading references they are created.

So, have created a patch with a small change. It takes care to unset these values from the home node.

Although it works for us, it needs review if my logic is somehow incorrect.