Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Recreating the issue
- Installing a Drupal 6.38 site with Standard profile
- Installing "CCK-6.x-2.10" (enable only module "content", latest 2.x version for compatibility with latest content_taxonomy)
- Installing content_taxonomy 6.x-2.x-dev
- Creating a Taxonomy vocabulary "Terms"
- Adding a few terms
- Adding a "Terms" field of type "Content Taxonomy Fields" to the "Page" content type
- Creating a few pages with one or more terms
- Installing a Drupal 8.3.3 site
- $ drush dl migrate_tools migrate_plus migrate_upgrade-8.x-3.x-dev, on Drupal 8.3.3 site
- $ 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
Comment #2
mikeryanComment #3
meichr CreditAttribution: meichr as a volunteer commentedThis 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.
Comment #8
heddnIs this still an issue?
Comment #12
quietone CreditAttribution: quietone as a volunteer commentedMore 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!