With the newest releases of PathAuto, Token and Node Hierarchy it seems that creating a root level node with node hierarchy (in other words a node with Parent set to "NONE") results in the path for that node being set to the actual token that was listed for that content type (for me, creating a root level node resulted in it having a path of "http://domain.com/%5Bfullhierarchypath%5D"). I can see why this could be intended functionality in the case where one doesn't want a node to be a part of the hierarchy, but knowing for sure would be nice.

Thanks!

Comments

ronan’s picture

ronan commented
Assigned: Unassigned » ronan

Nope, that's a bug. I'm travelling for the rest of the week but should be able to take care of this this weekend. I know I've fixed it locally, but am not sure if that's bee comitted to cvs yet. I'll check and commit as soon as I'm back.

kevbot’s picture

kevbot commented

Ah, great! It's nice to see that I'm not nuts.

Thanks!

isaac.niebeling’s picture

isaac.niebeling commented

Any progress on this? Also, is no output the intended behavior for the token when the node is at the root level?

Thanks,

Isaac

ronan’s picture

ronan commented

I have the code ready to go, I'll check it in tonight when I have a few minutes to spare.

I think for root-level nodes, fullhierarchypath should be the same as the title token, hierarchypath will be blank

R

isaac.niebeling’s picture

isaac.niebeling commented

I'm still pretty new to Drupal--will that update show up in the development snapshot when it's ready?

Thanks,

Isaac

ronan’s picture

ronan commented
Status: Active » Fixed

Yep, sometime in the next 12 hours the packaging scripts should grab the latest code from cvs and create a new dev snapshot which you can download and test. If the latest code fixes your problem let me know (and close the ticket) and I can create a new release (5.x-1.1). Or if you're impatient you can check out the end of the DRUPAL-5 branch from the cvs yourself.

Either way, let me know if this fixes the issue for you

Thanks
R

isaac.niebeling’s picture

isaac.niebeling commented
Status: Fixed » Closed (fixed)

Just checked, and it seems to have fixed my problem. Thanks!

As for the new release, would that also include the patch from #228448: Page Description (for multiple pages with the same title)? Or is that a patch I should apply separately?

Isaac

ronan’s picture

ronan commented

thanks for checking this out. As for the other patch, I have not yet committed that to cvs as I have not yet decided if that is a bug fix or a feature enhancement. I'll probably just call it a (usability) bug fix and put it in the 5.x-1.x branch, but it's not there yet.

Thanks
R

isaac.niebeling’s picture

isaac.niebeling commented

Sounds good. For what it's worth, I'm using that patch with the latest dev build (for the no-parent token fix here) and it's working great.