All translation migrations now require that the Migrate Drupal Multilingual module (migrate_drupal_multilingual) is installed on the Drupal 8 site. This covers any type of migration for translations, include those based on the i18n module, node translations and entity translations. All the Multilingual migrations are tagged with a 'Multilingual' migration_tag.
The migrations initially using the Multilingual tag are listed here. More migrations will include the Multilingual tag as they are completed.
- d6_user_profile_field_instance_translation.yml
- d6_user_mail_translation.yml
- d6_user_settings_translation.yml
- d6_system_maintenance_translation.yml
- d6_system_site_translation.yml
- d6_taxonomy_vocabulary_translation.yml
- node_translation_menu_links.yml
- d6_entity_reference_translation.yml
- d7_entity_reference_translation.yml
- d6_node_translation.yml
- d7_node_translation.yml
- d7_entity_translation_settings.yml
- statistics_node_translation_counter.yml
- d6_menu_links_translation.yml
- d6_custom_block_translation.yml
- d6_taxonomy_term_translation.yml
- d6_block_translation.yml
Before
The migrations above would be available.
After
The migrations listed above, and any more added with the 'Multilingual' tag are only available when migrate_drupal_multilingual is enabled on the destination Drupal 8 site.
The use of the Migrate Drupal Multilingual allows further development of the Multilingual migrations to proceed without causing any unwanted side effects to upgrades that do not require Multilingual translations. When the multilingual migrations are stable this module will be removed. See #2966856: Hide and disable Drupal Migrate Multilingual and #2966859: Remove Migrate Drupal Multilingual module in Drupal 10.
