Recreating the issue

  1. Installing a Drupal 6.38 site with Standard profile
  2. Installing "CCK-6.x-2.10" (enable only module "content", latest 2.x version for compatibility with latest content_taxonomy)
  3. Installing content_taxonomy 6.x-2.x-dev
  4. Creating a Taxonomy vocabulary "Terms"
  5. Adding a few terms
  6. Adding a "Terms" field of type "Content Taxonomy Fields" to the "Page" content type
  7. Creating a few pages with one or more terms
  8. Installing a Drupal 8.3.3 site
  9. $ drush dl migrate_tools migrate_plus migrate_upgrade-8.x-3.x-dev, on Drupal 8.3.3 site
  10. $ drush migrate-upgrade --configure-only, on Drupal 8.3.3 site

Expectation

I expected a "Taxonomy Term Reference" field being created together with a Drupal 8.3.3 "Page" content type.

Problem

As "Content Taxonomy Fields" have been used a lot in Drupal 6 sites and they are in Drupal 8 core as "Taxonomy Term Reference" fields, in my opinion it is a bug, that their field is not migrated to Drupal 8. Despite the field missing, the field migration itself is configured as "field_terms: field_terms" by migrate_upgrade, but which is ignored due to the missing destination field.

Comments

meichr created an issue. See original summary.

mikeryan’s picture

mikeryan
he/him
Primary language English
Location Murphysboro, IL, USA
CreditAttribution: mikeryan as a volunteer and at Virtuoso Performance commented
Title: drush migrate-upgrade --configure-only from Drupal 6 site doesn't create a D8 "Term reference" for a D6 "Content Taxonomy" field » Support content_taxonomy term reference fields from D6
Project: Migrate Upgrade » Drupal core
Version: 8.x-3.x-dev » 8.4.x-dev
Component: Code » migration system
Category: Bug report » Feature request
Issue tags: +migrate-d6-d8
meichr’s picture

meichr CreditAttribution: meichr as a volunteer commented
Related issues: +#2884240: D6 Taxonomy Term Reference Field is not migrated to D8 Field

This issue is related to #2884240: D6 Taxonomy Term Reference Field is not migrated to D8 Field as the process pipeline explained there is necessary only for Content Taxonomy term fields. Also, there is a workaround described in that issue, which allows migrating by adding Drupal 6 configuration. It comes with a few constraints, which are not major.

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.

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.

heddn’s picture

heddn
Primary language English
Location Nicaragua
CreditAttribution: heddn at MTech, LLC commented
Status: Active » Postponed (maintainer needs more info)

Is this still an issue?

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
Status: Postponed (maintainer needs more info) » Closed (outdated)

More information about this issue was asked for in #8, 1 year and 7 months ago. No additional information has been supplied, therefor closing.

If you are experiencing this problem, reopen the issue by setting the status to 'Active' and provide steps to reproduce.

Thanks!