Closed (fixed)
Project:
Corresponding node references
Version:
6.x-3.3
Component:
Code
Priority:
Major
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
16 May 2010 at 01:18 UTC
Updated:
25 Nov 2010 at 14:20 UTC
Created node A and made reference to node B (same node type), saved node A. Node A has a reference to node B (as expected). But node B has two identical references to node A.
Editing existing nodes doesn't have such problem. If node A is created and saved, then edited with making reference to node B, then node B has only one reference to node A (but if you edit node B you can see that this reference is in the second field of the form, first field is empty).
If node A is deleted, editing node B let you see that there is some text left in the fields of the form, like [nid:8672].
Reverted to version 3.2 – works OK.
Comments
Comment #1
jason.lally@gmail.com commentedI'm having this same problem. I have two references with two different delta values in the database. Can't pinpoint when this is happening, but it seems like the same case you describe. Anyone have any thoughts other than reverting to an earlier version?
Comment #2
gdud commentedI have the same problem. Even now, I don't now how to fix it.
Comment #3
mawosch commentedI have the same problem here.
In the node with double entry the first input field is empty. The second and third have the same entry.
Comment #4
jsenich commentedI'm running into this issue as well on a clean install of 3.3.
Comment #5
heatherann commentedI am also having this issue, as mawosch described, and can confirm that it only happens on node creation, not when editing already-existing nodes.
Comment #6
domidc commentedI confirm this issue working on a fix. It only happens when referencing nodes of the same type
Comment #7
domidc commentedThis is fixed in 6.4