I assigned this ticked as a bug, but please change the category if I'm wrong:
I created a custom module with the config translation. (finding tutorials is not easy)
So, I've a custom admin form (class ConfigFormBase) which contain a RichText (WYSIWYG Field).
The text will be displayed in the footer.
I can translate the field without problems (mysite.com/de/admin/mymodule/translate/fr/edit) <-- I add a french translation.
After save the translation form, I navigate to the french site and the translated text is shown correctly.
So, until this point the config translation works fine.
I want export now (drush cex -y) this translation with drush, but drush say:
<em>$boss:</em> <strong>drush cex -y</strong>
The active configuration is identical to the configuration in the export directory
When I visit the config sync UI de/admin/config/development/configuration, i see changes for the language collection.
At this point, in my opinion, the configuration should be exportable.
When I import, drush cim drush will import effectively the language collection/config file. (This is an absolute correct behavior.)
If I change another setting (like an field label, add a new tax. vocabulary) and export the config (drush cex -y), the configuration for the translated language can now be exported.
Short version:
- I add/edit a config translation and this is not exportable. But importable, which reset my changes.
- When I change another setting, example a Field label and export this. The language collection file can be exported.
Why I can't export the config translation «alone». I noticed this behavior in the drupal core too. (I translated the user mail under de/admin/config/people/accounts/translate)
I can't imagine that I am the only one to notice the behavior, but I didn't find any other issues and comments with google search.
This way, I've no idea if I'm wrong?
Is this related with the translation override and I only don't get in?