Rendered HTML Output doesnt respect activeLanguage completely

Same, patch from #39 solves the issue — Thanks!
We had the problem, that the UI translations were rendered in the language negotiated by Drupal --> so always German.

Reroll the MR and make a patch for it.

I'm just doing some light work related to #3190024: Problem with test dependencies when testing issue forks → .

@fjgarlin: Thanks a lot for your work on that!
However, please do such work in 📌 (Try to) fix the GitLab CI RTBC in the future, it’s quite unrelated to this ticket.

@drunken-monkey 100% you’re right, apologies. I was meant to undo the changes but totally forgot. My bad.

I arrived at this issue following the related ones and just wanted to prove something (which I did) in the related issues.

I’ll undo my commits Monday first thing (away from computer right now).

My changes are now reverted.

#3380219-2: Rendering is not changing the current content and string translation language → is a duplicate that contains a patch with a different approach, not needing a new service class (which I’d count as a big plus). Please try it out and see whether this doesn’t also resolve this problem for you.

In either case, though, we still need a regression test for this.

I created a new branch with the patch from 🐛 Rendering is not changing the current content and string translation language Closed: duplicate that doesn't create a new service. I haven't been able to figure out how to write a test for it though.

bgreco → changed the visibility of the branch 3035977-change-language-existing-services to hidden.

After some additional testing, I've found that the approach in this issue (creating a new language negotiator) works better than the approach from 🐛 Rendering is not changing the current content and string translation language Closed: duplicate .

The patch from the other issue fixes config and string translations, but entity references are still rendered in the request language. (Specifically - in layout builder, non-translatable custom blocks that reference translatable entities.) The branch from this issue is more complete and fixes all three - config, string, and entity translations.

Uploading a static patch of the MR:

Re-based MR and uploading a static patch.

Sorry about the noise, I just wanted to remove two modules from composer.json, which I think should not be there, and failed ...

Just a tip that I managed to get it to work in Search API Solr, and how to:

• Index translated labels in rendered content using the patch in 🐛 Rendering is not changing the current content and string translation language Closed: duplicate
• Set up "Language (with fallback)" correctly in a View

I have posted more details in the other issue, and updated the MR.

ressa → changed the visibility of the branch 3035977-rendered-html-v2 to hidden.

GitLab is not doing so well in this issue, it looks like it's stuck, and can't create a new branch with the latest code ...

Anyway, I was wrong about my previous comment, the patch in this issue works. I mixed up the two patches (I thought that 2.patch was in fact 237...)

I am attaching an updated patch.

I think this patch may be a bit closer to match dev.

Just an observation: The default language in my installation is English (under /en), with Danish as the other language, without language prefix (under /) like this:

1. Add Danish language in an existing English installation
2. Open "URL language detection configuration" (/admin/config/regional/language/detection/url)
3. Update "English (en) path prefix (Default language)" to en
4. Remove da under "Danish" and click Save
5. Get message about "The prefix may only be left blank for the selected detection fallback language → ."
6. Open link in new window and set "Language" to Danish
7. Go back to "URL language detection configuration" which can now be saved

The default language is now Danish at example.com (English is under example.com/en) and I get the text "Velkommen!" on the front page.

From Use URL language detection configuration? →

It mostly works, but sometimes, the system somehow gets stuck in its old ways, and only English labels get indexed ... I tried many things like clearing cache, rebuilding Solr index, etc., but this is what seems to work:

Open the edit form for a node under Danish (/node/259/edit), and see English translated field names. If I then clear caches, Drupal "wakes up" and realizes there is a default language (/en), but the fallback language in the current page is Danish. The fields are now rendered in Danish, and now, when I index, the correct translated field labels are used in the rendered HTML fields, in the Solr index content.