- Issue created by @arakwar
Hi,
We're trying to use Features to handle a set of configuration that we want to share between websites. We're facing one issue though, where Features built on an English-based website are exported with their langoce set as "en" (as expected), but Features then imports this setting on a website, even if it's installed in a different language (let's say French).
This behavior isn't a bug per itself, this is what you'd expect from the current configuration mangement of Drupal. But it does limit us in our project.
Since your module seems to make it a LOT easier for a site to fetch a set of config in a specific language, I'd like to explore the possibility of using it to add a functionality to Features where we'd be able to export our feature in English with a translated config in French, but then on import if we detect that the target website is in French, we flip the imported config to this language.
There's a flaw in this as if we have English as a second language on the second website, we'd still have issues with translations... but in our case having to set English as the default if it exists isn't an issue.
I'm opening a support request here to start the discussion, but my guess is that it would be either a change request on Features, or an extra module that binds into Features to make this work. I may be wrong, or other people may have a better idea.
Active
1.0
Code