Problem/Motivation

I expect that after executing Drupal 7 migrations from a (multilingual) Drupal 7 site where the default language is not English, the migrated configuration entities and content entities have the appropriate language code. But this is not what I got.

The biggest issue is that a config (or content) entity with language: en will contain non-english words (so you cannot translate them to English if you want to do it later).

On the other hand, having default configs with mixed language is a maintenance/development nightmare.

Steps to reproduce

Try to migrate a Drupal 7 instance with a default language other than English.

Proposed resolution

Migrations with config or content entity destination should depend on "default_language" migration (as an optional dependency).

Remaining tasks

User interface changes

API changes

Data model changes

Release notes snippet

Comments

huzooka created an issue. See original summary.

huzooka’s picture

huzooka
Primary language Hungarian
Location Hungary 🇭🇺🇪🇺
commented
Priority: Normal » Major
Issue tags: +migrate-d6-d7
wim leers’s picture

wim leers
Location Ghent 🇧🇪🇪🇺
commented
Status: Active » Postponed (maintainer needs more info)

Can you update the issue summary to show the concrete error messages you're encountering? 🙏

Version: 9.2.x-dev » 9.3.x-dev

Drupal 9.2.0-alpha1 will be released the week of May 3, 2021, which means new developments and disruptive changes should now be targeted for the 9.3.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

wim leers’s picture

wim leers
Location Ghent 🇧🇪🇪🇺
commented

Now that #3189463: all translation/localization migrations should depend on the 'language' migration landed, this is likely almost always implicitly already the case.

This issue would make that dependency explicit, so probably still worth doing. But probably no longer Major? 🤔

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

Drupal 9.3.0-rc1 was released on November 26, 2021, which means new developments and disruptive changes should now be targeted for the 9.4.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

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.

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.

kristen pol’s picture

kristen pol
she/her
Primary language English
Location Santa Cruz, CA, USA
commented
Issue tags: +Bug Smash Initiative, +Needs steps to reproduce

As part of the Bug Smash Initiative, we are triaging issues that are marked "Postponed (maintainer needs more info)". This issue was marked "Postponed (maintainer needs more info)" almost a year and a half ago and there has been no activity here since that time.

Per #5, bumping down to normal. Also tagging for more explicit steps to reproduce including the error message per #5.

Since we need more information to move forward with this issue, I am keeping the status at Postponed (maintainer needs more info). If we don't receive additional information to help with the issue, it may be closed after three months.

Thanks!

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.

kristen pol’s picture

kristen pol
she/her
Primary language English
Location Santa Cruz, CA, USA
commented
Status: Postponed (maintainer needs more info) » Closed (cannot reproduce)

As part of the Bug Smash Initiative, we are triaging issues that are marked "Postponed (maintainer needs more info)". This issue was marked "Postponed (maintainer needs more info)" more than 2 years ago.

Since there was no additional information provided since it was requested last year, I'm marking the issue "Closed (cannot reproduce)". If anyone can provide complete steps to reproduce the issue (starting from "Install Drupal core"), document those steps in the issue summary and set the issue status back to "Active" [or "Needs Work" if it has a patch, etc.].

Thanks!

quietone’s picture

quietone commented
Assigned: Unassigned » quietone
Status: Closed (cannot reproduce) » Active

I am not so sure about closing this. The Issue Summary makes sense and core does not test with a site that has a default language other than English. And if the result is a site where you can translate content, that is a problem.

I would like to find time to test this. Assigning to myself.

quietone’s picture

quietone commented
Status: Active » Closed (cannot reproduce)
Issue tags: -migrate content, -migrate configuration, -migrate-d6-d7

I did some limited testing on this with a D7 site, installed in Italian with a translated node and translated config (content type). After migrating I didn't have any error messages or trouble translating the content. But again, my testing and source was limited.

I do to agree with @Wim Leers and @Kristen Pol that steps to reproduce are needed here. And sample database would help as well. However, since it has been 3 years since the first request for more information, and none has been supplied, I am changing the status as per #11.

quietone’s picture

quietone commented
Assigned: quietone » Unassigned