Hi,
We have a multilingual website who use the taxonomy.
So we have many problems to translate the paths for each vocabulary terms.
For information we use a vocabulary in translation mode.
(Different terms will be allowed for each language and they can be translated).
We have translated the vocabulary name.
When we create a term with a different language (like french) the assigned language for the generated alias is always the "language none" (und)...
The first problem come with the path alias, because it's the same path for all languages.
ex: [mon-terme - taxonomy/term/2 - All] instead: [mon-terme - taxonomy/term/2- French]
In this case the path would be normaly available in french but with own problem it's available for all language.
The second problem come when you use the patche who allow to have a vocabulary path pattern for each language.
see : Support localized taxonomy (i18n)
Like the language is always "und". The path pattern used to generate the path is always the default pattern for all paths... The pattern for the right language is simply... ommitted.
Comments
Comment #1
Echofive commentedI think that I've the solution...
The problem come from the pathauto_entity_language who return (in own case) always a undefined language...
Own patch fix it like this:
Comment #2
Echofive commentedSorry,
Bad patch name...
Comment #3
blackandcode commentedDear Echofive I tried this patch but It stil don't work.
Also I think this issue is duplicate of https://drupal.org/node/290421
Comment #4
Echofive commentedHi blackandcode,
Thanks for your remark and your testing.
Did you remember what's wrong...
Comment #5
dmaciej commented(pathauto v1.2)
I've written a patch for that and it works for me so far.
In pathauto.module you must find the line:
and replace it with the following code:
I don't have a time to creating .patch file now.
Comment #6
dmaciej commentedOkay, I've completed the patch for the issue finally. I tested it and works pretty cool.
I created a issue on the i18n project issue list https://drupal.org/node/2098975
Comment #7
dmaciej commentedTests with i18n taxonomy disabled and some fix...
Comment #8
SebCorbin commentedTestbot enabled?
Comment #10
xpasi commentedTried the patch, but it now says it generated 2497 aliases, instead of the 240 it should of and paths in other languages than the interface is set to are not generated at all.
Comment #11
niels de ruijter commented7: i18n-i18n-taxonomy-and-pathauto-2098975-2.patch queued for re-testing.
Comment #13
Carl Johan commentedI just submitted a tiny patch for i18n that fixes this problem for me.
Comment #14
jose reyero commentedCommitted the i18n side fix (#13) give it a try.
Comment #15
mmncs commentedWe have a multilanguage site where we use translated taxonomy terms, that is: localize:
Localize. Terms are common for all languages, but their name and description may be localized.
But when we create a new node the path is created using the current langauge instead of the node language. This means that we get english terms as path even though the node is in danish. We would like the path to be generated using the node language and not the user language and would like to know if any of these patches fixes this?
We are using the latest dev version.
Thanks for your time.
Comment #18
quicksketchLet's consolidate this with #290421: pathauto patch to provide localized and entity translated taxonomy through i18n. We've got at least 4 issues covering the same thing (several with patches). That issue has the most traction and working patch. If you'd like to get this in, review that patch. And although this issue is a "bug" and that one is a "feature", it would solve this issue.