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 #3118262: Calling EntityConfig::import() with multiple destination IDs fails then the issue doesn't happen.

Remaining tasks

TBD.

CommentFileSizeAuthor
#5 interdiff-3260352-2-5.txt1.31 KBhuzooka
#5 core-migrate_entity_with_id_already_exists-3260352-5--test-only.patch3.04 KBhuzooka
#2 core-migrate_entity_with_id_already_exists-3260352-2--test-only.patch3.03 KBhuzooka

Comments

huzooka created an issue. See original summary.

huzooka’s picture

huzooka
Primary language Hungarian
Location Hungary 🇭🇺🇪🇺
commented
Assigned: huzooka » Unassigned
Status: Active » Needs work
StatusFileSize
new core-migrate_entity_with_id_already_exists-3260352-2--test-only.patch3.03 KB
huzooka’s picture

huzooka
Primary language Hungarian
Location Hungary 🇭🇺🇪🇺
commented
Title: Executing d7_ migrations in the calculated optimal order results in migration error » Executing d7_entity_translation_settings and d7_language_content_comment_settings migrations in the calculated optimal order results in migration error
huzooka’s picture

huzooka
Primary language Hungarian
Location Hungary 🇭🇺🇪🇺
commented

d7_language_content_taxonomy_vocabulary_settings and d7_language_content_settings should also be involved.

huzooka’s picture

huzooka
Primary language Hungarian
Location Hungary 🇭🇺🇪🇺
commented
StatusFileSize
new core-migrate_entity_with_id_already_exists-3260352-5--test-only.patch3.04 KB
new interdiff-3260352-2-5.txt1.31 KB

Version: 9.4.x-dev » 9.5.x-dev

Drupal 9.4.0-alpha1 was released on May 6, 2022, which means new developments and disruptive changes should now be targeted for the 9.5.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

anybody’s picture

anybody
Primary language German
Location Porta Westfalica
commented

Thanks @huzooka, we're experiencing a similar issue with
d7_language_content_settings:

[error] 'language_content_settings' entity with ID 'node.page' already exists. (/var/www/html/web/core/lib/Drupal/Core/Entity/EntityStorageBase.php:553)

d7_language_content_taxonomy_vocabulary_settings:

[error] 'language_content_settings' entity with ID 'taxonomy_term.tags' already exists. (/var/www/html/web/core/lib/Drupal/Core/Entity/EntityStorageBase.php:553)

d7_field_formatter_settings returns

[warning] Entity view mode "node." could not be loaded
[warning] Entity view mode "comment." could not be loaded

Unsure if that's also related...

huzooka’s picture

huzooka
Primary language Hungarian
Location Hungary 🇭🇺🇪🇺
commented

The entity view mode issue is an another one - try to find out which field formatter view mode triggers that message… Maybe the source was using Display Suite? Or Entity View Modes?

quietone’s picture

quietone commented
Issue tags: -migrate +migrate-d7-d8

Just updating tags,

Version: 9.5.x-dev » 10.1.x-dev

Drupal 9.5.0-beta2 and Drupal 10.0.0-beta2 were released on September 29, 2022, which means new developments and disruptive changes should now be targeted for the 10.1.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 10.1.x-dev » 11.x-dev

Drupal core is moving towards using a “main” branch. As an interim step, a new 11.x branch has been opened, as Drupal.org infrastructure cannot currently fully support a branch named main. New developments and disruptive changes should now be targeted for the 11.x branch, which currently accepts only minor-version allowed changes. For more information, see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

quietone’s picture

quietone commented
Status: Needs work » Postponed

The Migrate Drupal Module was approved for removal in #3371229: [Policy] Migrate Drupal and Migrate Drupal UI after Drupal 7 EOL.

This is Postponed. The status is set according to two policies. The Remove a core extension and move it to a contributed project and the Extensions approved for removal policies.

The deprecation work is in #3522602: [meta] Tasks to remove Migrate Drupal module and the removal work in #3522602: [meta] Tasks to remove Migrate Drupal module.

Migrate Drupal will not be moved to a contributed project. It will be removed from core after the Drupal 12.x branch is open.

Version: 11.x-dev » main

Drupal core is now using the main branch as the primary development branch. New developments and disruptive changes should now be targeted to the main branch.

Read more in the announcement.

quietone’s picture

quietone commented
Status: Postponed » Closed (won't fix)

The Migrate Drupal Module and Migrate Drupal UI are deprecated and they are not in Drupal 12.0.0.

Issues for these modules should now be on the 11.x branch. And the changes are limited to critical and major bug fixes. Other changes are allowed at the discretion of the core Release Managers in consultation with the Migrate subsystem maintainers.

Now that this issue is closed, review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, credit people who helped resolve this issue.