Hierarchical Select

Merge asked me to add support for Views 2 to Hierarchical Select 3 for Drupal 6. Once that was completed, they also asked me to add the ability to only show items in Hierarchical Select that were associated with at least one entity¹. This improved the UX for users: when filtering to an item in Hierarchical Select, it would be guaranteed that at least one entity would be displayed by Views!

Drupal 7’s client-side (JavaScript) settings (Drupal.settings) merging only supports merging of single-level settings, whereas Hierarchical Select was using multiple levels. This caused problems if a new Hierarchical Select instance was added in an AJAX callback.

Basic port of Hierarchical Select to Drupal 7: the core of the Hierarchical Select module, plus the integration with Taxonomy.

Corresponding Drupal.org issue: #200285. See the attached screencasts!

Marmaladesoul hired me to add multiple select support to the Hierarchical Select module, which lifted that module to the next level. See the live demo to see what an amazing UI/UX enhancement this is.

Paul Ektov was working on a new website for his company, a major U.S. car importer with settlements in both the U.S. and Russia. He needed certain functionality, some of which you could almost get with the existing modules – but not quite, the rest was simply non-existent. So he hired me to extend the former modules to meet his needs and to write the latter.

This resulted in a whole bunch of modules: