Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.The default selection (blank) for sublevels has the 'all' functionality, but in terms of user experience, it would be better to say ... just like the top level selector.
Comments
Comment #1
wim leersBetter to say what? I think d.o's HTML cleanup filter filtered away your word :)
Comment #2
pingers commentedlol, so it has... sorry.
<all>was the replaced word.Do you understand what i mean?
Basically, from the top level selector you can choose "all" terms.
When you select a top level term, a blank selector pops out. I think this blank selector should say "all" instead of being left blank. Functionality is identical (all nodes with the parent term).
It just makes more sense to a user this way.
Comment #3
wim leersThis is how I understand your request:
- you have the "save lineage" setting enabled
- you don't have any level labels set
- when you select a term, a new blank level (due to lack of a level label) appears. Instead of a blank level, you want an "all" option.
While I do understand what you mean, this is technically not feasible:
- the
<all>option is only available to the Views Taxonomy implementation of HS because Views has a special**ALL**option. This is what the<all>maps to.- making the
<all>option available to all HS implementations in the manner you describe, will result in bad scalability (e.g. use the<all>option at the second level, while there are 10k terms in the third level, I'm sure you can see how this can become problematic).For small hierarchies, your proposal makes sense. But it won't scale.
Note: that's also why I made it so that when the
<all>option is selected, the dropbox disappears (did you notice that already?). Essentially, the<all>is just a single option like any other, and it's implemented only for Views Taxonomy (see the source code, look for**ALL**), which is why it was possible to do this in the first place.Leaving this issue open for your response, but I probably will won't fix this issue.
Comment #4
pingers commentedBasically I mean to map
<all>to nothing... just a re-labelling of the blank selector that appears at the top of the next slide out level.Yes, this is only related to views... leaving the blank selected in the next level has the same effect as selecting all of those terms, so I think it should be labelled so for usability :)
I don't mean anything as complicated as actually querying all terms :)
Cheers,
Michael
Comment #5
wim leersWell, for an exposed filter it *can* make sense indeed. But then you can just enter
<all>as the level label for each level any way ;) :)So I'm definitely not going to hard-code this. Won't fixing this issue as it's not really an issue at all :)
Comment #6
pingers commentedAh, see, I hadn't played with level labels :)
Thanks for the hint ;)