Problem/Motivation

Follow-up to #2912348: Handle entity_references related to Drupal 6 and 7 node translations with different IDs.

On Drupal 7 entity reference fields could reference nodes in all languages whatever the language of the referencing node. For example, an English node could reference a French node. This was possible because each translations was its own node and entity reference fields are language agnostic.

On Drupal 8 since all translation share the same ID, those migrated entity reference fields are now all referencing the same ID with no indication of what was the node language of the original node on D7.

Proposed resolution

  1. Add this to the Known Issue page, adding reference to #2144377: Entity reference autocomplete lists entity labels only in current content language
  2. Determine if these cases can be detected, and if so, warn the users about it, and point them to a documentation page where they can learn how to create an entity reference autocomplete view that shows entities in all languages. Or just fix #2144377: Entity reference autocomplete lists entity labels only in current content language

Remaining tasks

Find a solution.

User interface changes

None.

API changes

TBD.

Data model changes

None.

Comments

maxocub created an issue. See original summary.

maxocub’s picture

maxocub CreditAttribution: maxocub commented

Not Critical, but major, based on this comment from the parent issue.

catch’s picture

catch
he/him
Primary language English
CreditAttribution: catch at Third and Grove commented

Hmm this is an interesting find. All I can think would be to extend the entity reference field to include a language property so that entity ID and language are included. Agreed this isn't critical, the most likely use-case would seem to be on sites not actually using node translation but having content in different languages (some of which might be translations, but not using tnid or content_translation at all) - those sites would not be affected since everything will continue to be separate nodes in 8.x

Version: 8.6.x-dev » 8.7.x-dev

Drupal 8.6.0-alpha1 will be released the week of July 16, 2018, which means new developments and disruptive changes should now be targeted against the 8.7.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.7.x-dev » 8.8.x-dev

Drupal 8.7.0-alpha1 will be released the week of March 11, 2019, which means new developments and disruptive changes should now be targeted against the 8.8.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.8.x-dev » 8.9.x-dev

Drupal 8.8.0-alpha1 will be released the week of October 14th, 2019, which means new developments and disruptive changes should now be targeted against the 8.9.x-dev branch. (Any changes to 8.9.x will also be committed to 9.0.x in preparation for Drupal 9’s release, but some changes like significant feature additions will be deferred to 9.1.x.). For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 8.9.x-dev » 9.1.x-dev

Drupal 8.9.0-beta1 was released on March 20, 2020. 8.9.x is the final, long-term support (LTS) minor release of Drupal 8, which means new developments and disruptive changes should now be targeted against the 9.1.x-dev branch. For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 9.1.x-dev » 9.2.x-dev

Drupal 9.1.0-alpha1 will be released the week of October 19, 2020, which means new developments and disruptive changes should now be targeted for the 9.2.x-dev branch. For more information see the Drupal 9 minor version schedule and the Allowed changes during the Drupal 9 release cycle.

quietone’s picture

quietone CreditAttribution: quietone as a volunteer commented
Issue summary: View changes
quietone’s picture

quietone CreditAttribution: quietone as a volunteer commented
Issue summary: View changes

Version: 9.2.x-dev » 9.3.x-dev

Drupal 9.2.0-alpha1 will be released the week of May 3, 2021, which means new developments and disruptive changes should now be targeted for the 9.3.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.3.x-dev » 9.4.x-dev

Drupal 9.3.0-rc1 was released on November 26, 2021, which means new developments and disruptive changes should now be targeted for the 9.4.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.4.x-dev » 9.5.x-dev

Drupal 9.4.0-alpha1 was released on May 6, 2022, which means new developments and disruptive changes should now be targeted for the 9.5.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.5.x-dev » 10.1.x-dev

Drupal 9.5.0-beta2 and Drupal 10.0.0-beta2 were released on September 29, 2022, which means new developments and disruptive changes should now be targeted for the 10.1.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 10.1.x-dev » 11.x-dev

Drupal core is moving towards using a “main” branch. As an interim step, a new 11.x branch has been opened, as Drupal.org infrastructure cannot currently fully support a branch named main. New developments and disruptive changes should now be targeted for the 11.x branch, which currently accepts only minor-version allowed changes. For more information, see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.