I have created a view and activated the taxonomy menu with menu path: "hierarchy".
Base Path for Hierarchy Path:category
The menu appears correctly but content doesn´t show up (no titel just empty node).

The parameters of the view:
Arguments:
- Term-ID
- no validation
- Allow multiple terms per argument: checked

Fields:
- Node titel
- Taxonomy term

No filters, no other stuff

Page path: category/%

(I have also tried category/%/%/% just to see what happens - funny)

So what to do? Any solution without php hooks, screws or nails?

Comments

indytechcook’s picture

indytechcook commented

It sends the arguments vid/tid/tid/tid... but I haven't gotten a view to work with it correctly.

ksc’s picture

ksc commented

I tested VID/TID/TID too.

In views one can choose multiple argument for term-id.
It says: "If selected, users can enter multiple arguments in the form of 1+2+3 (for OR) or 1,2,3 (for AND)."
In the live view it works with + or ,

So how do you pass the argument? It is the end of the url-path VID/TID/TID/.. or?
Which would meant that the Hierachy Path doesn´t work with individual views because / is not a valid separator.
You could create a third type of Menu Path: custom/user defined: the name category can be choosen and the rest will be category/VID/TID. Which wouldn´t produce nice breadcrumps, I guess :-(

Klaus

ksc’s picture

ksc commented

So what could be a solution here?
In version 6.x-1 every vocabulary can have its own view. People who use this will get problems when updating.

So one suggestion is:
You could create a third type of Menu Path: custom/user defined: the name category can be choosen and the rest will be category/VID/TID.

Thanks, Klaus

indytechcook’s picture

indytechcook commented

Does anyone use a different view per vocab?

in 6.x-1, the views required the argument of $tid. This is still true using the default path in 6.x-2. If they don't have any custom coding, then the upgrade path is to use the default path, and use the default taxonomy view or set their view's page display path to 'taxonomy/term/%'.

The hierarchy path is there not only to support any past custom coding, but also to show and example of how to use the taxonomy menu api. It's more for developers and not at end users.

Basically, don't use it unless you are going to use a custom module.

ksc’s picture

ksc commented

Hey Neil,
sorry, maybe I´m confused with using views or overlocking a way to manage my problem.

I have nodes linked to a vocabulary that contains pictures and I want to display thumbnails in the view.
Other nodes with another vocabulary have a date field that I want to display.
For another vocabulary I would integrate filters within the views.
All of these vocabularies are hirarchical - hence the use of taxonomy menu would be of great help.

So how can I do this with taxonomy menu using default path? Doesn´t the path "taxonomy/term/%" with only $tid as argument means that I can have only one view for all vocabularies?

Wouldn´t it be neccessary to have a path like taxomomy/term/vid/tid ... or "category"/tid to have an own view for each vocabulary?

Thanks, Klaus

indytechcook’s picture

indytechcook commented

I see your point. I have an idea how to do this with a custom module but you are starting to convince me to put the menu call back handling in taxonomy menu. This would basically solve most of your issues. I'll add it to the next beta release (next few days).

indytechcook’s picture

indytechcook commented

The latest DEV version has a new type of path "Custom View." This allows you to specify a base path for the URL. The URL will be 'category'/$tid. Just set the view path to 'category' and use a argument of TID. I also added a depth argument at the end.

I will add documentation for this tomorrow.

ksc’s picture

ksc commented

Many thanks, Neil
I´ll test it tonight.

indytechcook’s picture

indytechcook commented
Status: Active » Closed (fixed)

Klaus is now using the custom path to accomplish what he needs #393814: Wrong path for Custom view