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.
I've stumbled across a bug in PathAuto, whilst pathauto works accurately with translated term names, it ignores completely translated vocabulary names. For examples I use
Vocabulary: Tags
Term: About Us
Which gives the path: tags/about-us
i18n Vocabulary: Tagiau
i18n Term: Amdanom Ni
Which gives the path: tags/amdanom-ni
Now to me this seems like a design fault, if pathauto can recognise a translated term, why can it not use a translated vocabulary?
the string I'm using is [term:i18n-vocabulary]/[term:i18n-term]
Comments
Comment #1
Dave ReidWhat module are you using that provides those tokens?
Comment #2
Homotechsual CreditAttribution: Homotechsual commentedi18n/Internationalization provides the translations and therefore I presume the tokens, this may be an internationalization issue, I'm not certain.
Comment #3
Homotechsual CreditAttribution: Homotechsual commentedAny thoughts on this? If it is indeed an i18n issue I will move it onto their issue queuei
Comment #4
Dave ReidYou should probably check with i18n if they're providing the tokens - the problem relies there. If the problem is i18n's tokens don't have enough or the right data in order to work properly, then it can be moved back to Pathauto.
Comment #5
Dave ReidThis is also likely a duplicate of #290421: pathauto patch to provide localized and entity translated taxonomy through i18n.
Comment #6
Dave ReidComment #7
Homotechsual CreditAttribution: Homotechsual commentedI understand that this problem could stem from Token, Pathauto or i18n, the pathauto folks have suggested that is is more likely an issue with i18n
Comment #8
Jose Reyero CreditAttribution: Jose Reyero commentedFirst check you are using i18n-taxonomy tokens, see i18n_taxonomy.tokens.inc.
Anyway for this to work the proper language should be passed in the $options parameter. So you should check whether this is happening. If not maybe pathauto should pass the node language.
Comment #9
Jose Reyero CreditAttribution: Jose Reyero commentedDocumenting. See http://drupal.org/node/1240340
Comment #10
webflo CreditAttribution: webflo commentedComment #11
Jose Reyero CreditAttribution: Jose Reyero commentedNo follow up, so closing.
Comment #12
marcoka CreditAttribution: marcoka commentedseems related to: #290421: pathauto patch to provide localized and entity translated taxonomy through i18n
edit: already posted above.
Comment #13
marcoka CreditAttribution: marcoka commentedanother related issue: #1574628: [term:parents:join-path] not woking with multilanguage vocabualries
Comment #14
Dave ReidThere hasn't been any new information to point that this isn't a Pathauto problem, so closing again.
Comment #15
marcoka CreditAttribution: marcoka commentedi have tested it, and if you pass the $options array with the correct language, it works. so i guess a pathauto problem.
My notes and where i will post a patch. (i currently have something working).
#1587446: i18n tokens - multilanguage