Views exposed Taxonomy filters: supporting the **ALL** option

The first step would be: "any"/"all" support in the hierarchical select form element.

The second step is the operators part. This will require a customized version of the hierarchical_select form element, because it'd otherwise be bloat: it's only necessary for Views support. "any"/"all" support has use cases in any hierarchy, although it's pretty rare.
So I'm postponing this second part, because it'd be a lot of work to do if I don't want to make Hierarchical Select messy.
Note: it's possible that we may not even need this operators stuff, if I can manage to override *just* the selection of items instead of both the selection of items and that operator select. I don't have the time to look into this atm, so I'm assuming the worst-case scenario.

Assigning to myself since it's pretty unlikely somebody else will step up to do this. Status is critical indeed: HS claims Views integration, yet fails to deliver this critical feature.

Users interested in this issue may also be interested in this one: http://drupal.org/node/217368.

I began writing a new property for the hierarchical select settings in a form item: special values. This would allow you to easily add new special things like **ALL**.

However, this is a *very* special property, that demands exclusive selection: when it is selected, no other value should be selected. In multiple select mode, that becomes an issue: multiple select mode should not be allowed when special values are defined. The correct solution (and also the solution that doesn't require me to make the number of parameters even greater), is to implement the HS hooks again, for Taxonomy exposed filters in Views. Otherwise the code gets unnecessarily bloated.

For the sake of completeness, I've attached the patch of what I had so far.

To do this properly, I'll have to provide some configuration settings per view as well. This will require a relatively large amount of work, for which I don't have the time ATM. Postponing.

For now, I've implemented the second thing you were asking for, which is actually *a lot* easier than the first thing... See #217395 for details. Thanks to that, this issue just became minor :)

Geh :P Not AFAIK. But you could of course start a new tradition ;) :)

Reposted as http://drupal.org/node/218219 per Wim Leer's request (#10). Sorry!

Please open a new issue for that.

This feature will be sponsored by Marmaladesoul.