The 2026 Drupal Business Survey is open. Your response will help shape the future of the Drupal business ecosystem.Hi Wim,
For a specific taxonomy vocabulary (containing 10 or so terms), the users on my site normally select 7 or 8 of them... This is a lot to add via the drop box (especially because I have them selecting only the deepest level).
To help the user, I'd like to add a "select all" button, which would ideally add all the deepest terms to the HS dropbox. Then they could then just 'Remove' the few terms they don't want from the Dropbox.
Ideally this would be an option when editing the vocabulary. Maybe this option could appear when 'Dropbox settings' is enabled (like you already do with 'Limit the number of selections'). This option could say something like like "Select all: let users add all terms from this vocabulary to the dropbox: Enabled / Disabled".
I'm wondering the best way to accomplish this, to be compatible with the 6.x port of HS that's currently under development. Do you have any advice?
* Also, where is the best place to add feature requests until a 6.x-3.x-dev is added to the CVS?
* For now I added this to the issue queue as a feature request (under 5.x-3.x-dev for now), because a feature request seems out of place in the 6.x port issue, even though I assume all new features will go in the 6.x branch? Is this correct?
;) Scott
Comments
Comment #1
wim leersI won't do this, because it's an inherent scalability issue. Actually, I removed the very ability to do this from version 3, it existed in version 2.
Let me clarify. When you have 10 items, it's nice to have an "all" option. When you've got a 100, you've got yourself a usability issue. When you've got a 1000, you've got a scalability issue.
To be fair, you're suggesting this on a per-level scale. But still, I don't like this.
This is the reason that the "Reset selection of hierarchical select" setting has been added. Set that setting to "disabled" and that will increase the user experience.
However, I did notice your comment on the D6 port issue, stating that this very setting fails when enforce_deepest has been enabled. I've changed the issue to a bug report for that problem.
Regarding your 2 questions: all features go into 5.x-3.x dev AND will be ported to D6. For now, at least. This has been the policy for the past months, but will soon come to an end, because a final for D5 will soon be released and at that point, a 6.x-3.x-dev release will be created. From then on, all new features will go to the D6 version and the D5 version will no longer get new features.
Comment #2
wim leersIt works just fine for me… in Drupal 5 *and* Drupal 6. Don't discuss the Drupal 6 port here though.
This is what it looks like/how it works, and it's behaving correctly: screencast.
Please mark as active again if you think this issue should not be closed.