Hello, first of thank you all for this great module!

I've been trying to use this module's widget within a content type, but it looks like it's not detecting my term's language, thus showing double entries for every terms, e.g. I would see 'boat' and 'bateau' (english and french version of the same term) displayed by my term reference field.

Looking at the module's code, I couldn't find any easy way to let i18n filter my term's language, perhaps a more experimented dev could help me?

thank you and have a good day!

Comments

bartk’s picture

Status: Active » Closed (fixed)

Added a translation support patch.

al.ex’s picture

Status: Closed (fixed) » Patch (to be ported)
StatusFileSize
new915 bytes

I've had the same issue with a vocabulary that contains terms in different languages. This patch solved it for me.

tondeuse’s picture

This 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.

KLicheR’s picture

Version: 7.x-1.6 » 7.x-1.9
Priority: Normal » Major

The problem still here in version 1.9.
The patch (-p0) of #2 still work.

pmusaraj’s picture

StatusFileSize
new1.35 KB

I 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.)

angel.h’s picture

I created a patch for this issue which uses not the interface language or the node language but the language of the entity.

dave reid’s picture

Status: Patch (to be ported) » Needs work

All the trailing whitespace and coding standards have been fixed, so this needs to be re-rolled.

vladimiraus’s picture

Issue summary: View changes
Status: Needs work » Closed (outdated)

Thank you everyone for your contribution.
Drupal 7 is no longer supported but we always need support for Drupal 11 version.
Closing as outdated.

Now that this issue is closed, review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, credit people who helped resolve this issue.