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.Problem/Motivation
The conclusion described in #1907192: Multilingual product import isn't true anymore:
Yes, more than one migration is needed to handle translations. In core, there are two migrations to handle node translations, the first one executed is d6_node.yml or d7_node.yml, then d6_node_translation.yml or d7_node_translation.yml. The translation migrations handle multiple languages.
The core d7_node.yml handles translations in one migration by now. Let's try to solve this again.
One question I asked myself while looking into how core D7 node source plugin handles this: Why don't we just extend it and get support for this for free?
Steps to reproduce
Proposed resolution
Remaining tasks
User interface changes
API changes
Data model changes
Issue fork commerce_migrate-3204186
Show commands
Start within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
changes
Comments
Comment #2
Lukas von BlarerI did a first test an found out that this pretty easy to achieve in my current project and it worked right away with a i18n D7 site. Here is a issue fork that I use in my project.
Comment #4
quietone CreditAttribution: quietone as a volunteer commented@Lukas von Blarer, yes! lets add translations.
In order to include this in Commerce Migrate a test fixture is needed that has products that are translated. To avoid creating a new test fixture use the existing test fixture, ck2.php. The can be loaded into a Drupal 7 site with core tools.
php core/scripts/db-tools.php. It should also be exported with that tool as well.For support on doing that ask in #migration.
Comment #5
quietone CreditAttribution: quietone as a volunteer commented