Add test ensuring LanguageNegotiationContentEntity is correctly processing the query options

Created on 19 November 2015, almost 10 years ago
Updated 4 September 2025, 13 days ago

Problem/Motivation

The LanguageNegotiationContentEntity language negotiator introduced in #1810394: Site configuration with domain based language negotiation results in redirecting authenticated users to a different domain when accessing a content entity route for translation language different from the interface language β†’ is was not corectly processing the query options and if they are set it will ignore them, which might lead to incorrect outgoing urls.. This was the case until #2809789: UrlGenerator fails to urlencode aliases, incorrectly encodes "system" path β†’ got in and solved the problem.

Proposed resolution

#2809789: UrlGenerator fails to urlencode aliases, incorrectly encodes "system" path β†’ got in and solved the problem, however here we got additional tests and it would be nice to get them into the core as well.

Remaining tasks

Review the tests and commit.

User interface changes

none

API changes

none

Data model changes

none

πŸ“Œ Task
Status

Postponed: needs info

Version

11.0 πŸ”₯

Component

language system

Created by

πŸ‡©πŸ‡ͺGermany hchonov πŸ‡ͺπŸ‡ΊπŸ‡©πŸ‡ͺπŸ‡§πŸ‡¬

Live updates comments and jobs are added and updated live.
  • stale-issue-cleanup

    To track issues in the developing policy for closing stale issues, [Policy, no patch] closing older issues

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.

  • πŸ‡ΊπŸ‡ΈUnited States smustgrave

    Thank you for creating this issue to improve Drupal.

    We are working to decide if this task is still relevant to a currently supported version of Drupal. There hasn't been any discussion here for over 8 years which suggests that this has either been implemented or is no longer relevant. Your thoughts on this will allow a decision to be made.

    Since we need more information to move forward with this issue, the status is now Postponed (maintainer needs more info). If we don't receive additional information to help with the issue, it may be closed after three months.

    Thanks!

Production build 0.71.5 2024