On at least the Drag-n-Drop select widget there is no way to remove a choice on multiple value fields once made with the "Add another item" button.

EG: If I've chosen 3 entries from among my 5 available options. I can't go down to just one or two choices.
Values: 1|Eggs, 5|Toast, 2|Bacon
From among: 1|Eggs, 2|Bacon, 3|Waffles, 4|Sausage, 5|Toast

Comments

danielb’s picture

So picking 'other' and leaving the other field blank doesn't do it?

Maybe you can add an option like: 0|-none-

doublejosh’s picture

I mean after the node has been saved.

If 3 have been chosen, you can't remove them.

doublejosh’s picture

Still no way to remove items from the list when editing a node.

doublejosh’s picture

Category: feature » bug

Actually upon closer look this only happens if it's an Unlimited value field AND it's required. The "none" option is not available when required.

The widget isn't smart enough to know that 'at least one' value is good enough for required.
Each instance is considered for the required status during validation rather than an overall required check.

I just removed the required status, though I suppose this is actually somewhat of a Bug, but probably fairly edge case.
It still helps make the input easier to use.

danielb’s picture

Yeah you're right, that is indeed the case. Don't know what to do about it at this stage.

doublejosh’s picture

Status: Active » Postponed

Moving to postponed since the full info is here and it won't be tackled for a while.

danielb’s picture

This appears to be a problem on other modules that use this system too, when configured in the manner described. I'm not sure we will find a solution to this. What really needs to happen is a way to remove one of the 'add another item' bits, like with an ajax link or something.

danielb’s picture

Status: Postponed » Closed (won't fix)

Seems we are not the only ones who want this.

#1038316: Allow for deletion of a single value of a multiple value field
#196421: Deleting unwanted multiple values / multiple values delta issues

I reckon we can close this issue then, leave it to be handled by CCK and core.