I have two content types; Articles which contain typical fields such as body and image which are referenced by Issues that contains several node references and have been labeled; Features, Departments, and News. The Issue content type also contains fields for volume, issue and date. At this point everything is working perfectly and upon population, the Issue displays teasers of the appropriate Articles.

A node reference was then added to the Article in order to display the Issue's volume, issue and date. The appropriate checkboxes were checked on /admin/config/system/corresponding_node_references and a View created with the NID as a contextual filter and the issue as a Relationship. At this point the desired functionality is complete; Issues reference and display Articles while Articles display the Issue's volume, issue and date.

The problem occurs when a referenced article is edited. If Article A has been referenced in Issue's Feature section. Upon saving the Article's edit, the Issue will contain references to Article A in all three Issue reference fields.

I spun up a quick test an simplytest.me and the behavior is consistent. However, when the CNRs are broken (by unchecking the boxes on /admin/config/system/corresponding_node_references) new Issue references are no longer automatically added.

Any insight appreciated. Thanks.

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

NonProfit created an issue. See original summary.

NonProfit’s picture

Status: Active » Fixed

This appears to have been resolved by moving to Corresponding Entity References.

Status: Fixed » Closed (fixed)

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