OK - the issue is limited to the case where the parent and child languages do not match.

So, given the token from the OP, "[node:menu-link:parent:url:path]/[node:title]", we have (at least) three distinct cases:

Case 1, parent is language-neutral:
* Parent Node is "Language Neutral", alias "language-neutral-alias", and $nid 123
* Child Node has language "English" and title "English Node"
* generated alias will be "nid/123/english-node" instead of "language-neutral-alias/english-node"

Case 2, parent and child have mis-matched languages:
* Parent Node has language "English", alias "english-alias", and $nid 123
* Child Node has language "French" and title "Le Node Francais"
* generated alias will be "nid/123/le-node-francais" instead of "english-alias/le-node-francais"

Case 3, parent has a language assigned, but child is language neutral:
* Parent Node has language "English", alias "english-alias", and $nid 123
* Child Node is "Language Neutral" and title "Neutral Node"
* generated alias will be "nid/123/neutral-node" instead of "english-alias/neutral-node"

In case 1, where the parent is language-neutral, it seems intuitive that the child's url alias should use the language-neutral alias, rather than falling back on the system path.
In cases 2 and 3, I'm not actually sure how this should be resolved.

thoughts?
is this behavior documented somewhere and i'm re-treading old ground?
Seems like this could be an issue for other language-dependent tokens, though this is the first one i've run into in my short time developing a multi-language site.

Comments

AaronBauman’s picture

edit: updating OP description

AaronBauman’s picture

Title: [node:menu-link:parent:url:path] fails for 3+ level url aliases » unexpected results for menu-based tokens when parent and child aliases' languages do not match.
AaronBauman’s picture

Issue summary: View changes

wholly-separate issue than originally reported