Options not showing up for Taxonomy Term Reference lists

I doubt the Taxonomy Term reference field would support submitting arbitrary 'other' values. It wouldn't validate, would it?

If you can identify that Select (or other) should work in this case, and has a bug in code, please reopen.

Taxonomy Term Reference is very common used, and this module should support it.

+1

I agree this should be a major part of this module.

Yes. This is definitely needed.
CCK Select Other http://drupal.org/project/cck_select_other doesn't provide this either #1135556: select other for term field?
Are there any other ways to do this?

(Since this is now a feature request, I think it's appropriate to re-open it)

see #1

Term reference fields do support creating arbitrary "other" values: the core taxonomy_autocomplete widget already supports this. For some purposes Select (or other) would be a better UI than taxonomy_autocomplete, as it makes the existing options more visible.

I'm not quite sure why you think it isn't feasible, I haven't really done more than repeat the OP.

I haven't really done more than repeat the OP.

Precisely. Reiterating that it is a good idea doesn't really help.

This was originally a bug report that wasn't valid and dealt with as such. Changing it to a feature request without providing any more research or code, is what... a homework assignment for me?

I created this module as an API for developers to use so that I wouldn't have to get involved. The integration features here were provided as patches by other users, and to be honest I'm not too happy about having to maintain those.

Plus I'm pretty sure Drupal 7's FAPI comes with the ability to do much more with 'other' fields, so this module might need to be deprecated or redesigned :( I'd be hesitant to develop features around this model at the moment. I will start a new issue.

This will be an interesting and usefull feature, already provided by the http://drupal.org/project/taxonomy_other module for drupal 6.

+1 for me to add this functionality in this module too.

Thank you very much for considering this.

I too, would love to have this feature. As long as users have the ability to add terms in a vocabulary, they should be able to use the "other" to add new terms.

S.

We would also need this feature.

I would suggest if anyone who wants this can figure out how to do it, start a new project for it?

@danielb
In your initial reply to this feature request you said:

I doubt the Taxonomy Term reference field would support submitting arbitrary 'other' values. It wouldn't validate, would it?

I might be missing something, but as there also is the tagging widget which allows new terms to be added, I though an "select or other" approach should work for taxonomy term reference fields as well.

If this is the case, I think it would be better included in this project then starting another. However, I totally understand that anyone who needs this should actually help doing as well and not just requesting it. Means, if it turns out we will need this in our upcoming project I'll definitively try to help implement it.

Hi there,

It seems someone has done just that ...

elithorkelson wrote a module that rely on select_or_other.
see http://drupal.org/node/1208512#comment-5605324

It is a one shot module, and although it is not completely integrated with drupal.org (module is hosted on git, not sure that it gets updated), it gets the job done.

Maybe danielb could consider the integration of this module into select_or_other.

S.

Please Danielb consider what spouilly said in #15:

Maybe danielb could consider the integration of this module into select_or_other.

Thank you very much for this

I tried the external module in http://drupal.org/node/1208512#comment-5605324, it works and I will maybe use it. Any plan to integrate it in this module?

Thanks :)

I would be interested in getting this integrated as well. I'm trying to move from Webform to Entityforms and I have a few Select (or Other) Webform Select List components that are filled by taxonomy term lists. Entityforms uses Fields for the form components, so this sounds like it'll be the way to go. I'm anxious about using a random patch rather than the official release (particularly in production), so the sooner this becomes available the better. I would even take a dev release.

Seems to be a popular request so lets make it happen. Marking this issue as a duplicate of #1716764: Incorporate Select or Other Taxonomy module as I got to that one first.