AdminBundle sonata_type_collection Delete Column: Pitfall

I ran into a problem today working with AdminBundle. Basically i am trying to manipulate the delete column that automatically gets inserted. It would not work if i check the box and hit update or global delete. It would just not do anything or remove the whole top entity.

Any thoughts?

I have tried several things but nothing. Any hint appreciated.

After this thanks to @rander hint, I was able to figure out that the way to do this was:

* @ORM\OneToMany(targetEntity="StartDate", mappedBy="course", cascade={ "persist", "remove"}, orphanRemoval="true")

The xml version on the documentation here was cryptic to my eyes even though I went through that.

7 thoughts on “AdminBundle sonata_type_collection Delete Column: Pitfall

  1. Pingback: AdminBundle sonata_type_collection Delete Column: Pitfall ← Bookmarks

Leave a Reply to Wijnand Cancel reply

Your email address will not be published. Required fields are marked *