Executing d7_entity_translation_settings and d7_language_content_comment_settings migrations in the calculated optimal order results in migration error

Created on 25 January 2022, over 3 years ago
Updated 24 May 2025, 4 months ago

Problem/Motivation

Executing d7_entity_translation_settings and d7_language_content_comment_settings migrations in the same order how Migrate Drupal UI executes them results in entity storage exception:

[
  0 => ''language_content_settings' entity with ID 'comment.comment_node_et' already exists. (/Users/zoli/projects/migmag/zdev/public_html/core/lib/Drupal/Core/Entity/EntityStorageBase.php:487)'
  1 => ''language_content_settings' entity with ID 'comment.comment_node_test_content_type' already exists. (/Users/zoli/projects/migmag/zdev/public_html/core/lib/Drupal/Core/Entity/EntityStorageBase.php:487)'
]

Proposed resolution

TBD. If I apply my fixes from ✨ Calling EntityConfig::import() with multiple destination IDs fails Needs work then the issue doesn't happen.

Remaining tasks

TBD.

πŸ› 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.
Sign in to follow issues

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