Joining forces?
| Project: | Big Autocomplete TAXonomy |
| Version: | 6.x-1.6 |
| Component: | Miscellaneous |
| Category: | support request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
Jump to:
I just found your module and noticed the overlap with taxiselect.
Are you interested in joining forces? Have a look and see what you think. I think there is enough diff for them both to live side by side.
Anyway as an aside, you may want to look at the following:
<?php
/**
* Implementation of hook_form_FORM_alter().
*/
function taxiselect_form_taxonomy_form_term_alter(&$form, &$form_state) {
if (variable_get('taxonomy_override_selector', FALSE)) {
// your code here
}
}
// similar for admin interfaces
?>This prevents Drupal from loading the select lists before you insert your replacements. Reason, even a small big vocab can suck all of the memory resources using core Drupal selects. Intercepting this after the select element has been rendered has no effect on the server performance. This is a very poor API as you need to implement the native lists as well as your own, and there is only room for 1 module to do this at any one time, but so far, only Hierarchical Select & TaxiSelect use it.
Alan
#1
Cheers for the comments Alan. The batax module sets the mythical taxonomy_override_selector on install.
#2
:)
I'll add a warning about the conflict on TaxiSelect page.