Now if you fill something in the multifield, it works great. The error only presents itself when the multifield is empty. So you can put something in the multifield and save, then try to delete (which empties the multifield) and then try to save and you get same error.
Done some digging and found this started to happen with above cfp. Below is decompiled code
Left is the code before the package, and right is after package. You notice that name.endsWith is not there. When a multifield tries to save without values it sends list@Delete: true . That is what is killing the call.
I don't know who to contact with this issue, but it is killing the use of content fragments.
Sean (BTW - I will be at Summit if anyone wants to meetup)