- Issue created by @markwittens
- 🇩🇰Denmark ressa Copenhagen
Thanks for reporting, I am just going to connect these issues, so cross pollination can happen between them.
- 🇮🇳India bmahesh03121
I was able to reproduce this after spending a lot of time, and also the related issue queues are very long to digest. but based on my understanding the contrib module https://www.drupal.org/project/advanced_language_negotiation → should help you while issue fix gets released; please add your findings as well if possible
- 🇳🇿New Zealand quietone
Changes are made on on 11.x (our main development branch) first, and are then back ported as needed according to the Core change policies → .
Restoring template. The issue template is used to track progress and various tasks on an issue.
- 🇳🇱Netherlands markwittens
Installation of https://www.drupal.org/project/advanced_language_negotiation → doesn't change anything, and results in multiple errors and warnings when trying to configure the module.
I created an issue with my findings there ( https://www.drupal.org/project/advanced_language_negotiation/issues/3518106 🐛 Several errors and warnings Active ).
- 🇧🇪Belgium swentel
Related with #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 → - when you go to admin/content, the edit links will also point the other domain instead of using the "Content language detection" query param. It's so frustrating to no be able to decently configure this for webmasters/admin users!