When working in a multilingual context per default the interface translation is enabled. Leading to the following implications:
After enabling language negotiation, not only on the default Interface but also on the Content, creates problems. IMHO the purpose to have this distinction is to have a backend in one language and the actual content/frontend in an other.
Is the language negotiation enabled for content three consequences appear:
From the Drupal backend there is little information on the implications of the distinction between `Account administration pages` and `user` detection.
If both are enabled on `/admin/config/regional/language/detection` the user profile page will show two drop downs.
This is said to influence the communication with the user and his/her account information. Meaning something like content original language.
No hint to the Interface.
This one is clearly the "Account administration pages language setting". Is it? because when enabled, the frontend Content language will always default to this setting. Even showing a `404` for other paths! At this point I am unsure, if this is a bug.
But furthermore, in addition to the `user` setting this generates a couple of strange behaviors with e.g. three languages:
This is seriously misleading, since a simple user (with the permissions given) could configure his/her own profile like this!
- #2830033
- #2313309
- #2189267
Active
11.0 🔥
Issue summaries save everyone time if they are kept up-to-date. See Update issue summary task instructions.
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
An anonymous bird sent me this patch, he/she/they/other wishes to stay anonymous.
I expect test failures with this patch as it's changing the behavior of core in a way that makes sense to many but is different to the current behavior of core.