I'm building an IMDB like database for a theater company, and we're tracking shows to different functions people had within the show, so there are several sets of corresponding node references:
SHOW > ACTOR
field_show_director > field_was_director
field_show_producer > field_was_producer
field_show_cast > field_was_cast
field_show_musician > field_was_musician
field_show_crew > field_was_crew
field_show_ad > field_was_ad
field_show_intern > field_was_intern
When pulling up admin/settings/corresponding_node_references, the list seems to be "timing out" after 40 possible noderef combinations, so some of the later nodes are only showing up with possible links to earlier nodes (show_ad has everything but ad and intern) or not at all (no show_intern possibilities show up at all).
Comments
Comment #1
domidc commentedDoes php give you an error when it times out?
Comment #2
ClayRobeson commentedNope, I just get a list as if that's how it's supposed to be.
Comment #3
domidc commentedI dont seem able to duplicate this. Are you sure all reference that are missing are still pointing to each other?
Can you try and add the references one by one and check if they appear in settings screen?
Comment #4
ClayRobeson commentedI'm not quite sure what you mean... delete the existing node reference fields and re-create them?
I went looking in the database and there were more potential pairs listed there than showed up on the page.
But I think I see what the problem is. One of the content type's name changed, and there are still references to the old name in the corresponding_node_references table. The exact number of entries that AREN'T showing up on the page. When the content type's name changed from "actor" to "person" entries created before the change don't seem to have updated.
That makes a little more sense. Is there a way to "flush" that table and rebuild the data?
Comment #5
domidc commentedYes now I see. I ll add a flush settings option in next release
Comment #6
domidc commentedNo new features will be added. New features can be posted on http://drupal.org/project/cer which is the next evolution of cnr.