Closed (fixed)
Project:
Multiple Fields Remove Button
Version:
7.x-1.5
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Reporter:
Created:
13 May 2016 at 12:23 UTC
Updated:
26 Nov 2017 at 19:34 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
alex.bukach commentedI have faced the same issue, here's the patch.
The reason was that the values for field items (if not set in form state values) are taken from entity stored in
$form_state, and therefore to have proper (empty) value of the newly added item, we should process the entity the same way we do for the form and form state.Comment #3
Koen.Pasman commentedThanks a bunch! I was using this module together with taxonomy_orderselect (patched) but it failed to work properly. However, with this patch applied it works when I'm removing existing references.
However, I still run into problems when adding new values. I select a value, click 'add a new item' and the previous value is pretty much discarded.This was caused by me using the taxonomy_orderselect module instead of the multiple_select module. I recommend using multiple_select instead of taxonomy_orderselect!
Comment #4
lolandese commentedTested with a multi-value text field I confirm the issue. Removing a field value makes that a newly added is pre-filled with the last removed value. It has to be noted that usually you get an empty field already available, so this applies in the situation you want to add more than one new value.
The patch applies cleanly and solves the issue.
Comment #5
lolandese commentedCan this be merged in dev? Thanks.
Comment #6
mrpauldriver commentedBe good to see this committed to a 7.x-1.6 release
Comment #8
semjuel commentedComment #9
pifagorComment #10
pifagorThe previous patch does not work for version 1.5.
I added a new patch. It is not optimal, but it works.
Comment #13
semjuel commentedPlease use version 7.x-1.6-alpha2