Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.There seems to be a depth option for content_taxonomy, but not for taxonomy?
Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.There seems to be a depth option for content_taxonomy, but not for taxonomy?
Comments
Comment #1
wim leersThat's correct.
Drupal core's Taxonomy module does not support this. The content_taxonomy module does support this. If you want support for this feature, you should file an issue against Drupal core. It's not up to Hierarchical Select to implement this.
Comment #2
nicolash commentedRight, sorry for double-posting...only saw this response after I replied to the other one.
Just out of interest...when using taxonomy_get_tree(), each term has a depth parameter - could that be an approach? Or even just a number to set when to stop creating another select list - regardless what the hierarchy depth actually is?
Comment #3
wim leersYes, the API supports it, but the UI does not: the node form validation does not verify this. I *could* implement it in HS, but I won't, for the reasons mentioned.
You could write your own glue module that allows you to do this.
Alternatively, just use content_taxonomy ;)
Comment #4
nicolash commentedFair enough. No, I'm not opposed to content_taxonomy, but we've got pretty extensive integration with the taxonomy module already and it's a bit late in the project to switch such a major part.
I think I will go with the glue module approach...thanks for your replies - that's the best maintained issue queue I've seen so far on Drupal.org ;)
Comment #5
wim leersThanks. I'm doing my best (and am spending probably too much time on it). It's nice to know that at least somebody notices it :)
Content_taxonomy can use Taxonomy's tables (that's what I do too), so you can simply continue to use the Taxonomy API!