Using only Session language negotiation method makes it impossible to edit content other than the current session language

Created on 22 March 2023, over 1 year ago
Updated 10 November 2023, 8 months ago

Problem/Motivation

This was reported in another long running issue but not fixed. Opening a new issue as it got lost in the noise. When you enable only the Session language negotiation plugin and try to edit a nodeโ€™s translation itโ€™s impossible to go to that translation page by clicking the edit buttons. You are always redirected to the current language because the node urls are the same. The only way to get there is by adding a query parameter to the current node edit form with the desired language to edit and reloading the page. This will get you there but now your session language is updated everywhere.

Steps to reproduce

Create two languages and create a translation of a node. Enable only the Session language negotiation plugin in the interface translation section. Go to the original language node and set your session language by filling in the language query parameter with your default language. Now try and edit translation of the node. Itโ€™s impossible to get to the edit form.

Proposed resolution

You should be able to edit the translation without having to change the session language.

Remaining tasks

N/A

User interface changes

N/A

API changes

N/A

Data model changes

N/A

Release notes snippet

N/A

๐Ÿ› Bug report
Status

Active

Version

9.5

Component
Language systemย  โ†’

Last updated about 19 hours ago

  • Maintained by
  • ๐Ÿ‡ฉ๐Ÿ‡ชGermany @sun
Created by

achap ๐Ÿ‡ฆ๐Ÿ‡บ

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

Comments & Activities

  • Issue created by @achap
  • achap ๐Ÿ‡ฆ๐Ÿ‡บ

    One workaround to this is to create your own plugin similar to the Session one that returns NULL in the getLancode method if it's an admin path and then falls back to either the URL plugin or the Content Language plugin. This at least makes nodes editable in other languages. But the Session plugin should handle it on its own.

  • ๐Ÿ‡ฎ๐Ÿ‡ณIndia nitesh624 Ranchi, India

    Hi @achap is there any patch or code snippet available which solves the issue?

Production build 0.69.0 2024