Not sure if this is user error or not, but thought I'd submit it and see if any others were seeing the same behavior. In the Pathauto admin menu under category path settings, the default path pattern that applies to all vocabularies with blank patterns is category/[vocab]/[catpath]. I've been trying to set different path settings for different categories, as I want to have my categories for some nodes be /[catpath] for example, and have free tags be /[vocab]/[catpath].

It seems that I'm not able to have different settings for different categories, as one path pattern overrides another. In my case, as soon as I put in /[catpath], /[vocab]/[catpath] fails to take effect. If I keep /[vocab]/[catpath] as the only option, then the aliases are created correctly for free tagging terms, but I'd like to be able to differentiate between categories and free tagging terms by having different alias structures.

Comments

greggles’s picture

greggles
he/him
Primary language English
Location Denver, Colorado, USA
commented

The behavior I see is:

1. Install pathauto and either leave the default settings for "Default path pattern" or change them.
2. Create a taxonomy "test taxonomy"
3. Create terms in the taxonomy
4. Aliases are created using the default format
5. Edit the pathauto settings so that your "test taxonomy" terms will get a special alias format
6. Create a term in the "test taxonomy"

Expect results:
The term is aliased using the pattern set in step 5.

Actual results:
The term is aliased using the "Default path pattern" pattern (whether it is the original one the module uses or a new one.

So, yes I can confirm :) Thanks for reporting this problem.

Note that this format is the best way to report a bug so that it's easy to repeat. Prose is just harder to follow exactly what happened.

David N’s picture

David N commented

Ah, sorry! I will keep that in mind when reporting bugs going forward.

greggles’s picture

greggles
he/him
Primary language English
Location Denver, Colorado, USA
commented

Reassigning.

greggles’s picture

greggles
he/him
Primary language English
Location Denver, Colorado, USA
commented
Status: Active » Fixed

That last message was a total mistake - whoops.

That said, I just commited a fix for this. It will take a few hours for it to get rolled into the tarball.

David N’s picture

David N commented

Update after testing version released on May 18 @ 12:08.

1. Installed pathauto and changed settings for default path patterns for categories in order to test.
2. Used setting of [catpath] for default and [vocab]/[catpath] for one category (free tags, in my case)
3. Performed a bulk update of category paths

Expected results:

All terms would be aliased according to the path settings, and users would be able to have different settings for categories instead of being locked into the default setting.

Actual results:

There still seems to be an issue with creating aliases for forums and adding a "0" to the end, but that's another issue. Having more than one path pattern for categories seems to work ok for the most part, but I can never get it to generate aliases for all the terms that use a non-default setting the first time I run the bulk update. If I run it again right after, then everything seems ok. I've been able to repeat this pattern multiple times by uninstalling the module and starting over from scratch.

So in other words, my vocab terms all end up like term1-0, term2-0, term3-0 when using one type of path pattern ([catpath]) while others I try to alias using another pattern ([vocab]/[catpath]) end up ok, but only after more than one attempt at a bulk update. One sidenote: Forum aliases are still being created for the terms that don't use a default path pattern setting, in addition to the correct aliases.

greggles’s picture

greggles
he/him
Primary language English
Location Denver, Colorado, USA
commented

Note that the bulk update behavior has changed pretty drastically - see http://drupal.org/node/142762 and http://drupal.org/node/67665

I also had a thinko in my fix of http://drupal.org/node/140333 which I think has now been fixed. Can you please redo your tests with the bulk update changes in mind and after the forum fix gets re-rolled into a tarball?

Also, the problems you described in #5 seem quite different from the original problem. Can you confirm that the original problem is fixed? Any new problems (even if related) should be described/tracked in new tickets.

David N’s picture

David N commented

Thank you; I will definitely keep an eye out for the latest tarball.

With each round of testing, I did indeed start from a clean slate by deleting all URL aliases before performing a bulk update.

I would say that yes, the original problem of not being able to use more than one category path setting is fixed. I will go ahead and resubmit a new issue for the part about non-default category path settings not working on the first try.

Anonymous’s picture

(not verified) commented
Status: Fixed » Closed (fixed)