Regression: multilingual taxonomy term migrations are failing if user tries to migrate from Drupal 7.81+ and Entity Translation 7.x-1.1

Created on 16 June 2021, over 4 years ago

Updated 23 May 2025, 4 months ago

The most recent stable release of Entity Translation uses a different i18n_mode value for translated taxonomy terms. See https://git.drupalcode.org/project/entity_translation/-/blob/7.x-1.1/ent...

This means that any user trying to migrate from an up-to-date Drupal 7 instance will lose translation data.

With the most recent Drupal 7 release + Entity Translation, create a vocabulary which allows its terms to be translated by entity translation.
Try to migrate the source Drupal 7 instance (e.g. with Migrate Drupal UI)
You'll see a logged migrate exception message thrown from the migration plugin in the IT: "No static mapping found for ''32768'' and no default value provided for destination 'language_alterable'."
You'll see that none of the term translations are migrated (d7_taxonomy_term_translation migrate map table contains skipped rows only)."

Update mappings to deal with the most recent i18n_mode.

Nothing

🐛 Bug report

Status

Postponed

Version

11.0 🔥

Component

migration system

Created by

🇭🇺Hungary huzooka Hungary 🇭🇺🇪🇺

Live updates comments and jobs are added and updated live.

Needs tests
The change is currently missing an automated test that fails when run with the original code, and succeeds when the bug has been fixed.

Incomplete comments

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

Production build 0.71.5 2024