Postponed (maintainer needs more info)
Project:
Corresponding node references
Version:
7.x-4.1
Component:
Code
Priority:
Major
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
20 Sep 2011 at 13:16 UTC
Updated:
30 Dec 2012 at 17:46 UTC
Comments
Comment #1
lsolesen commentedIf I remove the entry added with cnr, the duplication goes away.
Comment #2
BenK commentedSubscribing
Comment #3
glennnz commented+1
For me, the duplication only occurs when I sort by the node reference field.
Comment #4
czigor commentedCould you explain how to reproduce this? 'Versionable nodes' means 'Revisions' from core?
Comment #5
lsolesen commentedYes, it is revisions from core. All I did was enabling the module and started making some corresponding node references. As soon as I select a node reference, the node is duplicated when selecting them in a regular view. When I try to remove the corresponding node references again it cannot save correctly the first time (only the node reference is removed - none of the other content is saved). I go back and see that the cnr reference has gone, but the content was left unchanged.
Comment #6
czigor commentedThe nodes that are affected (that appear duplicated and cannot save correctly) have revisions? Or how do revisions come to the picture?
Comment #7
lsolesen commentedYes they have revisions.
Comment #8
sandervd commentedAre you using multilingual nodes? If you are, you could try updating to the dev release; the 7.x-4.1 release doesn't handle languages correctly, which might cause duplicate records in the field data table. This could result in multiple rows in views...
Comment #9
lsolesen commentedThat did not fix the problem.
Comment #10
jonloh commentedIt's duplicating for me also for some weird reason when I view a page that uses Views.
Removing the node reference values still doesn't clear off the duplication. What I need to do is to de-select the taxonomy term, save, and re-add again. This is the only way that will clear off the duplication.
Comment #11
domidc commentedBased on explanation in #10 this issue is probably not caused by cnr