Hi,

My backreference setup has been working perfectly for a year. I have been using it to link lots of different types together. A few days ago I made a mistake and changed the value of the backreferenced field. I changed it back and went off a did a load of other things. I have only just noticed that when I saved it back to the correct field it didn't save the change (it said it had). I have changed it again and again and each time I choose a random field it saves, but as soon as I put the one I had originally back, it doesn't save the change.

This is in my logs now:

Duplicate entry 'field_group' for key 'idx_backreference_field_symmetry_right' query: UPDATE backreference_field_symmetry SET field_right = 'field_group' WHERE field_left = 'field_linked_nodes' in /var/www/sites/all/modules/backreference/backreference.module on line 368.

I have the same field_linked_nodes CCK in all content types I link together and its never been an issue having the same CCK (this is a suggested problem in another issue).

Thanks,
Paul.

Comments

techypaul’s picture

techypaul commented
Status: Active » Fixed

4 Hours of trying to fix it and after posting, I fixed it in two seconds. Heres what happened:

I have a CCK field called field_linked_nodes (which references itself on all the types I have it on). I created a new CCK field called field_billing. I configured this new field to also use field_linked_nodes. I needed it to be a separate CCK field on the main node as if there is no reference in there, then we know we haven't billed it yet. But I still wanted it to be linked back via the linked_nodes.

At some point, either immediately or after I also accidentally changed the linked_nodes field, it stopped working.

I just logged into myphpadmin and noticed the backreference table and then it all became clear. I was going to manually change it but by changing the billing CCK to n/a, I could then save and update the linked_nodes back to how it should be. I will now just create a billing CCK on the nodes I need and connect them up seperately, no big issue.

Thanks,
Paul.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.