Using a single-hierarchy container, the subcategories and pages all have flat generated URL paths... for example

container -> mycat1 -> mysubcat1 -> page

this would result in:

mycat1     node/##
mysubcat  node/##
page      node/##

instead of what i wanted:

mycat1                   node/##
mycat1/mysubcat1         node/##
mycat1/mysubcat1/page    node/##

with categorypathfirst, I get aliases like:

[categorypathfirst]._0  node/34
[categorypathfirst]._1  node/35

Anyone else getting results similar to these?

Comments

macunni’s picture

macunni commented
Version: 4.7.x-1.x-dev » master

I'm also running into the same issue. I even tried the latest cvs version.

I've just started going through this issues list and realized I'm also experiencing many of the other issues raised by Ramdak. The biggest aggrevation for me at the moment though is this path_auto feature as you described.

I'm excited about the potential for this module and hope Jaza can/will continue its development.

Jaza: should I submit an issue even though I know someone has already raised it (like this one)? I don't see this as value added but I will if you'd like --- thanks.

etterra’s picture

etterra commented

I run into the exact same problem.. i also tried the newest cvs version but it didn't help.

Besides that it seems that some nodes are not being autopathed... when i run the script some nodes stay regular "node/231" and don't get pathauto.

looking forward to this... this is the ultimate power feature when this once works!

venkat-rk’s picture

venkat-rk commented

etterra, you are right. The latest fixes (category module downloaded just today) to category_pathauto don't seem to work. I have posted followups with screenshots in the original thread.

May be we should continue the discussion there as requested by Jaza?

Jaza’s picture

Jaza commented
Status: Active » Closed (duplicate)

Yep, I think returning to the original thread - http://drupal.org/node/70640 - would be a good idea. thanks.