Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.Update after testing version released on May 18 @ 12:08.
1. Installed pathauto and changed settings for default node path patterns in order to test.
2. Tried various combinations of settings for different types of nodes. (e.g. [catpath]/[title], [type]/[title], [title])
3. Performed a bulk update of node paths
Expected results:
All nodes would be aliased according to the node path settings.
Actual results:
Node path setting of [catpath]/[title] does not appear to work. In my testing, all nodes were categorized but when aliased, the category term did not show up. So instead of sitename.com/category/node_title, the alias generated was sitename.com/node_title. Other combinations appear to be working correctly as far as I can tell.
Comments
Comment #1
gregglesYep, I'm definitely seeing this problem as well. Thanks for finding/reporting it!
Comment #2
David N commentedUpdate after testing version released on May 20.
1. Installed pathauto and changed settings for default node path patterns in order to test.
2. Tried various combinations of settings for different types of nodes. (e.g. [catpath]/[title], [type]/[title], [title])
3. Performed a bulk update of node paths
Expected results:
All nodes would be aliased according to the node path settings.
Actual results:
Node path setting of [catpath]/[title] now works. However, it only works when bulk updating nodes that already exist. If I submit a new node, the URL generated for the node is still sitename.com/node_title.
I'm not sure whether I should submit a new issue or not, as my memory's a bit hazy, but if I recall correctly, shouldn't the default node path setting NOT require an input? In other words, if I use pathauto, am I required to alias every node from that point on, or should I still be able to only generate URL aliases for certain types of nodes going forward? I ask because the module doesn't generate node aliases unless I enter some sort of setting for the default. If I do that, I can go ahead and set any combination of settings for node paths.
Comment #3
gregglesCould you perhaps try again?
I just tried with a node that had multiple hierarchy and freetagging and it worked fine.
If it doesn't work for you please let me know more precisely what kind of vocabulary settings you have.
Comment #4
gregglesThis works in testing again today (using the current 5.x-2.x-dev) so I assume it's been fixed somewhere along the way.
I also couldn't duplicate the behavior of node patterns only working if the default one is set.