Closed (outdated)
Project:
Taxonomy Term Reference Tree Widget
Version:
7.x-1.9
Component:
Code
Priority:
Major
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
8 Feb 2012 at 18:35 UTC
Updated:
2 Dec 2025 at 14:57 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
bartk commentedAdded a translation support patch.
Comment #2
al.ex commentedI've had the same issue with a vocabulary that contains terms in different languages. This patch solved it for me.
Comment #3
tondeuse commentedThis worked fine for me, oddly, I am not sur I was really working tih version 7.x-1.6, but I was easilly able to manually add the 2 lines required in the module file for this patch to work. Thanks a lot!
Is it me or this issue still isn't fixed for the current .9 version of the module, as this comment points out?
http://drupal.org/node/1514794#comment-5994850
I am using the term reference tree widget with a vocabulary for which the translation mode is 'Translate. Different terms will be allowed for each language and they can be translated.', an important nuance to mention.
Comment #4
KLicheR commentedThe problem still here in version 1.9.
The patch (-p0) of #2 still work.
Comment #5
pmusaraj commentedI have created a new patch for this that applies. It loads only the terms with the current node's language on node/edit screens, and the terms with the interface language on the node/add screen.
(This is only useful for translated terms. Localized terms work fine. This shouldn't break it for localized terms, but adds an unnecessary node_load.)
Comment #6
angel.hI created a patch for this issue which uses not the interface language or the node language but the language of the entity.
Comment #7
dave reidAll the trailing whitespace and coding standards have been fixed, so this needs to be re-rolled.
Comment #8
vladimirausThank you everyone for your contribution.
Drupal 7 is no longer supported but we always need support for Drupal 11 version.
Closing as outdated.