Aside for an empty text field for the "other" option, how difficult it would it be to make the field a node or entity reference field - either select list or autocomplete?

Comments

legolasbo’s picture

Issue summary: View changes

Could you elaborate more on the use case? When would this functionality be usefull? What would you be trying to achieve?

legolasbo’s picture

Status: Active » Postponed (maintainer needs more info)
MrPeanut’s picture

I'm not OP, but I started following this issue because of my use case, which was:

We have 100+ nodes of content type "profile," who represent our staff members. We have another content type "event," which contains a select (or other) field to choose "event contact." For 90% of the time, the event contacts consist of about 5 people. However, every once in a while, there is a need to select one of the other profiles. In this case, they would be the "other," and we'd want it as an entity reference so we could link to their profile.

legolasbo’s picture

Version: 7.x-2.20 » 7.x-3.x-dev
Status: Postponed (maintainer needs more info) » Active

Ok, I think I understand the use case now, but this is not something currently on the roadmap. I think it would take some effort to implement this and my priority is to fix the current bugs, add automated tests and work towards releasing the 3.x branch. However I will accept a patch for this.

daften’s picture

Component: CCK / Field API widget » Field widget (non-specific or listed)
Status: Active » Closed (outdated)

Closing as outdated because no activity in a long time and Drupal 7 goes EOL soon. Feel free to re-open if needed.