Make it work for LIST type fields [#2543814]

Thanks so much for the great module. This issue is related to #1184326: Can't find the widget

Every time I try this module it's usually to improve the usability of an existing site that already has data in a list field. So sadly, I haven't gotten a chance to take it for a spin yet :(

It seems that if what this module allows you to do is select from list (or, add another item) then it should be a widget on the LIST type field. Text fields don't allow you to select from a list, so requiring people to add a text field in order to get this functionality is counterintuitive.

Comments

Comment #1

legolasbo

he/him

Dutch

Middelburg

CreditAttribution: legolasbo at Ibuildings commented 27 August 2015 at 15:10

I've already played with the idea of support list fields, but I see a major problem with this.

Natively, Drupal doesn't allow text lists to be changed. This is something we can overcome, but enabling a way to change the configured options will make features show up as overridden. Any reverting of the feature would probably fail (best case) or result in the option being removed, which would result in more serious problems like data loss.

Comment #2

legolasbo

he/him

Dutch

Middelburg

CreditAttribution: legolasbo at Ibuildings commented 30 September 2015 at 12:01

Category:	Task	» Feature request
Priority:	Normal	» Minor
Status:	Active	» Postponed

Postponing this since it requires additional research and adds noise to an already full issue queue. Anyone willing to pick this up is welcome to do so though.

Comment #3

jenlampton

she / her

CreditAttribution: jenlampton at Backdrop CMS commented 17 January 2016 at 05:13

Component:

CCK / Field API widget

» Field widget (non-specific or listed)

Natively, Drupal doesn't allow text lists to be changed.

I'm not sure what you mean by this. Is it that there is no field_default_value_alter hook, or similar? We might be able to do it just by altering the form, or maybe the particular element... I'll take a closer look and see.

I'd be willing to take a stab at making this change, since I wanted to use this module yet again, and am again thwarted by my pre-existing list type fields.