Problem/Motivation

The migration system needs to support Drupal 7's core taxonomy term reference fields, converting them (along with their settings and values) to Drupal 8 entity reference fields.

Proposed resolution

Add a field plugin to handle Drupal 7's taxonomy_term_reference fields.

Remaining tasks

  • Write the field plugin
  • Write tests of said plugin
  • Update the Drupal 7 fixture with a taxonomy term reference field or two
  • Update our integration tests to ensure that the taxonomy term reference fields and their configurations are migrated correctly
  • Update other integration tests to ensure that taxonomy term reference fields' values are migrated properly
  • Commit the patch
  • Play a glorious game of fetch with a litter of puppies

User interface changes

None.

API changes

None.

Data model changes

None.

Comments

phenaproxima created an issue. See original summary.

phenaproxima’s picture

phenaproxima
he/him
Primary language English
Location Massachusetts
commented
Status: Active » Postponed

Postponing on #2447727: Add base class for migrating reference fields.

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.

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.

quietone’s picture

quietone commented
Issue tags: +Contributed project blocker

This is needed for work on commerce_migrate. The commerce migrate Commerce 1 test fixture, which is based on Commerce Kickstart, uses taxonomy_term_reference_plain. Therefor tagging as a contributed project blocker.

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.

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.

damienmckenna’s picture

damienmckenna
Location TN, USA
commented

Given that 8.6.0's release notes say

This is the first release of Drupal 8 to offer a fully supported migration path from Drupal 7.

yet term reference fields aren't supported, would it be possible to get the release notes updated to specifically state this basic functionality doesn't work yet? Thanks.

damienmckenna’s picture

damienmckenna
Location TN, USA
commented

(alternatively, providing a link to the open migrate-d7-d8 issues might be a good way of informing visitors that the functionality isn't all finished yet)

mikelutz’s picture

mikelutz
He/Him
Primary language English
Location Michigan, USA
commented
Status: Postponed » Closed (outdated)

Term reference field support has been included since 8.0, and was updated to the field plugin system in #2833206: Convert Migrate's cckfield plugins to use the new field plugins I am aware of no major bugs in the system, but this issue is definitely outdated.