The "none" option.

Hm, you're right about the labels. In my use cases this wasn't necessary yet, but it's of course something that should be supported.

And indeed, "all" and "none" are currently not available. You always have to select something. That's "by design" currently. That's something I'd like to change too.

Patches are welcome :)

An "all" option won't be added. A "none" option will. "All" is the equivalent of a select with the #multiple property enabled and then selecting everything, so that's what should happen.

I just have to rewrite the rendering function at this point. The "required" property of form elements is already being passed through (that's not yet committed though).

Committed. Please give the 5.x-dev tarball a try and report back how it works.

An "all" option is only applicable to selects with the "multiple" property enabled, which currently isn't supported at all. First there has to be support for that.

The "none" option is useful when you don't want to select *anything*, because now you *always* have to select something.

The "all" option is necessary in exposed view filters when the filter is optional. See functionality without the module installed. Also it's important to be able to filter by a parent category only, ie. including "all" sub-categories.

Great module by the way. Some teething issues expected early on but you have made a fabulous start.

Actually to be consistent with the way exposed views filters work, the top item in the *parent* list should be "all" (as I said in #9) but the top item in *subsequent* levels should be "none" (different to what I said in #9).

In views filters language, "all" is really "any". Existing views filters functionality includes "all" for parent level and "none" for sub-levels. It would be nice to have "all" *and* "none" at the sub-level, but "all" at sub-level is not currently provided by views filters.

Didn't mean it to sound this complex.

Hierarchical Select currently doesn't support selecting multiple items. So it doesn't make sense to select all of them. First we need multiple select support. In fact, the "all" option could be part of the same patch.

I hope I'm following the right procedures by reopening this issue (I apologize if I'm not). The Hierarchical Select 2 now supports multiple select and the «all» option (actually «any») is essential for the use of exposed filters (without it the vocabularies became mandatory and the search returns empty if no tag is selected).

I believe this module has a great potential and it could have a very wide use, but any site that uses exposed filters in views needs this «all» option or, at least some way to disable Hierarchical Select when exposed filters are being used (enabling it only in node edition and in views with no exposed filters).

Best regards.

Agreed. Completely forgot about this – because I haven't tested HS 2's integration with Views yet.

You will get the ability to set it to an arbitrary name (all/any, whatever you prefer).

Not sure I'll have time for this any time soon though. Sponsoring would allow me to give it a higher priority.

Oh and please start a *new* issue. This was the issue for the ability to have optional form items: http://drupal.org/cvs?commit=82347.

Thanks.