It seems that after I started using cnr together with versionable nodes, if I do a regular view, the nodes are duplicated. See here: http://vih.dk/fag

Comments

lsolesen’s picture

If I remove the entry added with cnr, the duplication goes away.

BenK’s picture

Subscribing

glennnz’s picture

+1

For me, the duplication only occurs when I sort by the node reference field.

czigor’s picture

Status: Active » Postponed (maintainer needs more info)

Could you explain how to reproduce this? 'Versionable nodes' means 'Revisions' from core?

lsolesen’s picture

Status: Postponed (maintainer needs more info) » Active

Yes, 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.

czigor’s picture

The nodes that are affected (that appear duplicated and cannot save correctly) have revisions? Or how do revisions come to the picture?

lsolesen’s picture

Yes they have revisions.

sandervd’s picture

Are 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...

lsolesen’s picture

That did not fix the problem.

jonloh’s picture

It'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.

domidc’s picture

Status: Active » Postponed (maintainer needs more info)

Based on explanation in #10 this issue is probably not caused by cnr