I have and old site where there are three languages installed: English, German and Dutch. Dutch is the default one.
When i do the migration to my new drupal 8 site the default langcode is switched from English to Dutch as per the default_langcode migration.

The problem is that when i do the rollback (both default_langcode and language) the default language stays on Dutch but the language rollback tries to remove it resulting in an exception and a stuck language migration that i have to keep reseting in order to continue with my work.

I am trying to get the default_langcode migration rollback to work but i see no way to find out what was the default language on the new site prior to the migrations.

Is this even doable?

Comments

MaskOta created an issue. See original summary.

Version: 8.5.x-dev » 8.6.x-dev

Drupal 8.5.0-alpha1 will be released the week of January 17, 2018, which means new developments and disruptive changes should now be targeted against the 8.6.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.6.x-dev » 8.7.x-dev

Drupal 8.6.0-alpha1 will be released the week of July 16, 2018, which means new developments and disruptive changes should now be targeted against the 8.7.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

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

Drupal 8.7.0-alpha1 will be released the week of March 11, 2019, which means new developments and disruptive changes should now be targeted against the 8.8.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

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

Drupal 8.8.0-alpha1 will be released the week of October 14th, 2019, which means new developments and disruptive changes should now be targeted against the 8.9.x-dev branch. (Any changes to 8.9.x will also be committed to 9.0.x in preparation for Drupal 9’s release, but some changes like significant feature additions will be deferred to 9.1.x.). 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.1.x-dev

Drupal 8.9.0-beta1 was released on March 20, 2020. 8.9.x is the final, long-term support (LTS) minor release of Drupal 8, which means new developments and disruptive changes should now 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: 9.1.x-dev » 9.2.x-dev

Drupal 9.1.0-alpha1 will be released the week of October 19, 2020, which means new developments and disruptive changes should now be targeted for the 9.2.x-dev branch. For more information see the Drupal 9 minor version schedule and the Allowed changes during the Drupal 9 release cycle.

quietone’s picture

quietone commented
Category: Task » Support request
Status: Active » Closed (works as designed)

@MaskOta, thanks for creating an issue about the rollback of languages.

What you have discovered is correct, the rollback of configuration migrations do not 'reset' configuration values to the value it had before the migration. That isn't information the migration knows about.

Just tried it myself and after `drush mr default_language` I had to manually change the default language back to the original (en) before `drush mim language` would work. By your description you destination site also has a default language of english. So, that could be restored manually. Or one could restart from a fresh empty database. And since the language migrations run early that is certainly an option.

There isn't anything to fix here, this is working as designed.

Changing to support request and closing as works as designed.