Taxonomy Super Select doesn't work when Hierarchical Select Taxonomy is enabled
muhleder - September 14, 2009 - 12:48
| Project: | Taxonomy Super Select |
| Version: | 6.x-1.0 |
| Component: | Code |
| Category: | task |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed |
Jump to:
Description
Hi,
When using the HS Taxonomy module, it seems to apply the HS override to all forms, which stops other Taxonomy modules from altering vocabs not specified to have HS applied. Looks like there should be a check in hs_taxonomy_form_alter to see if HS should be applied to the form (or preferably the individual vocab in the form).
Fwiw the problem I'm having is that HS breaks vocabs set to be altered by Taxonomy Super Select module. Adding logic to only apply HS to my particular content type in hs_taxonomy_form_alter fixes the problem for me, but isn't something that could be patched back.
Thanks for a great module tho,
Mark
#1
Configuring Taxonomy Super Select to run after Hierarchical Select should be sufficient (i.e. heavier/higher module weight). This happens because HS Taxonomy does this in the hook_enable() implementation:
function hs_taxonomy_enable() {variable_set('taxonomy_override_selector', TRUE);
drupal_set_message(t("Drupal core's taxonomy selects are now overridden on the
Taxonomy Term form. They've been replaced by
Hierarchical Selects for better scalability.<br />
You can <a href=\"!configure-url\">configure</a> it to
be used on node forms too!",
array(
'!configure-url' => url('admin/settings/hierarchical_select/configs'),
)),
'warning');
}
I.e. HS Taxonomy tells Drupal core to not generate the default form items because they're not scalable. Just altering the form isn't sufficient, because then the original (aka unscalable) form items are still being generated.
#2
Changing the module weight fixed the issue for me (in another use case as it happens). Thanks again.
#3
Automatically closed -- issue fixed for 2 weeks with no activity.