Hey,

I just installed my features which are currently having the langcode "de" for germany within my website which is currently having the default language set to german.
In the backend I added "english" as a second language and enabled the config translation module. Afterwards I translated some fields from german to english and recreated my features.
I now would have excepted that it does it the same way as config export is doing it, so that is creates a new translation folder next to the config files which contain the translations.

But I was wrong, after recreating the feature, no translation folder got created and the translation did not get added to the feature. Am I missing something?

Cheers
Sebastian

CommentFileSizeAuthor
#6 features_export-config-translation-2869336-2.patch1.36 KBandrewsizz
#3 features_export-config-translation-2869336.patch1.23 KBandrewsizz

Comments

sgurlt created an issue. See original summary.

nedjo’s picture

nedjo
he/him/his
Primary language English
commented

no translation folder got created and the translation did not get added to the feature.

This is not yet supported. Patches welcome.

andrewsizz’s picture

andrewsizz commented
StatusFileSize
new features_export-config-translation-2869336.patch1.23 KB

Hey, just added draft patch to make it working. So, when user select some configs on UI, to feature will be also added translations of configs which user select.

But for full support of config translations functionality we need to added support of config collections in module, as config translations implemented via config collections. Right now features works only with default collection. I think we need even change UI to have possiblity to chose configs from all existing config collections.

andrewsizz’s picture

andrewsizz commented
Status: Active » Needs review

Status: Needs review » Needs work

The last submitted patch, 3: features_export-config-translation-2869336.patch, failed testing.

andrewsizz’s picture

andrewsizz commented
Status: Needs work » Needs review
StatusFileSize
new features_export-config-translation-2869336-2.patch1.36 KB

Added check if collection array not empty. Restart test

rwam’s picture

rwam commented

Hi @AndrewsizZ,

patch #6 works fine to create the translated config files. But the opposite way isn't yet supported. Neither drush fd my_feature nor drush fim my_feature have any effects. Changes will be ignored and cannot imported at the moment ;( I think, you are right with

But for full support of config translations functionality we need to added support of config collections in module, as config translations implemented via config collections. Right now features works only with default collection. I think we need even change UI to have possiblity to chose configs from all existing config collections.

I would like to have this feature too because of building an increasing amount of multilingual sites based on Drupal 8 and features.

Ciao
Ralf

rwam’s picture

rwam commented
Status: Needs review » Needs work
letrotteur’s picture

letrotteur commented

This is a must-have for features and multilingual sites.

nedjo’s picture

nedjo
he/him/his
Primary language English
commented
Status: Needs work » Closed (duplicate)
Related issues: +#2795473: Support non-default configuration collections, including language

@AndrewsizZ

Thanks for the draft patch.

But for full support of config translations functionality we need to added support of config collections in module, as config translations implemented via config collections.

Yes. Apologies for not remembering when I commented earlier in this issue that we have an open issue, #2795473: Support non-default configuration collections, including language. Rather than adding hard coded support for language, we indeed need generic support for custom config collections (including language).

Closing this issue in favour of that earlier one.