- Issue created by @joachim
In a multilingual site, when module is enabled, configuration is updated.
This causes LOTS of configuration updates that are unrelated to the module being updated.
Should this happen when the language is being changed?
Step 1: enable a language. Config export says:
[notice] Differences of the active config to the export directory:
+------------+----------------------+-----------+
| Collection | Config | Operation |
+------------+----------------------+-----------+
| | language.entity.de | Create |
| | language.entity.und | Update |
| | language.entity.zxx | Update |
| | language.negotiation | Update |
+------------+----------------------+-----------+
Step 2: Make the new language the site default. Config export says:
[notice] Differences of the active config to the export directory:
+------------+----------------------+-----------+
| Collection | Config | Operation |
+------------+----------------------+-----------+
| | system.site | Update |
| | language.negotiation | Update |
+------------+----------------------+-----------+
Step 3: Enable a module. Config export says:
[notice] Differences of the active config to the export directory:
+-------------+------------------------------------------------------+-----------+
| Collection | Config | Operation |
+-------------+------------------------------------------------------+-----------+
| | block_content.type.basic | Update |
| | block.block.claro_secondary_local_tasks | Update |
| | block.block.claro_primary_local_tasks | Update |
SNIP -- EVERYTHING got updated!!!!
Active
11.0 π₯