As of now, all major migration regarding the content i,e the content type and the respective nodes are being imported from Drupal 6 to Drupal 8. Also, all the taxonomies available in the Drupal 6 instance are ported successfully to Drupal 8 instance.
However, after a successful upgrade, when the content is analysed the Taxonomy term reference that a node holds in Drupal 6 instance is no more maintained in the Drupal 8 instance.

CommentFileSizeAuthor
#20 migrate_plus.migration.upgrade_d6_term_node_2.yml1.41 KBniccottrell
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

dipali.dhole created an issue. See original summary.

dipali.dhole’s picture

dipali.dhole CreditAttribution: dipali.dhole commented
Issue tags: -Taxonomy term mapping missing while upgrading to Drupal 8 from Drupal 6 +Drupal 8.x, +taxonomy term reference
mikeryan’s picture

mikeryan
he/him
Primary language English
Location Murphysboro, IL, USA
CreditAttribution: mikeryan at Acquia commented
Title: Drupal Upgrade does not import the node's taxonomy term reference » Drupal 6 term references not migrated
Project: Migrate Upgrade » Drupal core
Version: 8.x-1.x-dev » 8.0.x-dev
Component: Code » migration system
Status: Active » Postponed (maintainer needs more info)
Issue tags: -Drupal 8.x, -taxonomy term reference

Moved to the core issue queue - anything to do with the results of the migration (as opposed to what happens in the browser during the process) is 99% sure to be in the underlying framework which actually performs the migration.

I did a test migration of my own D6 site to D8 just last week and the term-node relationships came over just fine, so I don't there's a universal problem with migrating term references. Is there anything unusual about your environment (especially the D6 side) related to taxonomy (such as contrib modules affecting taxonomy)? On the D8 side, when you say "when the content is analysed", how did you analyze it? Did you edit nodes with known term references to see if the relationships were there? If not, one possibility would be that the data itself was migrated but perhaps the proper display settings weren't...

quietone’s picture

quietone CreditAttribution: quietone commented
Issue tags: +migrate-d6-d8

Version: 8.0.x-dev » 8.1.x-dev

Drupal 8.0.6 was released on April 6 and is the final bugfix release for the Drupal 8.0.x series. Drupal 8.0.x will not receive any further development aside from security fixes. Drupal 8.1.0-rc1 is now available and sites should prepare to update to 8.1.0.

Bug reports should be targeted against the 8.1.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.2.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

akleinwaechter’s picture

akleinwaechter CreditAttribution: akleinwaechter commented

Hi,
I have the same problem. All the migrate map tables for term node relations are filled but have no destination Id. The migration says they are processed but ignored. This would normally happen if the referenced node wouldn't exist but they are all migrated. What I don't understand: Does Drupal 8 Migration generate taxonomy reference fields in the content types for Drupal 6 vocabulary while migration like the old Drupal 6 to 7 way?

Best regards
Alex

mikeryan’s picture

mikeryan
he/him
Primary language English
Location Murphysboro, IL, USA
CreditAttribution: mikeryan at Virtuoso Performance commented

@akleinwaechter - the Drupal 6->Drupal 8 upgrade process does generate term reference fields for Drupal 6 term_node relationships, yes, via the d6_vocabulary_field and d6_vocabulary_field_instance migrations.

I've just run a migration from my D6 site to D8 using the tip of 8.1.x and my term-node references are successfully migrated. So, this is still not a universal problem with the term_node migrations - there's some element that's different in your case to trigger what you're seeing. Could you look at the questions in #3 above and see if there's anything that might apply in your case?

Marc Angles’s picture

Marc Angles CreditAttribution: Marc Angles commented

Hi,

In my case (which seems to look like the description of the issue) the vocabulary on the drupal 6 was set to be french and localized. Some of the nodes have one of these terms set. On the end side of the migration the terms are not created in the vocabulary (the vocabulary IS created though).

I tried to change the vocabulary i18n config in the source (Changed to no language, to english and french) but I don't get the terms created in the drupal 8 either way.

bkeller’s picture

bkeller CreditAttribution: bkeller commented

Running an upgrade from D6 to D8.1.3. While the migration is being processed, I get this error:

Upgrading upgrade_d6_taxonomy_term
Missing bundle for entity type taxonomy_term (/var/www/XXXXXXXX/core/lib/Drupal/Core/Entity/ContentEntityStorageBase.php:83)                                                                     [error]
Upgrading upgrade_d6_vocabulary_field

After the migration, I see this with drush ms:

upgrade_d6_taxonomy_vocabulary                  Idle    6      6         0
upgrade_d6_taxonomy_term                        Idle    506    505       0
upgrade_d6_vocabulary_field                     Idle    6      0         0
upgrade_d6_vocabulary_field_instance            Idle    7      0         0
upgrade_d6_vocabulary_entity_display            Idle    7      7         0
upgrade_d6_vocabulary_entity_form_display       Idle    7      7         0
upgrade_d6_term_node_1                          Idle    465    0         0
upgrade_d6_term_node_2                          Idle    6239   0         0
upgrade_d6_term_node_3                          Idle    1409   0         0
upgrade_d6_term_node_4                          Idle    0      0         0 
upgrade_d6_term_node_5                          Idle    4465   0         0
upgrade_d6_term_node_6                          Idle    4395   0         0
upgrade_d6_term_node_revision_1                 Idle    37     0         0
upgrade_d6_term_node_revision_2                 Idle    7402   0         0
upgrade_d6_term_node_revision_3                 Idle    2043   0         0
upgrade_d6_term_node_revision_4                 Idle    0      0         0
upgrade_d6_term_node_revision_5                 Idle    5290   0         0
upgrade_d6_term_node_revision_6                 Idle    6611   0         0

Now when I look at the taxonomy term vocabs, they are present but there are only terms present for one of the vocabularies. The others are blank. When I look at the database, they are there, and if I go to edit them (/taxonomy/term/35/edit) and Save, it then shows up in the listing. Viewing the tables in the DB, I see nothing that is changed. And yes I have rebuilt Drupal cache.
The next problem of course is that since they are there but hidden from Drupal, they are not referenced in their respective nodes.

I would assume that this is an issue with the configuration of the D6 site, but I'm not sure where to start looking or where to fix this. Also, I don't understand the first error of the missing bundle, but it seems like that would be a good place to start.

Help?

Marc Angles’s picture

Marc Angles CreditAttribution: Marc Angles commented

I tried with a patch from https://www.drupal.org/node/2225775#comment-11324551, with drupal 8.2.x-dev and all the migrate tools updated to dev version.

I have those messages when running drush migrate-upgrade:

Upgrading d6_term_node:1
InvalidArgumentException: Field project_type is unknown. in Drupal\Core\Entity\ContentEntityBase->getTranslatedField() (line 471 of /drupal_root/core/lib/Drupal/Core/Entity/ContentEntityBase.php).
Field project_type is unknown. (/drupal_root/core/lib/Drupal/Core/Entity/Sql/SqlContentEntityStorage.php:756)
... and again

At the end I can find the terms in the DB but still not in the drupal UI.

Marc Angles’s picture

Marc Angles CreditAttribution: Marc Angles commented

After adding an entry for each tid in the 'taxonomy_term_hierarchy' table, the terms are now showing in the UI

mikeryan’s picture

mikeryan
he/him
Primary language English
Location Murphysboro, IL, USA
CreditAttribution: mikeryan at Virtuoso Performance commented

@Marc Angles: If the problem you're seeing is taxonomy_term_hierarchy not being populated, that would be #2744639: Taxonomy term hierarchy migration incomplete.

viirak’s picture

viirak CreditAttribution: viirak commented

My case, taxonomy terms also have its translation. Migration does not combine terms into one entity with translation, which mean terms translations are not properly migrated. Hence, the connection between translation nodes to taxonomy terms are broken.

mikeryan’s picture

mikeryan
he/him
Primary language English
Location Murphysboro, IL, USA
CreditAttribution: mikeryan at Virtuoso Performance commented
Status: Postponed (maintainer needs more info) » Active

I walked through this kind of scenario with someone on IRC yesterday, and was able to replicate the problem when running the migrations as generated through drush migrate-upgrade --configure-only, although the references worked fine when running a direct upgrade. d6_node_term maps the nid thusly:

  nid:
    -
      plugin: migration
      migration: d6_node
      source: nid
    -
      plugin: skip_on_empty
      method: row

And in the custom case it could be made to work by replacing migration: d6_node with

      migration:
        - d6_node__blog
        - d6_node__page

I.e., expanding out the specific node migrations. Seeing that, I'm not quite sure why it works at all, but it seems to me it would be less fragile if D6TermNodeDeriver would expand those node migrations.

nrambeck’s picture

nrambeck CreditAttribution: nrambeck commented

I was running into this same issue. Ran a drush migrate-upgrade --configure-only migration, then generated a custom module to store the migration configuration in. The Vocabs and Terms would migrate, but not the term/node references. Changing the *term_node_[ID].yml files as suggested by @mikeryan above resolved the problem. However, in my case using 2 underscores was not appropriate. I believe the appropriate value is whatever the ID is in the migration config for each node type. Also, I am migrating node revisions so I had to reference each individual node revision migration in *term_node_revision_[ID].yml.

Here are 2 example files after making the changes:

migrate_plus.migration.d6_term_node_1.yml

      migration:
        - d6_node_article
        - d6_node_page

migrate_plus.migration.d6_term_node_revision_1.yml

      migration:
        - d6_node_revision_article
        - d6_node_revision_page
chx’s picture

chx CreditAttribution: chx at Smartsheet, Migrate Rocks commented
Project: Drupal core » Migrate Plus
Version: 8.1.x-dev » 8.x-2.x-dev
Component: migration system » API

Until a reproduction case arises this doesn't belong in the core queue. I have no idea whatsoever what migrate plus does which might or might not break the migration process plugin or whatever else.

mikeryan’s picture

mikeryan
he/him
Primary language English
Location Murphysboro, IL, USA
CreditAttribution: mikeryan at Virtuoso Performance commented
Project: Migrate Plus » Drupal core
Version: 8.x-2.x-dev » 8.2.x-dev
Component: API » migration system

The problem is D6TermNodeDeriver as described in #14. It generates a migration process plugin referencing "d6_node", which is not a real migration and should be expanded to the actual migrations that D6NodeDeriver generates. The core upgrade UI works anyway because it's preserving nids, which just fall through here, but attempting to use the derived migrations in a custom migration scenario where IDs are not preserved will fail as described.

mikeryan’s picture

mikeryan
he/him
Primary language English
Location Murphysboro, IL, USA
CreditAttribution: mikeryan at Virtuoso Performance commented
Project: Drupal core » Migrate Upgrade
Version: 8.2.x-dev » 8.x-2.x-dev
Component: migration system » Code

Ah, I see now - the core plugin manager expands that d6_node at runtime (expandPluginIds()), so in the scenario here we need migrate-upgrade --configure-only to do the equivalent expansion when generating configuration entities...

Matt B’s picture

Matt B
Primary language English
CreditAttribution: Matt B commented

#15 @nrambeck - could you share your custom module code please? It may help me understand this better.

niccottrell’s picture

niccottrell CreditAttribution: niccottrell at Transmachina commented
FileSize
migrate_plus.migration.upgrade_d6_term_node_2.yml1.41 KB

I get the same Missing bundle for entity type taxonomy_term (/XXX/core/lib/Drupal/Core/Entity/ContentEntityStorageBase.php:83) [error] but my --configure-only generated migrate_plus.migration.upgrade_d6_term_node_2.yml looks a little different (see attachment) specifically:

source:
  plugin: d6_term_node
  vid: '2'
process:
  nid:
    -
      plugin: migration
      migration: upgrade_d6_node
      source: nid
    -
      plugin: skip_on_empty
      method: row
  type: type
  region_country: tid

that it says "upgrade_d6_node" rather than just "d6_node" like mentioned in #14.

Furthermore, the output claims that this term is migrated correctly:

Processed 5877 items (0 created, 0 updated, 0 failed, 5877 ignored) - done with 'upgrade_d6_term_node_2' [status]

But later migrations fail like:

Migration upgrade_d6_term_node_revision_18 did not meet the requirements. Missing migrations upgrade_d6_term_node_2. requirements:                      [error]
upgrade_d6_term_node_2.

Do I still need to edit the migration: entry? If so, to what?

mikeryan’s picture

mikeryan
he/him
Primary language English
Location Murphysboro, IL, USA
CreditAttribution: mikeryan as a volunteer and at Virtuoso Performance commented

@niccottrell: See comment #14 above. Edit the migration entry replacing upgrade_d6_node with a list of your specific upgrade_d6_node_* migrations.

niccottrell’s picture

niccottrell CreditAttribution: niccottrell at Transmachina commented

Thanks @mikeryan. Oh, dear. So I have 34 migrate_plus.migration.d6_term_node_XXX.yml files. Not all terms are used by all content types, will it hurt if I just list ALL content types in ALL these config files?

mikeryan’s picture

mikeryan
he/him
Primary language English
Location Murphysboro, IL, USA
CreditAttribution: mikeryan as a volunteer and at Virtuoso Performance commented

No, just a minor performance impact as it will be searching more map tables than it really needs to.

  • mikeryan committed 34f29d0 on 8.x-3.x 
    Issue #2653984 by mikeryan: Drupal 6 term references not migrated

  • mikeryan committed 9bb886e on 8.x-2.x 
    Issue #2653984 by mikeryan: Drupal 6 term references not migrated
mikeryan’s picture

mikeryan
he/him
Primary language English
Location Murphysboro, IL, USA
CreditAttribution: mikeryan as a volunteer and at Virtuoso Performance commented
Status: Active » Fixed

Done - migrations derived from d6_term_node and d6_term_node_revision now expand the references to d6_node migrations.

Matt B’s picture

Matt B
Primary language English
CreditAttribution: Matt B commented
Version: 8.x-2.x-dev » 8.x-3.0-rc1

Sorry to report, but I've tried this with Drupal 8.2.0, migrate_upgrade-8.x-3.0-rc1 and whilst all the vocabularies and terms are imported and available for selection on the node edit form, they have not been assigned to the nodes as they were in Drupal 6. Is this a separate issue?

Snippet from Drush below.

Processed 3 items (3 created, 0 updated, 0 failed, 0 ignored) - done    [status]
with 'upgrade_d6_taxonomy_vocabulary'
Processed 28 items (28 created, 0 updated, 0 failed, 0 ignored) -       [status]
done with 'upgrade_d6_taxonomy_term'
Processed 3 items (3 created, 0 updated, 0 failed, 0 ignored) - done    [status]
with 'upgrade_d6_vocabulary_field'
Processed 4 items (4 created, 0 updated, 0 failed, 0 ignored) - done    [status]
with 'upgrade_d6_vocabulary_field_instance'
Processed 4 items (4 created, 0 updated, 0 failed, 0 ignored) - done    [status]
with 'upgrade_d6_vocabulary_entity_display'
Processed 4 items (4 created, 0 updated, 0 failed, 0 ignored) - done    [status]
with 'upgrade_d6_vocabulary_entity_form_display'
Migration upgrade_d6_term_node_1 did not meet the requirements.          [error]
Missing migrations upgrade_d6_node_recording_file. requirements:
upgrade_d6_node_recording_file.
Migration upgrade_d6_term_node_2 did not meet the requirements.          [error]
Missing migrations upgrade_d6_node_recording_file. requirements:
upgrade_d6_node_recording_file.
Migration upgrade_d6_term_node_3 did not meet the requirements.          [error]
Missing migrations upgrade_d6_node_recording_file. requirements:
upgrade_d6_node_recording_file.
Migration upgrade_d6_term_node_revision_1 did not meet the               [error]
requirements. Missing migrations upgrade_d6_node_recording_file,
upgrade_d6_term_node_1, upgrade_d6_term_node_2,
upgrade_d6_term_node_3, upgrade_d6_node_revision_recording_file.
requirements: upgrade_d6_node_recording_file. requirements:
upgrade_d6_term_node_1. requirements: upgrade_d6_term_node_2.
requirements: upgrade_d6_term_node_3. requirements:
upgrade_d6_node_revision_recording_file.
Migration upgrade_d6_term_node_revision_2 did not meet the               [error]
requirements. Missing migrations upgrade_d6_node_recording_file,
upgrade_d6_term_node_1, upgrade_d6_term_node_2,
upgrade_d6_term_node_3, upgrade_d6_node_revision_recording_file.
requirements: upgrade_d6_node_recording_file. requirements:
upgrade_d6_term_node_1. requirements: upgrade_d6_term_node_2.
requirements: upgrade_d6_term_node_3. requirements:
upgrade_d6_node_revision_recording_file.
Migration upgrade_d6_term_node_revision_3 did not meet the               [error]
requirements. Missing migrations upgrade_d6_node_recording_file,
upgrade_d6_term_node_1, upgrade_d6_term_node_2,
upgrade_d6_term_node_3, upgrade_d6_node_revision_recording_file.
requirements: upgrade_d6_node_recording_file. requirements:
upgrade_d6_term_node_1. requirements: upgrade_d6_term_node_2.
requirements: upgrade_d6_term_node_3. requirements:
upgrade_d6_node_revision_recording_file.
Migration upgrade_d6_upload did not meet the requirements. Missing       [error]
migrations upgrade_d6_node_recording_file. requirements:
upgrade_d6_node_recording_file.
Processed 0 items (0 created, 0 updated, 0 failed, 0 ignored) - done    [status]
with 'upgrade_d6_term_node_1'
Processed 0 items (0 created, 0 updated, 0 failed, 0 ignored) - done    [status]
with 'upgrade_d6_term_node_2'
Processed 0 items (0 created, 0 updated, 0 failed, 0 ignored) - done    [status]
with 'upgrade_d6_term_node_3'
Processed 0 items (0 created, 0 updated, 0 failed, 0 ignored) - done    [status]
with 'upgrade_d6_term_node_revision_1'
Processed 0 items (0 created, 0 updated, 0 failed, 0 ignored) - done    [status]
with 'upgrade_d6_term_node_revision_2'
Processed 0 items (0 created, 0 updated, 0 failed, 0 ignored) - done    [status]
with 'upgrade_d6_term_node_revision_3'
Processed 0 items (0 created, 0 updated, 0 failed, 0 ignored) - done    [status]
with 'upgrade_d6_upload'
mikeryan’s picture

mikeryan
he/him
Primary language English
Location Murphysboro, IL, USA
CreditAttribution: mikeryan as a volunteer and at Virtuoso Performance commented
Status: Fixed » Active 
Migration upgrade_d6_term_node_1 did not meet the requirements.          [error]
Missing migrations upgrade_d6_node_recording_file. requirements:
upgrade_d6_node_recording_file.

This is the issue reported at #2797057: Migration upgrade_d6_term_node_revision_18 did not meet the requirements. Missing migrations upgrade_d6_term_node_2.

Matt B’s picture

Matt B
Primary language English
CreditAttribution: Matt B commented

It looks like the node terms are correctly expanded, here's my migrate_plus.migration.upgrade_d6_term_node_1.yml

uuid: 7b6f0af8-91f9-4d12-a631-092f60e4a54c
langcode: en
status: true
dependencies: {  }
id: upgrade_d6_term_node_1
migration_tags:
  - 'Drupal 6'
migration_group: migrate_drupal_6
label: 'Term/node relationships'
source:
  plugin: d6_term_node
  vid: '1'
process:
  nid:
    -
      plugin: migration
      migration:
        - upgrade_d6_node_article
        - upgrade_d6_node_event
        - upgrade_d6_node_page
        - upgrade_d6_node_recording_data
        - upgrade_d6_node_recording_file
        - upgrade_d6_node_webform
      source: nid
    -
      plugin: skip_on_empty
      method: row
  type: type
  general: tid
destination:
  plugin: 'entity:node'
migration_dependencies:
  required:
    0: upgrade_d6_vocabulary_entity_display
    1: upgrade_d6_vocabulary_entity_form_display
    67: upgrade_d6_node_article
    68: upgrade_d6_node_event
    69: upgrade_d6_node_page
    70: upgrade_d6_node_recording_data
    71: upgrade_d6_node_recording_file
    72: upgrade_d6_node_webform
  optional:
    - upgrade_d6_node_article
    - upgrade_d6_node_event
    - upgrade_d6_node_page
    - upgrade_d6_node_recording_data
    - upgrade_d6_node_recording_file
    - upgrade_d6_node_webform
    - upgrade_d6_node

The error message is 

Missing migrations upgrade_d6_node_recording_file. requirements:
upgrade_d6_node_recording_file.

but there is a upgrade_d6_node_recording_file.yml ?

niccottrell’s picture

niccottrell CreditAttribution: niccottrell at Transmachina commented

Shouldn't the filename be migrate_plus.migration. upgrade_d6_node_recording_file.yml ?

mikeryan’s picture

mikeryan
he/him
Primary language English
Location Murphysboro, IL, USA
CreditAttribution: mikeryan as a volunteer and at Virtuoso Performance commented

Shouldn't the filename be migrate_plus.migration.upgrade_d6_node_recording_file.yml ?

Yes, it should. Looking at your migration .yml files, all of them should have the migrate_plus.migration. prefix, how many are missing it?

Matt B’s picture

Matt B
Primary language English
CreditAttribution: Matt B commented

I ran drush cex --destination=/tmp/export and have the following files:

migrate_plus.migration.upgrade_block_content_body_field.yml
migrate_plus.migration.upgrade_block_content_type.yml
migrate_plus.migration.upgrade_contact_category.yml
migrate_plus.migration.upgrade_d6_block.yml
migrate_plus.migration.upgrade_d6_comment_entity_display.yml
migrate_plus.migration.upgrade_d6_comment_entity_form_display_subject.yml
migrate_plus.migration.upgrade_d6_comment_entity_form_display.yml
migrate_plus.migration.upgrade_d6_comment_field_instance.yml
migrate_plus.migration.upgrade_d6_comment_field.yml
migrate_plus.migration.upgrade_d6_comment_type.yml
migrate_plus.migration.upgrade_d6_contact_settings.yml
migrate_plus.migration.upgrade_d6_custom_block.yml
migrate_plus.migration.upgrade_d6_date_formats.yml
migrate_plus.migration.upgrade_d6_dblog_settings.yml
migrate_plus.migration.upgrade_d6_field_formatter_settings.yml
migrate_plus.migration.upgrade_d6_field_instance_widget_settings.yml
migrate_plus.migration.upgrade_d6_field_instance.yml
migrate_plus.migration.upgrade_d6_field.yml
migrate_plus.migration.upgrade_d6_file.yml
migrate_plus.migration.upgrade_d6_filter_format.yml
migrate_plus.migration.upgrade_d6_node_article.yml
migrate_plus.migration.upgrade_d6_node_event.yml
migrate_plus.migration.upgrade_d6_node_page.yml
migrate_plus.migration.upgrade_d6_node_recording_data.yml
migrate_plus.migration.upgrade_d6_node_recording_file.yml
migrate_plus.migration.upgrade_d6_node_revision_article.yml
migrate_plus.migration.upgrade_d6_node_revision_event.yml
migrate_plus.migration.upgrade_d6_node_revision_page.yml
migrate_plus.migration.upgrade_d6_node_revision_recording_data.yml
migrate_plus.migration.upgrade_d6_node_revision_recording_file.yml
migrate_plus.migration.upgrade_d6_node_revision_webform.yml
migrate_plus.migration.upgrade_d6_node_setting_promote.yml
migrate_plus.migration.upgrade_d6_node_setting_status.yml
migrate_plus.migration.upgrade_d6_node_setting_sticky.yml
migrate_plus.migration.upgrade_d6_node_settings.yml
migrate_plus.migration.upgrade_d6_node_type.yml
migrate_plus.migration.upgrade_d6_node_webform.yml
migrate_plus.migration.upgrade_d6_profile_values.yml
migrate_plus.migration.upgrade_d6_search_settings.yml
migrate_plus.migration.upgrade_d6_statistics_settings.yml
migrate_plus.migration.upgrade_d6_system_cron.yml
migrate_plus.migration.upgrade_d6_system_date.yml
migrate_plus.migration.upgrade_d6_system_file.yml
migrate_plus.migration.upgrade_d6_system_performance.yml
migrate_plus.migration.upgrade_d6_taxonomy_term.yml
migrate_plus.migration.upgrade_d6_taxonomy_vocabulary.yml
migrate_plus.migration.upgrade_d6_term_node_1.yml
migrate_plus.migration.upgrade_d6_term_node_2.yml
migrate_plus.migration.upgrade_d6_term_node_3.yml
migrate_plus.migration.upgrade_d6_term_node_revision_1.yml
migrate_plus.migration.upgrade_d6_term_node_revision_2.yml
migrate_plus.migration.upgrade_d6_term_node_revision_3.yml
migrate_plus.migration.upgrade_d6_upload_entity_display.yml
migrate_plus.migration.upgrade_d6_upload_entity_form_display.yml
migrate_plus.migration.upgrade_d6_upload_field_instance.yml
migrate_plus.migration.upgrade_d6_upload_field.yml
migrate_plus.migration.upgrade_d6_upload.yml
migrate_plus.migration.upgrade_d6_url_alias.yml
migrate_plus.migration.upgrade_d6_user_contact_settings.yml
migrate_plus.migration.upgrade_d6_user_mail.yml
migrate_plus.migration.upgrade_d6_user_picture_file.yml
migrate_plus.migration.upgrade_d6_user_role.yml
migrate_plus.migration.upgrade_d6_user_settings.yml
migrate_plus.migration.upgrade_d6_user.yml
migrate_plus.migration.upgrade_d6_view_modes.yml
migrate_plus.migration.upgrade_d6_vocabulary_entity_display.yml
migrate_plus.migration.upgrade_d6_vocabulary_entity_form_display.yml
migrate_plus.migration.upgrade_d6_vocabulary_field_instance.yml
migrate_plus.migration.upgrade_d6_vocabulary_field.yml
migrate_plus.migration.upgrade_file_settings.yml
migrate_plus.migration.upgrade_menu_links.yml
migrate_plus.migration.upgrade_menu_settings.yml
migrate_plus.migration.upgrade_menu.yml
migrate_plus.migration.upgrade_search_page.yml
migrate_plus.migration.upgrade_system_image_gd.yml
migrate_plus.migration.upgrade_system_image.yml
migrate_plus.migration.upgrade_system_logging.yml
migrate_plus.migration.upgrade_system_maintenance.yml
migrate_plus.migration.upgrade_system_rss.yml
migrate_plus.migration.upgrade_system_site.yml
migrate_plus.migration.upgrade_taxonomy_settings.yml
migrate_plus.migration.upgrade_text_settings.yml
migrate_plus.migration.upgrade_update_settings.yml
migrate_plus.migration.upgrade_user_picture_entity_display.yml
migrate_plus.migration.upgrade_user_picture_entity_form_display.yml
migrate_plus.migration.upgrade_user_picture_field_instance.yml
migrate_plus.migration.upgrade_user_picture_field.yml
migrate_plus.migration.upgrade_user_profile_entity_display.yml
migrate_plus.migration.upgrade_user_profile_entity_form_display.yml
migrate_plus.migration.upgrade_user_profile_field_instance.yml
migrate_plus.migration.upgrade_user_profile_field.yml
mikeryan’s picture

mikeryan
he/him
Primary language English
Location Murphysboro, IL, USA
CreditAttribution: mikeryan as a volunteer and at Virtuoso Performance commented

I guess I'm confused by your comment #30 - there is a migrate_plus.migration. upgrade_d6_node_recording_file.yml, as expected?

Matt B’s picture

Matt B
Primary language English
CreditAttribution: Matt B commented

The full output of migrate-all --import if it may be of help. Please let me know if there is any other info that would help! 

Processed 1 item (1 created, 0 updated, 0 failed, 0 ignored) - done     [status]
with 'upgrade_block_content_type'
Processed 1 item (1 created, 0 updated, 0 failed, 0 ignored) - done     [status]
with 'upgrade_contact_category'
Processed 3 items (3 created, 0 updated, 0 failed, 0 ignored) - done    [status]
with 'upgrade_d6_date_formats'
Processed 1 item (1 created, 0 updated, 0 failed, 0 ignored) - done     [status]
with 'upgrade_d6_dblog_settings'
Processed 1 item (1 created, 0 updated, 0 failed, 0 ignored) - done     [status]
with 'upgrade_d6_search_settings'
Processed 1 item (1 created, 0 updated, 0 failed, 0 ignored) - done     [status]
with 'upgrade_d6_statistics_settings'
Processed 1 item (1 created, 0 updated, 0 failed, 0 ignored) - done     [status]
with 'upgrade_d6_system_cron'
Processed 1 item (1 created, 0 updated, 0 failed, 0 ignored) - done     [status]
with 'upgrade_d6_system_date'
Processed 1 item (0 created, 0 updated, 0 failed, 1 ignored) - done     [status]
with 'upgrade_d6_system_file'
Processed 1 item (1 created, 0 updated, 0 failed, 0 ignored) - done     [status]
with 'upgrade_d6_system_performance'
Processed 3168 items (3168 created, 0 updated, 0 failed, 0 ignored) -   [status]
done with 'upgrade_d6_url_alias'
Processed 1 item (1 created, 0 updated, 0 failed, 0 ignored) - done     [status]
with 'upgrade_d6_user_mail'
Processed 1 item (1 created, 0 updated, 0 failed, 0 ignored) - done     [status]
with 'upgrade_d6_user_settings'
Processed 1 item (1 created, 0 updated, 0 failed, 0 ignored) - done     [status]
with 'upgrade_file_settings'
Processed 1 item (1 created, 0 updated, 0 failed, 0 ignored) - done     [status]
with 'upgrade_menu_settings'
Processed 1 item (1 created, 0 updated, 0 failed, 0 ignored) - done     [status]
with 'upgrade_search_page'
Processed 1 item (1 created, 0 updated, 0 failed, 0 ignored) - done     [status]
with 'upgrade_system_image'
Processed 1 item (1 created, 0 updated, 0 failed, 0 ignored) - done     [status]
with 'upgrade_system_image_gd'
Processed 1 item (1 created, 0 updated, 0 failed, 0 ignored) - done     [status]
with 'upgrade_system_logging'
Processed 1 item (1 created, 0 updated, 0 failed, 0 ignored) - done     [status]
with 'upgrade_system_maintenance'
Processed 1 item (1 created, 0 updated, 0 failed, 0 ignored) - done     [status]
with 'upgrade_system_rss'
Processed 1 item (1 created, 0 updated, 0 failed, 0 ignored) - done     [status]
with 'upgrade_system_site'
Processed 1 item (1 created, 0 updated, 0 failed, 0 ignored) - done     [status]
with 'upgrade_taxonomy_settings'
Processed 1 item (1 created, 0 updated, 0 failed, 0 ignored) - done     [status]
with 'upgrade_text_settings'
Processed 1 item (1 created, 0 updated, 0 failed, 0 ignored) - done     [status]
with 'upgrade_update_settings'
Processed 1 item (1 created, 0 updated, 0 failed, 0 ignored) - done     [status]
with 'upgrade_block_content_body_field'
Processed 1 item (1 created, 0 updated, 0 failed, 0 ignored) - done     [status]
with 'upgrade_d6_contact_settings'
Processed 7 items (7 created, 0 updated, 0 failed, 0 ignored) - done    [status]
with 'upgrade_menu'
Missing filter plugin: filter_null.                                      [error]
Missing filter plugin: filter_null.                                      [error]
Missing filter plugin: filter_null.                                      [error]
Processed 3 items (3 created, 0 updated, 0 failed, 0 ignored) - done    [status]
with 'upgrade_d6_filter_format'
Processed 3 items (3 created, 0 updated, 0 failed, 0 ignored) - done    [status]
with 'upgrade_d6_custom_block'
Processed 7 items (7 created, 0 updated, 0 failed, 0 ignored) - done    [status]
with 'upgrade_d6_user_role'
Processed 60 items (14 created, 0 updated, 0 failed, 46 ignored) -      [status]
done with 'upgrade_d6_block'
Processed 1 item (1 created, 0 updated, 0 failed, 0 ignored) - done     [status]
with 'upgrade_d6_comment_type'
Processed 1 item (1 created, 0 updated, 0 failed, 0 ignored) - done     [status]
with 'upgrade_d6_comment_field'
Processed 6 items (6 created, 0 updated, 0 failed, 0 ignored) - done    [status]
with 'upgrade_d6_node_type'
Processed 1 item (1 created, 0 updated, 0 failed, 0 ignored) - done     [status]
with 'upgrade_d6_comment_field_instance'
Processed 1 item (1 created, 0 updated, 0 failed, 0 ignored) - done     [status]
with 'upgrade_d6_comment_entity_display'
Processed 1 item (1 created, 0 updated, 0 failed, 0 ignored) - done     [status]
with 'upgrade_d6_comment_entity_form_display'
Processed 1 item (1 created, 0 updated, 0 failed, 0 ignored) - done     [status]
with 'upgrade_d6_comment_entity_form_display_subject'
Processed 11 items (6 created, 0 updated, 0 failed, 5 ignored) - done   [status]
with 'upgrade_d6_field'
Processed 13 items (8 created, 0 updated, 0 failed, 5 ignored) - done   [status]
with 'upgrade_d6_field_instance'
Processed 7 items (7 created, 0 updated, 0 failed, 0 ignored) - done    [status]
with 'upgrade_d6_view_modes'
Processed 64 items (20 created, 0 updated, 44 failed, 0 ignored) -      [status]
done with 'upgrade_d6_field_formatter_settings'
Processed 13 items (8 created, 0 updated, 0 failed, 5 ignored) - done   [status]
with 'upgrade_d6_field_instance_widget_settings'
Processed 482 items (482 created, 0 updated, 0 failed, 0 ignored) -     [status]
done with 'upgrade_d6_file'
Processed 0 items (0 created, 0 updated, 0 failed, 0 ignored) - done    [status]
with 'upgrade_d6_user_picture_file'
Processed 1 item (1 created, 0 updated, 0 failed, 0 ignored) - done     [status]
with 'upgrade_user_picture_field'
Processed 1 item (1 created, 0 updated, 0 failed, 0 ignored) - done     [status]
with 'upgrade_user_picture_field_instance'
Processed 1 item (1 created, 0 updated, 0 failed, 0 ignored) - done     [status]
with 'upgrade_user_picture_entity_display'
Processed 1 item (1 created, 0 updated, 0 failed, 0 ignored) - done     [status]
with 'upgrade_user_picture_entity_form_display'
Processed 873 items (873 created, 0 updated, 0 failed, 0 ignored) -     [status]
done with 'upgrade_d6_user'
Processed 1 item (1 created, 0 updated, 0 failed, 0 ignored) - done     [status]
with 'upgrade_d6_node_settings'
Processed 1 item (1 created, 0 updated, 0 failed, 0 ignored) - done     [status]
with 'upgrade_d6_upload_field'
Processed 5 items (5 created, 0 updated, 0 failed, 0 ignored) - done    [status]
with 'upgrade_d6_upload_field_instance'
Processed 1928 items (1928 created, 0 updated, 0 failed, 0 ignored) -   [status]
done with 'upgrade_d6_node_article'
Processed 46 items (46 created, 0 updated, 0 failed, 0 ignored) -       [status]
done with 'upgrade_d6_node_event'
Processed 20 items (20 created, 0 updated, 0 failed, 0 ignored) -       [status]
done with 'upgrade_d6_node_page'
Processed 3043 items (3043 created, 0 updated, 0 failed, 0 ignored) -   [status]
done with 'upgrade_d6_node_recording_data'
Migration failed with source plugin exception: SQLSTATE[42S22]:          [error]
Column not found: 1054 Unknown column
'field_recordingdata_' in 'where clause': SELECT
0 AS delta
FROM 
{content_type_recording_file} t
WHERE  (field_recordingdata_ IS NOT NULL ) AND (nid =
:db_condition_placeholder_0) AND (vid = :db_condition_placeholder_1);
Array
(
    [:db_condition_placeholder_0] => 977
    [:db_condition_placeholder_1] => 7915
)

Processed 0 items (0 created, 0 updated, 0 failed, 0 ignored) - done    [status]
with 'upgrade_d6_node_recording_file'
Processed 4 items (4 created, 0 updated, 0 failed, 0 ignored) - done    [status]
with 'upgrade_d6_node_revision_article'
Processed 2 items (2 created, 0 updated, 0 failed, 0 ignored) - done    [status]
with 'upgrade_d6_node_revision_event'
Processed 8 items (8 created, 0 updated, 0 failed, 0 ignored) - done    [status]
with 'upgrade_d6_node_revision_page'
Processed 160 items (160 created, 0 updated, 0 failed, 0 ignored) -     [status]
done with 'upgrade_d6_node_revision_recording_data'
Migration upgrade_d6_node_revision_recording_file did not meet the       [error]
requirements. Missing migrations upgrade_d6_node_recording_file.
requirements: upgrade_d6_node_recording_file.
Processed 0 items (0 created, 0 updated, 0 failed, 0 ignored) - done    [status]
with 'upgrade_d6_node_revision_recording_file'
Processed 2 items (2 created, 0 updated, 0 failed, 0 ignored) - done    [status]
with 'upgrade_d6_node_webform'
Processed 1 item (1 created, 0 updated, 0 failed, 0 ignored) - done     [status]
with 'upgrade_d6_node_revision_webform'
Processed 6 items (6 created, 0 updated, 0 failed, 0 ignored) - done    [status]
with 'upgrade_d6_node_setting_promote'
Processed 6 items (6 created, 0 updated, 0 failed, 0 ignored) - done    [status]
with 'upgrade_d6_node_setting_status'
Processed 6 items (6 created, 0 updated, 0 failed, 0 ignored) - done    [status]
with 'upgrade_d6_node_setting_sticky'
Processed 7 items (7 created, 0 updated, 0 failed, 0 ignored) - done    [status]
with 'upgrade_user_profile_field'
Processed 7 items (7 created, 0 updated, 0 failed, 0 ignored) - done    [status]
with 'upgrade_user_profile_field_instance'
Processed 7 items (7 created, 0 updated, 0 failed, 0 ignored) - done    [status]
with 'upgrade_user_profile_entity_display'
Processed 7 items (7 created, 0 updated, 0 failed, 0 ignored) - done    [status]
with 'upgrade_user_profile_entity_form_display'
Processed 873 items (873 created, 0 updated, 0 failed, 0 ignored) -     [status]
done with 'upgrade_d6_profile_values'
Processed 3 items (3 created, 0 updated, 0 failed, 0 ignored) - done    [status]
with 'upgrade_d6_taxonomy_vocabulary'
Processed 28 items (28 created, 0 updated, 0 failed, 0 ignored) -       [status]
done with 'upgrade_d6_taxonomy_term'
Processed 3 items (3 created, 0 updated, 0 failed, 0 ignored) - done    [status]
with 'upgrade_d6_vocabulary_field'
Processed 4 items (4 created, 0 updated, 0 failed, 0 ignored) - done    [status]
with 'upgrade_d6_vocabulary_field_instance'
Processed 4 items (4 created, 0 updated, 0 failed, 0 ignored) - done    [status]
with 'upgrade_d6_vocabulary_entity_display'
Processed 4 items (4 created, 0 updated, 0 failed, 0 ignored) - done    [status]
with 'upgrade_d6_vocabulary_entity_form_display'
Migration upgrade_d6_term_node_1 did not meet the requirements.          [error]
Missing migrations upgrade_d6_node_recording_file. requirements:
upgrade_d6_node_recording_file.
Migration upgrade_d6_term_node_2 did not meet the requirements.          [error]
Missing migrations upgrade_d6_node_recording_file. requirements:
upgrade_d6_node_recording_file.
Migration upgrade_d6_term_node_3 did not meet the requirements.          [error]
Missing migrations upgrade_d6_node_recording_file. requirements:
upgrade_d6_node_recording_file.
Migration upgrade_d6_term_node_revision_1 did not meet the               [error]
requirements. Missing migrations upgrade_d6_node_recording_file,
upgrade_d6_term_node_1, upgrade_d6_term_node_2,
upgrade_d6_term_node_3, upgrade_d6_node_revision_recording_file.
requirements: upgrade_d6_node_recording_file. requirements:
upgrade_d6_term_node_1. requirements: upgrade_d6_term_node_2.
requirements: upgrade_d6_term_node_3. requirements:
upgrade_d6_node_revision_recording_file.
Migration upgrade_d6_term_node_revision_2 did not meet the               [error]
requirements. Missing migrations upgrade_d6_node_recording_file,
upgrade_d6_term_node_1, upgrade_d6_term_node_2,
upgrade_d6_term_node_3, upgrade_d6_node_revision_recording_file.
requirements: upgrade_d6_node_recording_file. requirements:
upgrade_d6_term_node_1. requirements: upgrade_d6_term_node_2.
requirements: upgrade_d6_term_node_3. requirements:
upgrade_d6_node_revision_recording_file.
Migration upgrade_d6_term_node_revision_3 did not meet the               [error]
requirements. Missing migrations upgrade_d6_node_recording_file,
upgrade_d6_term_node_1, upgrade_d6_term_node_2,
upgrade_d6_term_node_3, upgrade_d6_node_revision_recording_file.
requirements: upgrade_d6_node_recording_file. requirements:
upgrade_d6_term_node_1. requirements: upgrade_d6_term_node_2.
requirements: upgrade_d6_term_node_3. requirements:
upgrade_d6_node_revision_recording_file.
Migration upgrade_d6_upload did not meet the requirements. Missing       [error]
migrations upgrade_d6_node_recording_file. requirements:
upgrade_d6_node_recording_file.
Processed 0 items (0 created, 0 updated, 0 failed, 0 ignored) - done    [status]
with 'upgrade_d6_term_node_1'
Processed 0 items (0 created, 0 updated, 0 failed, 0 ignored) - done    [status]
with 'upgrade_d6_term_node_2'
Processed 0 items (0 created, 0 updated, 0 failed, 0 ignored) - done    [status]
with 'upgrade_d6_term_node_3'
Processed 0 items (0 created, 0 updated, 0 failed, 0 ignored) - done    [status]
with 'upgrade_d6_term_node_revision_1'
Processed 0 items (0 created, 0 updated, 0 failed, 0 ignored) - done    [status]
with 'upgrade_d6_term_node_revision_2'
Processed 0 items (0 created, 0 updated, 0 failed, 0 ignored) - done    [status]
with 'upgrade_d6_term_node_revision_3'
Processed 0 items (0 created, 0 updated, 0 failed, 0 ignored) - done    [status]
with 'upgrade_d6_upload'
Processed 5 items (5 created, 0 updated, 0 failed, 0 ignored) - done    [status]
with 'upgrade_d6_upload_entity_display'
Processed 5 items (5 created, 0 updated, 0 failed, 0 ignored) - done    [status]
with 'upgrade_d6_upload_entity_form_display'
Processed 873 items (873 created, 0 updated, 0 failed, 0 ignored) -     [status]
done with 'upgrade_d6_user_contact_settings'
Processed 39 items (39 created, 0 updated, 0 failed, 0 ignored) -       [status]
done with 'upgrade_menu_links'
mikeryan’s picture

mikeryan
he/him
Primary language English
Location Murphysboro, IL, USA
CreditAttribution: mikeryan as a volunteer and at Virtuoso Performance commented

Ah, that wasn't your comment, never mind...

Matt B’s picture

Matt B
Primary language English
CreditAttribution: Matt B commented

I've tried with Drupal 8.2.1, Migrate Plus 8.x-3.0-beta1 and Migrate Tools 8.x-3.0-beta1 - still having the same problem.

Matt B’s picture

Matt B
Primary language English
CreditAttribution: Matt B commented
Status: Active » Fixed

I've followed the instructions here: https://www.drupal.org/project/migrate_upgrade/releases/8.x-3.0-rc1 to create a custom module, and commented out the references to upgrade_d6_node_recording_file in the term_node and term_node_revision yml files, nd it now works. Some warnings and errors, but I believe this is something to do with the recording_file or recording_data content type on my D6 system (possible use of node references), which I can work around if needs be.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.

drzraf’s picture

drzraf CreditAttribution: drzraf commented

It was pushed into migrate_upgrade 8.x-3.x
But for people still experiencing the issue (especially the one described by @Marc Angles in comment 10): see #2827867: InvalidArgumentException: Field <taxonomy-slug> is unknown. in Drupal\Core\Entity\ContentEntityBase->getTranslatedField() (line 472 core/lib/Drupal/Core/Entity/ContentEntityBase.php)
@mikeryan: About the different behaviours between configure --only and migrate-upgrade (#2653984-14: Drupal 6 term references not migrated #2823414-15: User Profile field values not migrated from Drupal 6) and migrate_drupal_ui, is there a centralized issue about this?

kubrt’s picture

kubrt CreditAttribution: kubrt commented

I'm experiencing the exact same issue. Nodes are being migrated correctly, vocabularies as well but the term references are not updated.
Any further migration is happy with Processed 0 items (0 created, 0 updated, 0 failed, 0 ignored).
Migration status is happy withy unprocesssed items 

d6_term_node_1                                  Idle    17175   0         0            2017-05-24 07:36:02 
 d6_term_node_11                                 Idle    194     0         0            2017-05-24 07:36:03 
 d6_term_node_13                                 Idle    552     0         0            2017-05-24 07:36:03 
 d6_term_node_15                                 Idle    354     0         0            2017-05-24 07:36:04 
 d6_term_node_16                                 Idle    2525    0         0            2017-05-24 07:36:06 
 d6_term_node_18                                 Idle    1065    0         0            2017-05-24 07:36:07 
 d6_term_node_19                                 Idle    70      0         0            2017-05-24 07:36:07 
 d6_term_node_2                                  Idle    15861   0         0            2017-05-24 07:36:26 
 d6_term_node_20                                 Idle    2120    0         0            2017-05-24 07:36:28 
 d6_term_node_21                                 Idle    303     0         0            2017-05-24 07:36:29 
 d6_term_node_22                                 Idle    136     0         0            2017-05-24 07:36:29 
 d6_term_node_23                                 Idle    466     0         0            2017-05-24 07:36:30 
 d6_term_node_25                                 Idle    578     0         0            2017-05-24 07:36:30 
 d6_term_node_26                                 Idle    0       0         0            2017-05-24 07:36:31 
 d6_term_node_27                                 Idle    0       0         0            2017-05-24 07:36:31 
 d6_term_node_28                                 Idle    67      0         0            2017-05-24 07:36:31 
 d6_term_node_3                                  Idle    15695   0         0            2017-05-24 07:36:46 
 d6_term_node_4                                  Idle    1355    0         0            2017-05-24 07:36:47 
 d6_term_node_5                                  Idle    624     0         0            2017-05-24 07:36:48 
 d6_term_node_6                                  Idle    1416    0         0            2017-05-24 07:36:49 
 d6_term_node_7                                  Idle    437     0         0            2017-05-24 07:36:50 
 d6_term_node_8                                  Idle    2529    0         0            2017-05-24 07:36:52

No error messages at all.

I've originaly created the migrations using migrate-upgrade --configure-only and then moved them over to my custom module.
Any hints greatly appreciated.

My config migrate_plus.migration.d6_term_node_1.yml looks like this

uuid: f006fac8-a2c7-44e4-9da2-ab011c0c8dbd
langcode: en
status: true
dependencies: {  }
id: d6_term_node_1
class: null
field_plugin_method: null
cck_plugin_method: null
migration_tags:
  - 'Drupal 6'
migration_group: migrate_drupal_6
label: 'Term/node relationships'
source:
  plugin: d6_term_node
  vid: '1'
process:
  nid:
    -
      plugin: migration_lookup
      migration: d6_node
      source: nid
    -
      plugin: skip_on_empty
      method: row
  type: type
  ein_keywords: tid
destination:
  plugin: 'entity:node'
migration_dependencies:
  required:
    0: d6_vocabulary_entity_display
    1: d6_vocabulary_entity_form_display
    36: d6_node_blog
    37: d6_node_book
    38: d6_node_bpg
    39: d6_node_bundle
    40: d6_node_case
    41: d6_node_countryhp
    42: d6_node_country_report
    43: d6_node_event
    44: d6_node_expert
    45: d6_node_help_page
    46: d6_node_image
    47: d6_node_jcwi_update
    48: d6_node_job
    49: d6_node_legislation
    50: d6_node_news
    51: d6_node_organisation
    52: d6_node_page
    53: d6_node_profile
    54: d6_node_resource
    55: d6_node_simplenews
    56: d6_node_transaction
  optional: {  }
kubrt’s picture

kubrt CreditAttribution: kubrt commented

Quoting from this article

The bad news is that the mappings from nodes to taxonomy terms aren't being migrated properly - for some strange reason they're being registered correctly, but all the rows are being ignored.

Why ? Why ?
Is there really no usable way to find out why something is being ignored by the migration process?