If you have two taxonomy term fields one with the original name and one with the translated name
the original names got overridden in the result.

Here is a patch to fix this

CommentFileSizeAuthor
#7 1283024-translate-7.patch3.39 KBwebflo
#6 1283024-translate-6.patch1.56 KBwebflo
#1 1283024-translate.patch1.98 KBdawehner

Comments

dawehner’s picture

dawehner
Primary language German
commented
StatusFileSize
new 1283024-translate.patch1.98 KB
dawehner’s picture

dawehner
Primary language German
commented
Status: Active » Needs review

I'm wondering why this issue doesn't have "needs review", let's mark it and get some more reports.

cjoy’s picture

cjoy commented

I am not sure if it would be useful (beyond my current usecase) to have the option of "term:name (translated, if available)" too, but it seems common practice in many places to fall back to default when no tranlation is available.

cjoy’s picture

cjoy commented
Status: Needs review » Needs work

problem with fallback / default language:

as pointed out above,
term:name:translated field is empty when using the default language or when the term is not trasnlated for the current language.

this can be solved using the token [name] in the "no results behavior" replacement.
BUT, that content is ignored when using the "rewrite result" behavior to output the term as a link.

cyberwolf’s picture

cyberwolf commented

Alternative patch in #824696: taxonomy translation makes original name (before translation) unavailable.

webflo’s picture

webflo commented
StatusFileSize
new 1283024-translate-6.patch1.56 KB
webflo’s picture

webflo commented
Status: Needs work » Fixed
StatusFileSize
new 1283024-translate-7.patch3.39 KB

Commit d5ff98a on 7.x-3.x. Thanks!

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.