- 🇩🇪Germany Anybody Porta Westfalica
Same issue seems to exist for "Global" Textarea and Textfield in header and footer. That should be a separate issue, but both are highly related.
In my opinion, these should follow the rendering language setting!
In most aspects, views work great with content language (contents) vs. interface language (admin). This is for example important if you have contents on the page (e.g. chinese or russian) you can't read as administrator (e.g. English user)
For "More link" text (1), this is NOT the case. It always uses interface language (despite other views elements as it seems, which work just fine!)
I first thought the reason was a wrong configuration in (2) and tried other settings (and cleared cache), but still the same.
If using content language and having the "Rendering Language" setting (2) set to "Content language of view row" (or any other option which you'd expect to also work for the "More link text" (1)
The "More link text" (1) is always output in interface language, regardless which content language is selected or which "Rendering language" setting is set in views.
Only switching the interface language shows the correct translation!
We've configured
See above
Handle the "More link" text like all other elements in views and show it in content language, eventually based on the views "Rendering Language" setting (2) - I'm not experienced enough in the details here.
Active
11.0 🔥
Last updated
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
Same issue seems to exist for "Global" Textarea and Textfield in header and footer. That should be a separate issue, but both are highly related.
In my opinion, these should follow the rendering language setting!