These two modules seem to do exactly the same thing. On this project's page it says that the other module seems to have issues with multiple values, but I think that's been fixed. Could these two modules be merged?

Comments

jcfiala’s picture

jcfiala commented
Category: bug » task
Priority: Critical » Major

Adjusting the settings.

I'm willing to talk about merging, but I'm having enough trouble just getting Link ready for Drupal 7 that I don't have the time to look into it at this time.

For folks looking into this, the link to Corresponding Node References is http://drupal.org/project/cnr.

BackReference at least has the benefit of being easy to search on. :)

dmitrig01’s picture

dmitrig01 commented

Er, sorry about the inflated issue status :-). Here's a corresponding issue over there: http://drupal.org/node/1212056

It looks like that project has a 7.x version whereas this one doesn't, so the way forward might just be an upgrade path. What (if any) differences are there?

jcfiala’s picture

jcfiala commented

I'm not really sure at the moment.

Actually, did you look at #788966: Drupal7 Port? Basically, because of the difficulty of replicating the current code in D7, and because Corresponding Node Reference is already in D7, there's currently no plan to update this module to Drupal 7, and we'll just let CNR take up the slack.

joelstein’s picture

joelstein commented

I agree. I'm using CNR on a D7 site with great success. I don't see any need to duplicate efforts. An upgrade path from BackReference would be helpful, but I can't tackle it right now, unfortunately.

jcfiala’s picture

jcfiala commented

So, I just threw some text up on the page for the module explaining the D7 path.

Naturally, I accept any and all patches/code bits to help people with switching from BR to CNR.

dmitrig01’s picture

dmitrig01 commented

Great. I think this is (nearly) resolved. Could you add a note on the project page to that effect?