[Form] Deletion not handled on collection field since 2.3.10

[ohaag]

Although the param allow_delete is set to true on the field. When the form is submit, during the handler of the request, the base entity of the form get back the erased entity in the form.

http://symfony.com/doc/2.3/cookbook/form/form_collections.html#allowing-tags-to-be-removed

This is exactly the example it concerns. I'm currently in the case : "Doctrine: Ensuring the database persistence"

"$task->getTags()" contains the same data than "$originalTags", so the comparison made with "false === $task->getTags()->contains($tag)" can't render the wished result.

This problem occured in 2.3.10 and not in 2.3.9

[webspin]

+1

[mkovrigovich]

have the same issue

[bartlomiej84]

Same here.

I believe after setting data like this:

$this->form->setData($entity);

then after validation, the collection in $entity contains all items. (in 2.3.10 - about), even those which were removed from form.

In version 2.3.9 that collection doesn't contain items which have been removed. It should stay this way.

Any news on this?

[bjo3rnf]

I can confirm the issue as well. I temporarily fixed my local install by replacing the new ResizeFormListener.php with the 2.3.9 one.

[bjo3rnf]

$iter->offsetUnset($name); doesn't seem to unset the offset from the original array so what about adding $data = $iter->getArrayCopy();?

[rpagliuca]

I'm having exactly the same issue. Reverting to 2.3.9 fixed it.

[florentchaboud]

Still have the issue with 2.3.10, had to revert to 2.3.9 too.

[stof]

@florentchaboud The issue affects only 2.3.10. Given that it is a release, an issue will not be fixed inside it (you don't change a release). The fix is in the 2.3 branch (it will be part of the 2.3.11 release

[florentchaboud]

@stof My bad ! I've didn't notice that we can't fix a release, even if it's kind of logical !
So thanks for the reply and sorry for the inconvenience ;)