I'm trying to use the menu items of parents as the automatically generated path by using [node:menu-link:parents:join:/]/[node:title].

I have removed forward slashes from being stripped in the punctuation settings.

The issue I'm having is that my top level item has its path set manually, rather than being generated by pathauto.

If this page's title is foo, but it's path is set to bar, when I add a child of this page, the path is /foo/baz, not /bar/baz as expected.

Is this intentional? It seems that pathauto is figuring out what the path *would* be if it were automatically generated, rather than what it actually is.



kiwimind’s picture

Version: 7.x-1.0 » 7.x-1.1

Further to this issue, this does not only apply to manually set menu paths.

I have a page that has a page title of foo, an automatically generated path of foo, but a menu title of bar. When I create a new page, baz, and use the pattern of [node:menu-link:parents:join:/]/[node:title], I would expect to see the url for baz to be /foo/baz.

What's happening instead is that the path is /bar/baz, so the pattern seems to be picking up on the menu title, rather than the actual path.

Any ideas what is causing this?

caschbre’s picture

I'm experiencing the same issue and haven't been able to track down a solution.

Either we're using the wrong token and there isn't a token for parent path.
Or the token is using the wrong values (menu title vs node title).

I'm guessing it's that we simply don't have a token for parent path or parent(s) path(s).

Dave Reid’s picture

Maybe you're looking for [node:menu-link:parent:url:path] ?

caschbre’s picture

Maybe you're looking for [node:menu-link:parent:url:path] ?

That's exactly what I'm looking for and saw you mention that in another issue. Thanks!!

I went back and looked through the replacement tokens listed at admin/config/search/path/patterns and that token is not listed as a replacement option. The token does what I expect it to... so is it not being listed a separate issue?