OG Vocabulary does not consider other modules handling 'taxonomy_override_selector'

In this use case, it will (should - I am talking about TaxiSelect... I have no idea about OG Vocab) be safe to increase the weight of the TaxiSelect < OG Vocab so that it runs first. If you look at the install file, you will see a list of modules that must be run before TaxiSelect as they bypass the core Taxonomy access checks on the core Flag 'taxonomy_override_selector'.

The issue here is that there is no mechanism in Drupal to control this form, the flag is a 0 or 1. The elements are added via a hook_form_alter() [Taxonomy module - weight = 0] so it is a race condition based on the system weight.

This will effect at least the following modules, so moving to the OG Vocab queue.

Internationalization - rewrites the vocabs
Hierarchical Select - like this, handles the Taxonomy form, as does a couple of others.

Solution - OG Vocab must run last

Another module that will have a conflict - Big Autocomplete TAXonomy

@snorkers Both Taxiselect and BATAX will conflict if you don't already know that.

I can not update the OG Vocab system weight from taxiselect, is it running OK? It has been added to my watch list of modules in the past, but I see no reason for this currently. Please test the new weight combo, and if this runs OK I take it out of my watch list and let other maintainers of modules that use 'taxonomy_override_selector' know. Then OG Vocab just needs to make sure that it runs after these modules.

This sounds like a specific case, so a custom module can give og_vocab the required weight.

So you do not care about the core Drupal feature 'taxonomy_override_selector'? There are at least three modules that use this, maybe more. From the quick look at the most up to date code, all you need to do is make this module is run last and make sure that you do not update / create any of the vocabularies that are absent from the form when the form alter is called.

I think this is why the module was added to the "make sure that this is run first" module lists of HS & Taxiselect. It use to recreate the select widgets, the sole point that the 'taxonomy_override_selector' flag. This flag was added to allow better implementations of the term select widget, as a select element is very basic for a number of vocabularies. I personally have a country / region / city & town vocab that will cripple the best system if you try to render it in a single select element. (it is about 230 MB)

Anyway, your call.

PS: That vocab cripples Drupal itself as the DnD page tries to load the most of the vocab in a single hit. Not a common use case unless someone creates a Drupal friendly geocode database of significance.

Ok, I might missed the point of this issue -- please explain how it's related to the taxonomy_override_selector variable.

This is a flag that stops the Taxonomy module from creating the form term elements. Once the flag is set, it simply saves the terms on submit, nothing else. Then it is up to the module that created the flag to implement these, usually with a form_alter().

The flag also overwrites the admin section select elements.