Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.OG requires entity_reference. Since this project has a dependency on cm_project, it requires a user to enable two modules that essentially do the same thing. What features are you using that are in node reference that aren't in entity reference?
Comments
Comment #1
ckngAgreed.
However, the source of node_reference dependency is in cm_show_airings and cm_project_airings, which cm_tv_schedules depends on. So moving to cm_airing project issue queue, before this can be changed/updated within cm_tv_schedules.
Comment #3
kreynen commentedI updated the feature exports for those fields, but when using an alpha release of a module it is your responsibility to understand why it is an alpha and what is changing BEFORE building on it. The move from node references to entity references was not made on a whim. It was discussed in https://groups.drupal.org/node/293178 and https://groups.drupal.org/node/312658 and a requirements for https://drupal.org/project/cm_airing_grid
We had some luck using https://drupal.org/project/entityreference_migration to convert these fields, but that doesn't handle changes in Views, Feed Importers, or several other places were the difference between a node reference and an entity reference matters.
Comment #5
emilyf commentedFixed and new branch released in order to both support legacy as well as new version of cm_airings. This issue is resolved in the 7.x-2.x branch.