Taxonomy term translation on not translated nodes

Created on 30 July 2019, over 5 years ago
Updated 23 June 2024, 6 months ago

Greetings,

As I found out that there is possible bug or conflict in language selection of taxonomies on nodes.


Summary of the problem:


Taxonomies are shown as depend on orginal langauge of node (if it don't have translated version of the node) when it should be another langauge.


Steps


-Create a taxonomy vocabulary with 3 languages with allowed translation.
English | French | Turkish
Hello | Bonjour | Merhaba
House | Maison | Ev 

-Create a node type with allowed to translation (Name of the content type: "testing", field name "taxonomy").
-You may translate field's name or other details. (french version "taxonomie", turkish version "taxonomi" ). We choose interface language to display.
-Add a field with term references

-Create a new content, name it "a new content" in Turkish. Lets choose "Merhaba" in "taxonomy" field. Its node number is "5".

-Open this new node example.com/tr/node/5 (default langauge of site is English )
You may see as
taxonomi: Merhaba
-Now use URL as example.com/fr/node/5
you should see
taxonomie: Bonjour
However it appears as
taxonomie: Merhaba
in example.com/node/5, English langauge
taxonomy: Merhaba

If you create translated version of "a new content" as French, example.com/fr/node/5 url will show you as correct one.

taxonomie: Bonjour
But still English would be (example.com/node/5)
taxonomy: Merhaba

The need of the problem is even if user didn't translate the content, taxonomies should appear in correct form, like its field names.

Note: I am not really sure it is a dublicate problem but as I searched in last 2 days, I only found very old examples of problem (exp:
https://www.drupal.org/forum/support/post-installation/2010-03-26/taxono... ) and another maybe more up-to-date similar one. ( https://www.drupal.org/project/drupal/issues/2930458 )

Thanks

🐛 Bug report
Status

Active

Version

11.0 🔥

Component
Taxonomy 

Last updated 1 minute ago

  • Maintained by
  • 🇺🇸United States @xjm
  • 🇬🇧United Kingdom @catch
Created by

🇹🇷Turkey Erso

Live updates comments and jobs are added and updated live.
  • Needs issue summary update

    Issue summaries save everyone time if they are kept up-to-date. See Update issue summary task instructions.

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.

  • 🇺🇸United States smustgrave

    Based on #11 this could still be an issue. Moving to active and tagging for IS and steps to reproduce

  • I can confirm that D10 as well:
    1. I have nodes that are translatable, but not localized
    2. I manage language via session
    3. Opening node in non-localized language all labels are translated, but taxonomy field itself is no.

  • 🇮🇹Italy apaderno Brescia, 🇮🇹
  • I attached image to describe issue better:
    1. Node is not translatable, but not localized, ie only id default language
    2. Reviewing node by forcing language in URL or managing it via session results in same: label translated to target language, but fields with taxonomy reference displayed in default language, but not URL/Session language.

    Would be happy to pay for the fix if anyone would be intersted.

Production build 0.71.5 2024