Situation:

We have installed Drupal (wizard) with German language. Later we have installed as additional language (under admin/config/regional/language) English. Because the customer wanted to translate some strings (override the Source string) we activate the Checkbox "Enable interface translation to English" in the English language. The main problem now, if we install now a community module like commerce and they have some configurations or views they will import the strings into our German language. So if we go into the view, we have in our "default language" German the English words. So i.e. if we change now a label or button text to German, we lost the English word. If we go then into the translation tab, add a translation for English we have now the German word and need to translate all back to English.

Steps to reproduce:

1. Install a fresh Drupal wizard with German language
2. Install a Module like Commerce
3. Add the english translation (Enable interface translation to English)
4. Try to translate a view like commerce_orders.

What behavior were you expecting?

The View is fully translatable in English

What happened instead?

The View is not fully translated.

translation

CommentFileSizeAuthor
Tranlation.png21.06 KBnicolabelleri

Comments

nicolabelleri created an issue. See original summary.

handkerchief’s picture

handkerchief
Primary language German
Location Chur, Switzerland
commented
Related issues: +#2910353: Prevent saving config entities when configuration overrides are applied
handkerchief’s picture

handkerchief
Primary language German
Location Chur, Switzerland
commented
Related issues:
handkerchief’s picture

handkerchief
Primary language German
Location Chur, Switzerland
commented
Related issues: +#2905295: Configuration language being overwritten during module install

Version: 8.8.5 » 8.8.x-dev

Core issues are now filed against the dev versions where changes will be made. Document the specific release you are using in your issue comment. More information about choosing a version.

Version: 8.8.x-dev » 8.9.x-dev

Drupal 8.8.7 was released on June 3, 2020 and is the final full bugfix release for the Drupal 8.8.x series. Drupal 8.8.x will not receive any further development aside from security fixes. Sites should prepare to update to Drupal 8.9.0 or Drupal 9.0.0 for ongoing support.

Bug reports should be targeted against the 8.9.x-dev branch from now on, and new development or disruptive changes should be targeted against the 9.1.x-dev branch. For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

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

Drupal 8 is end-of-life as of November 17, 2021. There will not be further changes made to Drupal 8. Bugfixes are now made to the 9.3.x and higher branches only. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

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

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

Drupal 9.3.15 was released on June 1st, 2022 and is the final full bugfix release for the Drupal 9.3.x series. Drupal 9.3.x will not receive any further development aside from security fixes. Drupal 9 bug reports should be targeted for the 9.4.x-dev branch from now on, and new development or disruptive changes should 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.4.x-dev » 9.5.x-dev

Drupal 9.4.9 was released on December 7, 2022 and is the final full bugfix release for the Drupal 9.4.x series. Drupal 9.4.x will not receive any further development aside from security fixes. Drupal 9 bug reports should be targeted for the 9.5.x-dev branch from now on, and new development or disruptive changes should 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: 9.5.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. For more information, see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

pameeela’s picture

pameeela commented
Status: Active » Postponed (maintainer needs more info)
Issue tags: -language, -langcode +Bug Smash Initiative
Related issues: +#2806009: Installing a module causes translations to be overwritten

Needs more specific steps to reproduce. Could this be a duplicate of #2806009: Installing a module causes translations to be overwritten?

quietone’s picture

quietone commented
Issue tags: +Needs steps to reproduce

Since we need more information to move forward with this issue, I am setting the status to 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!

smustgrave’s picture

smustgrave commented
Status: Postponed (maintainer needs more info) » Closed (outdated)

Since there has been no follow up in 6+ months going to close out. If still an issue please reopen.