Allow for deletion of a single value of a multiple value field

i can confirm this

just a follow up to the issue. this isn't just a problem with removing ones with required fields. the problem also exist if you are simply editing an entity with a field collection in it that has required fields. right now the default is to always have a blank 'new' field collection at the end (or unlimited values). I think this could be fixed by only adding the new field collection form if the add more button was pushed.

just for an example:
i have a field collection degree that contains 3 required fields (school, program, type). this is an unlimited values field in my profile. if a user needs to edit their profile for lets say changing their name, upon saving it will say that required fields haven't been filled out due to the blank field collection form that contains required fields.

this is doing what it is suppose to in some respect of making sure required values are filled out. however, there wasn't a need for a new field collection form as the user didn't intend on adding a new degree field collection.

Subscribe, just ran into the same issue.
I too would prefer that it displays the last filled field and an add more button, insetad of an extra empty field.

sub
I also need to remove the blank line when editing a node
and the Remove link next to each one!

If I understand this topic correctly, I believe the issue I'm having is related to the need for "unlimited-aware validation."

I have an unlimited field collection that consists of a text field and a boolean check box. Every time the node is edited and saved a new blank instance of the collection is generated. (Neither field is required.)

I have the same problems as the jared12. Need "Remove" button

subscribe

@RobW at #6

That issue & patch #1234574: Add a delete button on the field-collection item edit form is not related to what this issue ask for, it is just a redundant delete button to the item edit form

I made a jQuery script that add the delete button next to each multiple value, but that is just half the solution, since if the user hit the Add another Value button, the deleted one returns :p
my jQuery could use a livequery and delete the row again, not the best solution but ... I will try and if it works I will share my code with you all

Similar Drupal core feature request: #1038316: Allow for deletion of a single value of a multiple value field

Subscribe.

I have same issue with not only required fields but fields in general in the embedded widget. as of latest build at this time I get this error "An illegal choice has been detected." when hitting "add another" button.
In my field collection, I have, in order: 2 text fields, 1 long text + summary, 1 list (text), 1 text field, 1 number field.

If I may be so bold, I'd like to elevate priority of this, since it seems as a showstopper for field collections.

I figured out what was causing an issue:
in form.inc @ line 1289 elseif (!isset($options[$elements['#value']])) {

a list field was cause an issue because it was lacking a 'value' entry in the array that is expected. This list field was using the checkbox/radio buttons widget. After I changed it to a list(text) list select widget, the repeatable field/field collection is working properly now.

subscribe

Same issue here. I'll check the behaviours of Drupal core and this module and than see what I can do.

However, in my opinion, a delete/remove button for a field-collection is a must.
The patch for the delete button above doesn't seem to work when the "field collection table" module is installed.
Looking into that one too.

We're definitely going to need to focus this. "Unlimited-aware validation" should be a separate issue.

I marked #1208030: Embedded widget: remove item with required select not possible as a duplicate, it is an example of why this is a major bug and not a feature request.

subscribe

Subscribing... This is really needed.

Subscribe

Mirroring the core issue. I'd like to think this would be fixed in core first, but it might not be backportable, so we'll likely have to do this ourselves anyway.

subscribe

subscribing

subscribe

subscribe

subscribe

subscribe

sub

sub

sub

subscribe

subscribe

I don't understand how this issue is different from #1234574: Add a delete button on the field-collection item edit form. Whenever you're editing an entity that has a multi-valued field_collection field you can now delete specific field_collection entities via a delete button. Isn't that what this issue is trying to accomplish? Shouldn't we mark this issue duplicate?

Thanks,
-Derek

Agreed.

Just downloaded de dev version of NOV 15 and ... patch is already committed and it works great.

Thanks Merlin