The Needs Review Queue Bot → tested this issue. It either no longer applies to Drupal core, or fails the Drupal core commit checks. Therefore, this issue status is now "Needs work".
Apart from a re-roll or rebase, this issue may need more work to address feedback in the issue or MR comments. To progress an issue, incorporate this feedback as part of the process of updating the issue. This helps other contributors to know what is outstanding.
Consult the Drupal Contributor Guide → to find step-by-step guides for working with issues.
- last update
over 1 year ago Custom Commands Failed - 🇺🇸United States Greg Boggs Portland Oregon
This patch only works with the following conditions:
1. You set your content language the same as your Interface language. So, you have to translate both the admin interface and the content. If your users have a different language for the admin interface, this patch doesn't work for them.
2. If a content type does not have translation enabled, this patch does not work and it should. Even if a node is not translatable, it still has a valid path in each language and that path should be used to prevent an untranslated node from switching a user's chosen language.
- 🇺🇸United States Greg Boggs Portland Oregon
Here's a patch of the latest work in the MR
- 🇧🇪Belgium fernly
Patch based on latest MR version against Drupal 11.1.7. The MR still needs to be targeted to 11.x.
- 🇮🇳India shabana.navas
The patch in #57 🐛 The language of content entities incorrectly falls back to the default language of the content whilst ignoring the current language of the user Needs work had a copy/paste error. Re-rolling it with the fix.