When content language detection is different from interface language detection, the detected language is not applied to the rendered content

Open on Drupal.org →

Created on 5 February 2014, almost 11 years ago

Updated 11 December 2023, 11 months ago

Problem

When setting language detection method, the checkbox Customize Content language detection to differ from User interface text language detection settings is not applied, only the interface configuration.

This leads to two critical issues with translating content:

It is not possible to edit translated version of a node. All "Edit" urls on node's "Translate" tab are the same and lead to main editing form. See edit.png.
Translated content is never shown to the user. Default language is always displayed.

Steps to reproduce

On a fresh D8 install:

Enable content translation and language modules
Add another language
Set Detection and selection method to session and browser (tested both, both are broken)
Configure content type "Article" to be translatable (Administration >> Configuration >> Regional and language)
Add a node and set it's language to default one (I used article with image. All fields were filled including image)
Translate node to a second language and save.
Go to "Translate" tab and investigate "Edit" links. Both lead to the same page.
Go to the newly create node and try switching language using "session" parameter. You will still see the node in default language.
Do the same with a browser running second language (or just spoof the browser string to change language). You will still see the node in default language.

Remaining tasks

- the configuration is correctly saved
- Patch is provided

User interface changes

No changes to the UI are required for the fix.

API changes

The protected variable type which indicates whether a given type of language usage (language_content, language_interface, language_url) changes to an array to allow different types to initialize during the initialization of another.

🐛 Bug report

Status

Fixed

Version

8.7 ⚰️

Component

Language system →

Last updated 2 days ago

Maintained by
🇩🇪Germany @sun

Created by

🇵🇱Poland SiliconMind

Live updates comments and jobs are added and updated live.

D8MI
(Drupal 8 Multilingual Initiative) is the tag used by the multilingual initiative to mark core issues (and some contributed module issues). For versions other than Drupal 8, use the i18n (Internationalization) tag on issues which involve or affect multilingual / multinational support. That is preferred over Translation.

sprint

language-ui

Incomplete comments

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.

Comment over 1 year ago →
achap 🇦🇺
For the comments in #40, #42 and #67 I agree that the original idea of the issue has been forgotten about so I created a new issue to deal specifically with the fact that you can't edit a node if only session negotiation is enabled. https://www.drupal.org/project/drupal/issues/3349579 🐛 Using only Session language negotiation method makes it impossible to edit content other than the current session language Active
Comment about 1 year ago →
🇨🇿Czech Republic honyik
Had the same problem on Drupal 10.1, solved it NOT by turning off the "Account administration pages" option on the detection page, but by pushing this option further down, so my detection order is "Chosen language", "URL" and then "Account administration pages" and the translations are accessible. Just in case this helps anybody.
Comment 11 months ago →
🇨🇦Canada joseph.olstad
I haven't found a patch that fixes this.

Implementing a workaround as follows:
#2650434-174: Clearing cache via UI in translated language resets config translation of field labels to default language →
Comment 11 months ago →
🇨🇦Canada joseph.olstad
@honyik, I just noticed your suggestion, I'll try that later.
Regarding comment #127 above

contrib.social Blog FAQ Discussions

Production build 0.71.5 2024