Hi,
i don't understand if the feature is missing or i'm wrong (i use D7 and Views3).

I don't find "Hierarchical Select" in "Selection type" of "Content: Has taxonomy term" in Views3's exposed filters.
I've only 1 possible drop down selection list with option "show the hierarchical in the list", but the result is 1 select drop down.

I would 2 hierarchical select drop down in my view.

Is it possible??

thanks
bye

Comments

nikonvulcano’s picture

nikonvulcano commented

any suggestions?

nikonvulcano’s picture

nikonvulcano commented

No one answers here?

Perrogato’s picture

Perrogato commented

Hi, I have the same problem. I am using version 7.15 of drupal, and I two version of HS. The HS don't appear in any filter of Taxonomy.

pog21’s picture

pog21 commented

Same problem here:
Drupal 7.14, views 7.x-3.3
The view is of type: User.
Hierarchical select is used in a field added to profiles.
The field can be used as an exposed filter, but offers no option for HS.

nikonvulcano’s picture

nikonvulcano commented

I did other tests, but without success. Does anyone have any idea?

nikonvulcano’s picture

nikonvulcano commented

no one wants to suggest a solution?

rafinskipg’s picture

rafinskipg commented

I think that is not implemented, look at the issue queue searching "Views" http://drupal.org/project/issues/hierarchical_select?text=views&status=A...

kars-t’s picture

kars-t commented
Priority: Major » Normal
Status: Active » Fixed

Dear fellow Drupal enthusiasts,

this issue is now lasting for a very long time in the issue queue and was unfortunately never solved. As Drupal is a open source project everyone is helping on voluntary basis. So that this is was not solved is nothing personal and means no harm. But perhaps no one had time to deal with this issue, maybe it is too complex or did not describe the problem comprehensibly.

But this issue is not the only one. There are thousands of issues on Drupal.org that have never been worked on or could not be processed. This means that we are building a wave that is unmanageable and just a problem for the Drupal project as a whole. Please help us keep the issue queue smaller and more manageable.

Please read again, "Making an issue report" and see if you can improve the issue. Test the problem with the current Core and modules. Maybe the problem doesn't exist anymore, is a duplicate or has even been solved within this issue but never closed.

Help can also be found for it on IRC and in the user groups.

In order to remove this issue, I have set this issue to "fixed"

If there is new information, please re-open the issue.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.