It would be nice to be able to select the author-name in categories and be able to set how many term levels down pathauto should go before doing it's thing, or how many down to do it's thing on, but not all.
Perhaps it's a matter of being able to choose the behavior of pathauto for individual Vocabularies if you want.
I'm not too sure of my nomenclature when it comes to talking about taxonomies, to be honest, i'm learning more about them with pathauto than i have before.
I'll explain what i'm doing and perhaps my ignorance will become clear.
I have acidfree installed, but i don't want pathauto to generate a category url alias based on the user's first/primary album name (a term that acidfree automatically creates when my users login, ie., "John's Album"), but rather pathauto should use their username (ie., "John") instead and then alias everything below their primary album name (ie., "John/album-name-1"). I'm using (or attempting to use) the acidfree initial album (always a primary term in it's vocabulary) as an album container that won't have any loose images directly in it, but each of those terms will contain 1 or many sub-terms that are albums containing images.
This way i can have a url alias like "www.example.com/albums/john/going-out-to-dinner", but the node breadcrumb remains "John's Albums-->Going out to dinner".
This would be my use, although i can imagine it being useful at other times.
All without a lot of fussing in the urlalias settings or remembering to make a change in my template files (although i never touch them and when i do it takes me hours to remember what and where i did it, i'm the perfect dummy user.)
----
i'm really happy with the fixes and updates to pathauto. i'm pretty ignorant when it comes to coding, but the new changes, the info on using raw and the much much more predictable nature of pathauto is extremely appreciated. i don't hesitate at all to delete and regenerate aliases.
i'm ecstatic that this module got some serious attention.
| Comment | File | Size | Author |
|---|---|---|---|
| #3 | pathauto_categories.png | 54.7 KB | greggles |
Comments
Comment #1
gregglesThis seems reasonable to me. Something like [termpath:2-10] would build a termpath starting at the second term in the hierarchy and going down as far as the 10th. That's the goal of your request, right?
Unfortunately this will require some more code in the token module. There is plenty of discussion going on about that, but no actual work (and its not a priority for me).
eaton and fago are the two people who are working on that right now.
Comment #2
messenger commentedthanks greggles
that is exactly what i would be liking, though being able to select aliasing path options on a per Vocabulary basis would also solve some of my currently annoying (and confusing to users) path consistency issues across the node and category pauthauto aliasing options.
I'll head over to the token module and do a little reading, don't know squat about it other than i had to install it :)
many thanks for your clarifying response.
Comment #3
gregglesThe concept of a [vocab:fruit] token is in the token issue queue and also postponed until the Token2 work - http://drupal.org/node/185446
Is that what you mean?
Otherwise, there should already by a pattern box for each of the vocabularies that allows you to "select aliasing path options on a per Vocabulary basis".
Attached screenshot shows the area where you have the "aliasing path options on a per vocabularly basis" right?
Comment #4
messenger commentedyes the pattern box is there.
"Otherwise, there should already by a pattern box for each of the vocabularies that allows you to "select aliasing path options on a per Vocabulary basis".
- - - - - -
you hit on where i haven't understood my own problems yet - there may be several resulting from my own misunderstandings and taxonomy or pathauto limitations.
I think what i am also asking for is to be able to select which vocabulary to use as the primary vocabulary in creation of a pattern for a node that has several vocabularies assigned to it and then possibly let a secondary vocabulary (perhaps a freetagging one) follow in the pattern, or even choose to not alias certain categories and instead re-route or forward them elsewhere.
i think i'm finding a problem in how aliases are created in acidfree dependiing on whether you mass import within an album or uploading to album as category using image.module. but i am still fiddling to see if it's me.
many thanks for your time
Comment #5
dave reidFeature requests are bumped to 7.x-1.x/6.x-2.x now. 6.x-1.x is feature frozen.
Comment #6
dave reidComment #7
blaiz commentedSubscribe. Very interested in this feature.
I have many activities taking place in different cities. Instead of having something like domain.com/name of activity/name of city/sub categories, I would like something like domain.com/name of city/name of activity/sub categories, put I have to put each activity in different vocabulary because each activity is also a different content type and a different part of the website.
Thanks
Comment #8
dave reidAfter three years, it's time to won't fix this one since it's not appropriate for Pathauto.