Currently if I create a Content Taxonomy field for a vocabulary, the function provided by Taxonomy Other is removed, it'd be handy if the 2 modules were compatible.

Comments

no2e’s picture

That would be nice.

phildu’s picture

subscribe

Xabraxas’s picture

Version: 5.x-1.x-dev » 6.x-1.1

This is something I would also like to see for Drupal 6. Is there any chance this is being worked on?

wilfn’s picture

I would also appreciate this feature. Also, the same goes for compatibility with Taxonomy Super Select.

psicomante’s picture

+1

benone’s picture

subscribe

brisath’s picture

subscribe

Michsk’s picture

I to +1 and subscribe for this one. I'm no coder but i will take a look at this and maybe will be able to get this done, but if there is someone who is a true coder and can get this fixed please don't hesitate!

Michsk’s picture

And when we will start on this, there should also be a content_multigroup option since that is a strong option in content_taxonomy.

damiandab’s picture

subscribe

akin.demirci’s picture

subscribe

jarchowk’s picture

subscribe

alibama’s picture

yes. please = any chance? am certain this is a great feature... autocomplete confuses people way too much

bsandor’s picture

Subscribe

cposer’s picture

Subscribe

CarbonPig’s picture

Would be awesome! Subscribe

slucas’s picture

I am also interested.
TIll now I've found a way to do similar things with http://drupal.org/project/hierarchical_select
But the UI is not so clear.
And there's this module http://drupal.org/project/select_or_other but it seem only for text field.
As I'm using nearly always content taxonomy field, it'll be great.
Another option i've found create another field just below, in autocomplete widget, and with the title "other".
The new value created will be available for all immediatly.
But surely a bit complicated for such a task.

cposer’s picture

I'm starting to doubt that this module really is "actively maintained". Well, there's no help but pushing requests until someone notices =)

rellis’s picture

This module is only actively maintained in that I'll do bug
fixes for current functionality, and compatibility fixes
that don't require a major rewrite.

Compatibility with content_taxonomy would require a
different approach than the current one (which uses
hook_form_alter() and taxonomy functions).

I did have some ideas for a new version that would use
a custom form element and widget -- something along the
lines of select_or_other -- but I haven't got much time
for it, and I don't want to duplicate effort.

cposer’s picture

Fair enough =)