Problem/Motivation

The migration system doesn't yet support migrating Drupal 7 entity reference fields, along with their settings and values, from Drupal 7 to Drupal 8. The source module is https://www.drupal.org/project/references.

Proposed resolution

Add a field plugin to handle Drupal 7 entity reference fields.

Remaining tasks

  • Write the field plugin
  • Write tests of said plugin
  • Update the Drupal 7 fixture with an entity reference field or two
  • Update our integration tests to ensure that the entity reference fields and their configurations are migrated correctly
  • Update other integration tests to ensure that entity reference fields' values are migrated properly
  • Commit the patch
  • Cuddle several kittens

User interface changes

None.

API changes

None.

Data model changes

None.

Comments

phenaproxima created an issue. See original summary.

phenaproxima’s picture

Issue summary: View changes
Status: Active » Postponed

Version: 8.3.x-dev » 8.4.x-dev

Drupal 8.3.0-alpha1 will be released the week of January 30, 2017, which means new developments and disruptive changes should now be targeted against the 8.4.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

davidsickmiller’s picture

I'm working on migrating from a D7 site to Drupal 8.3.3, and it looks like the entity references are working. Did the plugin already get written?

Version: 8.4.x-dev » 8.5.x-dev

Drupal 8.4.0-alpha1 will be released the week of July 31, 2017, which means new developments and disruptive changes should now be targeted against the 8.5.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.5.x-dev » 8.6.x-dev

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

quietone’s picture

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.

quietone’s picture

Issue summary: View changes

Add source module

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.

quietone’s picture

Looking at core/modules/field/tests/src/Kernel/Migrate/d7/MigrateFieldInstanceWidgetSettingsTest.php I see assertions for node user and term entity reference fields. Those assertions were committed in #2611066: Migration path to entity reference field from 7.x. And the d7 EntityReference field plugin was committed in #2901851: Replace the static map in the d7_field migration by field plugins.

I am not sure what is to be done here.

quietone’s picture

Status: Postponed » Closed (outdated)

Double checked and this has been in since 8.3.x.