In Pathauto I have a content type set to use [fullhierarchytitlepath-raw] as its path. If I create a node whose title ends in one of the "strings to remove" for Pathauto, then create children of that node, the path of the children includes an extra separator after the parent title. For instance, the path of "Test Page B", which is a child of "Test Page A" comes out as /test-page-/test-page-b (since "A" is a string removed by Pathauto). However, the path of "Test Page A" by itself is correct, with no trailing separator.

I'm not really sure whether this is a bug in Node Hierarchy or Pathauto; please move if appropriate.

Comments

ronan’s picture

ronan commented

Try using [fullhierarchypath] and let me know if it has the same issue. This is the recommended token to use as it uses the node's parent's url to build the url. This means it will respect any changes you have made to urls of nodes in the hierarchy. It might also help solve this problem.

Grantovich’s picture

Grantovich commented

Using that token does appear to solve the problem. I now no longer remember why I used [fullhierarchytitlepath-raw] in the first place, so I guess I'll just use [fullhierarchypath] instead.

ronan’s picture

ronan commented
Status: Active » Closed (fixed)