Links from teasers switch interface language if node is not translated

Created on 27 September 2016, over 8 years ago
Updated 7 September 2024, 4 months ago

My site example.com is configured with 2 languages, Norwegian and Finnish. All nodes are written in Norwegian, and some are translated to Finnish.
The front page view is configured to include teasers from all nodes from the default language (Norwegian), that is:
* Filter: Content: Translation language (= Site's default language (Norwegian BokmΓ₯l))
and render them in the language of the selcted interface, that is:
* Rendering Language: Interface text language selected for page

The result of this is that the front page shows teasers from all nodes in Norwegian if the user has selected Norwegian as interface text language. If the user selects Finnish as his interface text, the front page shows teasers from all nodes - the ones that are translated in Finnish, and the ones that are not in Norwegian. And this is how I want example.com to work.

The problem occurs when the user now clicks on one of the titles (or read more link) of the nodes that are not translated. Because this will link to the node without the prefix for Finnish (fi), and effectively switch the interface language.

Example:
example.com/node/4 is not translated to Finnish. So visiting example.com/fi/node/4 shows the node in Norwegian, but with Finnish interface text (menu etc).
When visiting example.com/fi the user sees teasers of all nodes, the ones that are translated in Finnish, and the ones that are not in Norwegian.
Clicking on the title of node 4 takes the user to example.com/node/4 which correctly shows node 4 in Norwegian, but also swithces the interface language to Norwegian (which is undesired). I would expect the link to take the user to example.com/fi/node/4.

FYI: If adding a menu entry for this node, this menu entry behaves as I expect (in other words linking to example.com/fi/node/4 if the user has selected Finnish as interface text language)

I've tried tons of combinations of settings for the front page view, language setup, content type setup etc., but have not been able to achieve my goal. Any input on this would be highly appreciated :)

πŸ’¬ Support request
Status

Closed: works as designed

Version

11.0 πŸ”₯

Component
Views  β†’

Last updated about 5 hours ago

Created by

πŸ‡³πŸ‡΄Norway roald

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

  • πŸ‡³πŸ‡ΏNew Zealand quietone

    Three years ago a solution was given in #7. I think it is time to close this.

    The Drupal Core issue queue is not the ideal place for support requests. The 'support request' option is there for filing support issues for contributed modules and themes. There are several support options listed on our support page β†’ (Community > Support at the top of Drupal.org) and there is Drupal Slack β†’ . You may get better replies in one of those places.

Production build 0.71.5 2024