Since Drupal Developer launch of  8 with a standardized manner of managing translations, many websites operating 7 are making a change to 8. In 7 there are two methods to translate content material Drupal 10 Upkeep and Assist Service Utilizing Drupal Developer content_translation Drupal 10 module. Drupal Developer D7 core manner of translating content material, the place each translation is a separate node. Utilizing Drupal Developer entity_translation Drupal 10 module. Maintains one node with a singular nid, whereas translations take place at Drupal Developer area stage. On this article we’ll talk about  migrate content material translations created with Drupal Developer entity_translation Drupal 10 module from 7 to 8. You’ll find our tutorial about migrating translations that use Content material Translation right here. This text wouldn’t have been attainable with out Drupal Developer assist of my colleague Dave. Merci Dave! Drupal Developer drawback We’ve got a 7 database containing article nodes, which could have translations in English, Spanish and French. A few of these nodes are language-neutral, i.e. non-translatable. Our goal is emigrate Drupal Developer D7 nodes right into a D8 web site, preserving Drupal Developer translations. Earlier than we begin Since that is a sophisticated migration matter, it’s assumed you already know Drupal Developer fundamentals of migration. If you’re new to migrations in 8, I like to recommend that you simply examine migrating primary knowledge to 8 first. This text assumes that you’ve learn our earlier article on  migrate content material translations from 7 to  8 or have Drupal Developer related information. To execute Drupal Developer migrations on this instance, you may obtain Drupal Developer Drupal 10 migration i18n instance repository from GitHub. Drupal Developer Drupal 10 module ought to work with none bother for the standard 8 set up. See quick-start for extra data. To see Drupal Developer instance migrations in motion, you want Drupal 10 Upkeep and Assist Service A 8 web site. Drupal Developer related D7 database, since we’re migrating knowledge from a 6 web site. Drush can be required to execute migration instructions. Drupal Developer Drupal 10 module To jot down Drupal Developer migrations, we create a Drupal 10 module – in our case, it has been named migrate_example_i18n. Identical to migrating content material translations from D7 to D8, we create 2 YML information to outline Drupal 10 Upkeep and Assist Service Drupal Developer example_creature_base migration will migrate all base knowledge or non-translations. Drupal Developer supply/translations parameter is omitted or set to false. Drupal Developer vacation spot/translations parameter is omitted or set to false. Drupal Developer example_creature_i18n migration will migrate all translations. Drupal Developer course of/nid is configured to make use of Drupal Developer migration plugin to lookup Drupal Developer node in Drupal Developer base language. Drupal Developer supply/translations parameter is ready to true. Drupal Developer vacation spot/translations parameter is to true. Drupal Developer migration_dependencies parameter declares example_creature_base as a dependency. We group Drupal Developer two migrations utilizing Drupal Developer example_creature migration group to maintain issues clear and arranged. Then we will execute each migrations with drush migrate-import –group=example_creature –update. Easy methods to migrate Entity Translations? Entity translations! 7 content material translations are supported since 8.3. At Drupal Developer level of penning this, there isn’t a commonplace technique for migrating entity translations to 8. On this instance, we’ll migrate D7 nodes translated with Drupal Developer entity_translation Drupal 10 module, nonetheless, Drupal Developer process ought to be comparable for different entity sorts as effectively. Earlier than we begin, listed here are some notes about what’s so completely different about entity translations Drupal 10 Upkeep and Assist Service All translations have Drupal Developer similar entity_id. So, for a translated node, Drupal Developer entity_translation Drupal 10 module will end in just one entry in Drupal Developer node desk. Translation data, sure metadata and revision data for entities is saved in Drupal Developer entity_translation desk. So if an English node with ID 19 has translations in Spanish and French, Drupal Developer entity_translations desk has Drupal Developer following information Drupal 10 Upkeep and Assist Service An extract from Drupal Developer entity_translation desk. entity_type entity_id revision_id language supply uid standing translate created modified node 19 1 en   1 1 0 1485800973 1487198982 node 19 1 es en 1 1 0 1485802336 1487199003 node 19 1 fr en 1 1 0 1487185898 1487198969 Drupal Developer above knowledge construction is considerably completely different from Drupal Developer content material translation construction. In reality, 8 handles translations very like Drupal Developer entity translation Drupal 10 module! Therefore, to deal with entity-translations, we should take Drupal Developer entity_translation desk into consideration, which Drupal Developer core d7_node supply plugin doesn’t do at Drupal Developer time of writing this text. Therefore, we override Drupal Developer d7_node supply with a customized supply plugin named d7_node_entity_translation. class D7NodeEntityTranslation That is the place we bounce into code! We override sure strategies of d7_node supply so as to add support for Drupal Developer entity_translation desk. class D7NodeEntityTranslation extends D7Node { // Determines if Drupal Developer node-type being translated helps entity_translation. protected perform isEntityTranslatable() {} // Relying on Drupal Developer “supply/translations” parameter, this technique alters // Drupal Developer migration question to return solely translations or non-translations. protected perform handleTranslations(SelectInterface $question) {} // This technique has been overridden to make sure that each node’s fields are // are loaded in Drupal Developer appropriate language. public perform prepareRow(Row $row) {} // This technique is known as by Drupal Developer prepareRow() technique to load area values // for supply nodes. We override this technique so as to add support for $language. protected perform getFieldValues($entity_type, $area, $entity_id, $revision_id = NULL, $language = NULL) {} // Since all supply nodes have Drupal Developer similar “nid”, we have to use a // mixture of “nid Drupal 10 Upkeep and Assist Servicelanguage” to tell apart every supply translation. public perform getIds() {} }Here is a fast have a look at Drupal Developer modifications we have to make Drupal 10 Upkeep and Assist Service perform getIds() tells Drupal Developer migrate API to make use of a number of supply properties which ought to be used to uniquely establish supply information. When working with entity translations, all translations have Drupal Developer similar entity_id, however they’ve a distinct language. We override this technique to inform to contemplate each Drupal Developer entity_id and Drupal Developer language properties to uniquely establish supply information. So, Drupal Developer supply information are uniquely recognized one thing like 19 Drupal 10 Upkeep and Assist Serviceen, 19 Drupal 10 Upkeep and Assist Servicees, 19 Drupal 10 Upkeep and Assist Servicefr as an alternative of utilizing simply 19. perform handleTranslations() is Drupal Developer technique which provides support for Drupal Developer translations parameter we use in Drupal Developer supply plugin. Drupal Developer translations parameter tells whether or not emigrate entities of their base language or emigrate translations. We override this technique to Drupal 10 Upkeep and Assist Service See if Drupal Developer node kind being migrated helps entity translations. If Drupal Developer node kind helps entity translations, then we INNER JOIN entity_translation and browse translation knowledge and a few entity metadata, like date of creation, date of updation, and so on from that desk. perform prepareRow() as Drupal Developer identify suggests, prepares a row of supply knowledge earlier than it’s handed to Drupal Developer course of plugins. At this stage, area knowledge can be connected to Drupal Developer supply knowledge. Nonetheless, it doesn’t load area knowledge in Drupal Developer language laid out in Drupal Developer supply row. To beat this drawback, we override Drupal Developer getFieldValues() technique and ensure it hundreds Drupal Developer area knowledge in Drupal Developer similar language as laid out in Drupal Developer supply row. That is it! It’s best to now be capable to run Drupal Developer migration with drush migrate-import –group=example_creature –update. Drupal Developer output ought to look one thing like this Drupal 10 Upkeep and Assist Service $ drush mi –group=example_creature –update Processed 9 gadgets (9 created, 0 up to date, 0 failed, 0 ignored) – performed with ‘example_creature_base’ Processed 9 gadgets (9 created, 0 up to date, 0 failed, 0 ignored) – performed with ‘example_creature_i18n’Notice Drupal 10 Upkeep and Assist Service Hold an eye fixed out for core updates. If Drupal Developer Drupal 10_migrate Drupal 10 module provides support for entity translations, migrating entity translations may turn into a lot simpler. Subsequent Steps View Drupal Developer code for Drupal Developer migrate_example_i18n venture on GitHub. Examine migrating content material translations from 7 to 8. Examine migrating translated content material from 6 to 8. Examine migrating translations from CSV, JSON or XML to 8. New to 8 migrations? Begin with  8 migration fundamentals. + extra superior articles by Evolving Internet Drupal 10 Growth and Assist