Language Independence of Features not respected

Created on 2 October 2018, about 6 years ago
Updated 19 March 2024, 8 months ago

Hi there,

I'm using features to re-use functionality on a multi-site (3 separate sites), 2 of those sites are not multilingual, however the default language is set to en-AU. The 3rd site is multilingual and its default language is set to en.

When I generate a feature, it seems to take the default language of the site its being generated from and use that for the langcode of each config it changes. As a result, some of the config files for a feature have langcode en-AU, while other files have en depending on which site I was working on when I re-generated the feature. This is strange as I have set content_translation.enabled: false and language_alterable: false.

In fact, I'm not sure why any language settings are being exported as I have selected for "Language" and "Content Language Settings" to be excluded.

See the attached screenshots for clarification.

My desired behaviour is that the features are completely independent of language but receive the desired functionality.

💬 Support request
Status

Active

Version

3.7

Component

Generation Plugins

Created by

achap 🇦🇺

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

  • 🇨🇦Canada arakwar

    We have the same challenge here, some of our sites have a different base language from our "source" site.

    But a clarification needs to be made here : The "Language" option enabled here is about Language configurations, not the langcode in config files.

    So the site will exclude any Language config, so if one of your config requires the "language.en" config, it won't be part of the feature export.

    I'm still trying to figure out how to handle the langcode difference.

Production build 0.71.5 2024