Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
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
Comment #1
legolasboCould you elaborate more on the use case? When would this functionality be usefull? What would you be trying to achieve?
Comment #2
legolasboComment #3
MrPeanut CreditAttribution: MrPeanut commentedI'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.
Comment #4
legolasboOk, 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.
Comment #5
daften CreditAttribution: daften at Dropsolid commentedClosing as outdated because no activity in a long time and Drupal 7 goes EOL soon. Feel free to re-open if needed.