Language » Detection and selection

Created on 7 February 2023, almost 2 years ago
Updated 30 August 2023, about 1 year ago

Drupal Version

* Drupal version » 9.5.2
* PHP version » 8.1.14
* Drush version » 11.4.0

Domain module version

* "drupal/domain": "^1.0@beta"

Expected Behavior

* That the module respects the content language.

Actual Behavior

* Module respects the interface language.

Steps to reproduce

* /en/admin/config/regional/language/detection
* Enable "Customize Content language detection to differ from Interface text language detection settings"
* Change the order in "Content language detection", so another language is displayed when logged of or when ur visiting in inkognito mode.
* If you try to load the configuration now you will notice that it will load the language based on the interface language which is wrong.

🐛 Bug report
Status

Needs work

Version

2.0

Component

- Domain Config

Created by

🇩🇪Germany eugen zerr

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

Comments & Activities

  • Issue created by @eugen zerr
  • @eugen-zerr opened merge request.
  • Issue was unassigned.
  • Status changed to Needs review almost 2 years ago
  • Status changed to Needs work almost 2 years ago
  • 🇺🇸United States agentrickard Georgia (US)

    This patch seems very specific to the stated configuration steps and I have concerns that it would break other configurations.

    It definitely needs a test.

    Questions that need to be answered:

    1. Why is the current user status relevant here?
    2. Can we even distinguish between "interface" and "content" configurations when the two are different?

    As far as I understand, interface changes should be limited to string translations, not actual config differences that affect behavior of the application.

Production build 0.71.5 2024