Contrib.social

ossible integration with Features

Open on Drupal.org →
Created on 19 March 2024, about 1 year ago

Problem/Motivation

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.

Proposed resolution

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.

✨ Feature request
Status

Active

Version

1.0

Component

Code

Created by

🇨🇦Canada arakwar

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

Comments & Activities

  • Issue created by @arakwar
  • Comment about 1 year ago →
    🇨🇦Canada arakwar
  • Status changed to Closed: works as designed 3 months ago
  • Comment 3 months ago →
    🇨🇭Switzerland florianmuellerch Aarau, Switzerland

    Hi @arakwar

    Thank you for raising the issue and for your suggestions!
    However, I do not think that this module should move in this direction for the following reasons:

    • Usage of features is actively discouraged as from their project page →
    • The problem seems to originate not even in the features module, but by your application which in my opinion is something that the features module did never consider supporting. If it should do so, it should definitely be implemented in the features module.

    If you feel otherwise, please specify your use case a bit more in detail with some config examples, so I can get a better picture of the issue. And if you could provide a patch or MR, that would be great :)

    Because of no one else participating in the discussion, I'll close this issue for the moment.

contrib.social Blog FAQ Discussions
Production build 0.71.5 2024