Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.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
| Comment | File | Size | Author |
|---|---|---|---|
| #7 | 1283024-translate-7.patch | 3.39 KB | webflo |
| #6 | 1283024-translate-6.patch | 1.56 KB | webflo |
| #1 | 1283024-translate.patch | 1.98 KB | dawehner |
Comments
Comment #1
dawehnerComment #2
dawehnerI'm wondering why this issue doesn't have "needs review", let's mark it and get some more reports.
Comment #3
cjoy CreditAttribution: cjoy commentedI 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.
Comment #4
cjoy CreditAttribution: cjoy commentedproblem 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.
Comment #5
Cyberwolf CreditAttribution: Cyberwolf commentedAlternative patch in #824696: taxonomy translation makes original name (before translation) unavailable.
Comment #6
webflo CreditAttribution: webflo commentedComment #7
webflo CreditAttribution: webflo commentedCommit d5ff98a on 7.x-3.x. Thanks!