Closed (won't fix)
Project:
Hierarchical Select
Version:
6.x-3.x-dev
Component:
Code - Taxonomy Views
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
29 Nov 2009 at 10:31 UTC
Updated:
22 Jan 2012 at 03:47 UTC
Jump to comment: Most recent file
Comments
Comment #1
jrao commentedRepost to get <Any> displayed properly:
Not sure if I'm understanding this correctly, but if my HS views filter setting has enforce_deepest = False, then the Level Labels are displayed and they serve the same purpose as <Any> option. In this case, <Any> option is unnecessary and should be removed, otherwise it's impossible to have the filter default to <Any> option (if it's removed, we can use Level Label to create an <Any> label for default, but if <Any> is not removed, we'll have two <Any>'s if we use this trick), which is how the regular taxonomy views filter will behave.
Comment #2
wim leersI don't understand at all. So please make a screencast of:
That makes it easier for me to reproduce the problem. Thanks!
P.S.: don't have any screencast software yet? On Windows and Mac OS X, you can use the free Jing.
Comment #3
jrao commentedOk, Jing doesn't like my display setup, so I have to use normal screen capture, please check attached zip:
location vocabulary.jpg: I have a vocabulary called Location which has states and cities in a 2 level hierarchy, it is applied to a content type called Video
location terms.jpg: Terms in the vocabulary
filter setting.jpg: I have a view for listing Video contents, I added a HS taxonomy filter to this view, this is the filter setting
filter setting hs.jpg: Here's the HS setting for the filter, dropbox is also disabled
views filter.jpg: The filter looks like this in views preview, the problem is both State and <Any> are displayed in the dropdown, they serve the same purpose, so the <Any> here is not necessary and should be removed, so that admin can just change State to <Any>
Comment #4
wim leersThe is special and required by Views when the exposed filter is optional. I understand what you're saying though. I welcome a patch but won't add this one myself (due to time constraints) — it's a very small nuisance. I'm pretty sure you won't be implementing this either, so unfortunately I'm won't fixing this.
Comment #5
benone commentedSubscribe.
If somebodoy could create a patch for this issue, would be great.
Thanks.
Comment #6
jsimonis commentedI agree. It would be nice to turn this off.
We have a block in the sidebar, which means we can't set the filter to be required. Doing so brings up a big red message about the field being required on every single page on the site.
There should be an option to remove that if you have a label for that level since the label acts the same way.
Comment #7
adityamenon commentedHi, I'm having this exact 'nuisance', as Mr. Leers rightly put it.
If anyone can point me in the right direction, even with very generic pseudocode / code locations, I will fix this. I simply cannot have it, that I cannot switch this off or at least change the text for the
<any>label. But I am quite frightened to wade into the code without any direction, because of time constraints I have - in addition, not the least, due to the fact that I am somewhat new to Drupal coding.jrao, did you notice, that the Level Labels do not seem to have the same functionality as
<any>? Choosing a Level Label and clicking appply will not do anything but redirect to the same page you are on. Choosing<any>however, will bring you back to the unfiltered results. So I would actually love to remove all the labels and change the text of<any>from within my module, but I don't really know how to do that because HS does not appear to work with FAPI (I remember Mr. Leers writing something somewhere about FAPI being too complex).