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.

CommentFileSizeAuthor
#7 3339990-7-language-detection.patch3.2 KBalexrayu

Issue fork domain-3339990

Command icon Show commands

Start within a Git clone of the project using the version control instructions.

Or, if you do not have SSH keys set up on git.drupalcode.org:

Comments

Eugen Zerr created an issue. See original summary.

eugen zerr’s picture

Issue summary: View changes

eugen zerr’s picture

Assigned: eugen zerr » Unassigned
Status: Active » Needs review
agentrickard’s picture

Status: Needs review » Needs work

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.

hitchshock’s picture

Version: 8.x-1.0-beta6 » 2.0.x-dev
Priority: Major » Normal
alexrayu’s picture

StatusFileSize
new3.2 KB

For those would need this patch for Drupal 11, here is the reworked version.

mably’s picture

Status: Needs work » Postponed (maintainer needs more info)

Not sure to understand what you are trying to do here.

Is the problem still present with latest 3.0.x-dev version?

Unless new, valuable information is provided, this issue will be closed in 3 months.

mably’s picture

Status: Postponed (maintainer needs more info) » Closed (cannot reproduce)
Issue tags: -language, -Context

Haven't been able to reproduce the problem locally. Closing.

Now that this issue is closed, review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, credit people who helped resolve this issue.