- Issue created by @secretsayan
We are in a multisite site setup with same codebase catering to multiple sites with different databases and observing that status of config splits are different in `admin/config/development/configuration` and `admin/config/development/configuration/config-split` after upgrading config_split from 1.x to 2.x and upgrading config_ignore from 2.x to 3.x.
We have the below versions to start with -
Config Split : 1.9.0 -- Config Ignore: 2.4.0 -- Config Filter: 1.12
1. We have a split configured with only the devel module selected in it.
2. Now we did, composer require drupal/config_split:^2 and composer require drupal/config_ignore:^3
3. Then we did, drush @site1 updb , we observe that everything is working fine at this point, and `admin/config/development/configuration` and `admin/config/development/configuration/config-split` are showing the same splits as enabled. The upgrade is successful and everything is fine.
4. Now we export the config to use in other sites, so we go to our split and check no_patching to true and save and then drush @site1 cex
5. Then we move to our second site to upgrade it to config_split 2.x, and at this point its codebase has config_split 2.x and config_ignore 3.x from step 2 above , so we do drush @site2 updb
6. When we navigate to `admin/config/development/configuration/config-split` we find that all splits have been upgraded as expected and are showing as active. But when we go and navigate to `admin/config/development/configuration` and see all splits are disabled and it says You are not using any config split configuration. . This is unexpected and probably a bug.
7. Then we do, drush @site2 cim and it says no changes to import.
When we navigate to `admin/config/development/configuration` and `admin/config/development/configuration/config-split` it should both show similar splits as enabled.
We are not sure if we are doing something wrong here. Any help will be highly appreciated.
Active
2.0
Code