10.2.6
2.0.0-beta1
Using a configuration translation form should get and save values for the selected language.
Configuration translation forms use values from the default site language when editing translations. Translations do not save.
drush si, and default settings.composer install drupal/domain.drush en config_translation domain_config_ui language./admin/config/regional/language and add Spanish as a second language./admin/config/domain and configure two domain records./admin/config/system/site-information and configure a site title for all domains and languages. (Note that this is the Domain Configuration UI and is working as expected!)/admin/config/system/site-information/translate and edit the Spanish translation. The values for English are displayed and will not save for Spanish.Perhaps this is not a valid use case. However, be aware that some modules do not expose all configuration values in the main form. These must be edited from the configuration translation form for that module. For example, see the External Links → module:
composer require drupal/extlink.drush en extlink./admin/config/user-interface/extlink, enable domain configuration, and save values for each domain./admin/config/user-interface/extlink/translate and try to add a Spanish translation. The values are not retrieved or saved.I didn't get far with Xdebug, but my first suspect is DomainConfigOverrider. Here the language manager was returning the site default language for me, rather than the actual language of the request.
Active
2.0
- Domain Config
I'm not sure how common this issue is actually. I looked more into the External Link module and opened an issue 🐛 Add fields for alternative text labels to settings form Active which should expose the fields we need without needing to use the configuration translation form. However, it would be neat if Domain Config UI were more compatible with, or more explicit about its incompatibility, with the core Configuration Translation module.