Hi everyone
There is a major issue with site name changing through configuration manager in multilingual site.
The scope considered:
- Use Drupal installation built with English language for a multilingual purpose
- Use another language as default language and provide consistent experience across all pages in terms of original language
- Make all configuration management per language
- Ability to utilize UI capability for site management and administration
- Drupal translate system should take into account current or built configuration (original configuration) as default configuration.
Drupal basic settings (system.site) configuration would break UI capability by modifying the langcode of the configuration file. By changing the langcode no longer the UI has the capability to change the site name. The site name would not change from the UI but rather directly with configuration synchronization.
It seems that the backend system removes the file related to the original configuration and the new langcode modification and import are not taken into account. In this manner the configuration integrity is broken, no longer changing the strings from UI is possible.
If you revert back to the default langcode here is en, it would not be any help, and issue persist.
Configuration synchronization from the UI perspective and backend yaml files are respected differently. in the UI only a file is shown with no respect to language but in the backend and sync config folder 3 version of file exist. One in en language, one in es language and one in the sync root.
A capability should be added to Drupal system to make configuration adjustment per language.
Active
11.0 🔥
Last updated
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
