Hi,
I have searched issues and read through the documentation more than once and I must be missing something. I want to setup a custom view, which I thought I could use custom path with, however when I do this method, I'm able to configure the views and everything works great, but the paths aren't using the path alias.
Therefore what I'm getting is:
category/tid/tid
rather than:
category/fashion/women
Am I missing something, or is this not supported in the latest dev version? I know path alias works properly with default views, however as I said I wanted to setup a custom view that is different then other vocabularies.
Thank you.
Comments
Comment #1
indytechcook commentedYou are not missing anything. Path Auto is only setup to use the standard taxonomy path aliases so anything custom is not available at this time. This is a feature that I have been wanting to add but haven't gotten it on a official list yet. So I'm changing the issue to a feature request for custom path auto support.
Comment #2
indytechcook commentedComment #3
indytechcook commentedChanging the title to better reflect the request.
Comment #4
indytechcook commentedSetting to Active.
Comment #5
zarudnyi commentedHi,
I'm not sure that is right place for post my issue, so please forgive me if I did something wrong ;)
That module is very helpfull but I can't start it work in way that I need.
I have some hierarchy in my taxonomy vocabulary like that:
Cars (term aliase catalog/cars)
-- BMW (term aliase catalog/cars/bmw)
-- Mercedes Benz (term aliase catalog/cars/mercedes-benz)
I create view with path catalog/% and an argument Term ID with the option Allow multiple terms per argument.
After setup views i create taxonomy menu and enable the option Use term name.
Taxonomy menu was generated and all looks fine but path for second level terms is wrong and don't reflects hierarchy, please look:
Cars (term aliase catalog/cars)
-- BMW (term aliase catalog/bmw)
-- Mercedes Benz (term aliase catalog/mercedes-benz)
Based on the foregoing, I have two questions:
1. What i missing?
2. Why menu items for second level has wrong aliase?
I'll be glad of any assistance.
Thank You.
Comment #6
undersound3 commentedI am not an expert on this but I think you either have to:
change your custom path to catalog/cars in admin/content/taxonomy/edit/vocabulary/yourvid
or try changing the path in Pathauto.
./admin/build/path/pathauto -> Catalog path settings
set path to catalog/cars/[catpath-raw]
Comment #7
zarudnyi commentedThanks for reply
Main thing is what cars that term too...
@indytechcook any progress here? Default and Vocabulary menu path types works fine and return right path for menu item, but I need custom views for different vocabularies and now I can't get it with right hierarchy path.
Comment #8
indytechcook commentedMoving to version 3. This really isn't that hard, I just didn't have time to put it against version 2.
Comment #9
zarudnyi commentedThank you for your attention to this issue.
Comment #10
undersound3 commentedComment #11
Andrew Gorokhovets commentedIt would be remarkable!
Comment #12
devkinetic commentedI'm using the the "Vocabulary path" and wanted to clean the term name of special characters. This is a slightly different take on pathauto integration.
I merged in the "use term name" option from custom path fapi, as well as as the foreach that was replacing spaces with dashes:
Then using the available module hooks in a custom module I added the code below. You can use this yourself by just doing a find/replace on "mw_site" which was the name of my custom module. You can see where I've replaced the strtolower(str_replace()) with pathauto_cleanstring(). I feel this is an overall better solution, as it allows you to use a custom path as well as implement pathauto functionality
In my use case, these urls point to a view using taxonomy redirect. In order for the view to be able to understand these urls (views won't without the spaces and special characters), set the arg to term id and write a hook_views_pre_build to convert the term names to tid and vid respectively.
If you did it right, you will see your new type in the dropdown on a taxonomy edit screen.
Comment #13
mazzPlease read my replies here: http://drupal.org/node/903774#comment-3475058 they deal with the issue and how I handled it when integrating with ubercart. To solve my issue I created a module to automatically populate pathauto catalog aliases.
Please note that even with this the beginning of your path still needs to be "catalog/" from within pathauto. Read the above posts to see why this is.
Comment #14
NickWebman commentedi'm hosed without this! Need something like whatever/[term]/[term2]
Comment #15
jonaswouters commentedsubscribing
Comment #16
dstolPostponing for the time being.
Comment #17
undersound3 commentedsubscribing
Comment #18
dstolThere will be no more work on the 6.x-3.x-dev branch for the foreseeable future.