TYPO3 Core

Hey Gernot,

thanks for your detailed report. I had a look at your extension, made it compatible with TYPO3 v11 and found out that this is because the Fluid Form submits the father record without any information about any children - thus, Extbase fetches the relations again completely.

So your example also works if you have 5 children, and you delete all at once, you save them and nothing changes - because the form does not submit an empty "father[children]" field anymore, so the incoming request cannot handle this (how should it know it should be emptied?). As long as there is one "child" record, the property $father->children is updated from the incoming request.

So the problem lies in the case, that the <form> should actually send something like "empty children storage" flag field (or "NULL") with it, so Extbase would know not to reconstitute the field anymore.

Just to clear the issue up:
Imagine you have another property "spouse" for the father model. just a text field. If you don't have an input field for "spouse" in the update form, and you just hit "save", the spouse field would never be touched.

So I'm not sure if we need to modify fluid, I believe the code comes from the ExtensionBuilder, which would need to handle such a thing with a specific flag in the Fluid template, as the Fluid template currently does not submit such information, so Extbase could handle it.

Hi Benni,

Ok, I understand. But I'm sure, that it is a problem of Extbase, not of the ExtensioBuilder.
Because the ExtensonBuilder does not generate code for childrens.

The main problem is, that I want to use the propertymapper in its full functionality (map also childrens). And with this, it's is not possible to remove all childrens.

A solution can be a new property/setting for the propertymapper. As you said, an "empty children storage flag".
But this should be in the core/extbase, not made by every developer for his own.

Thanks for the nice phone call.

The responsible part would be the MvcPropertyMappingConfiguration and the PersistentObjectConverter.

Ideally the PersistentObjectConverter receives an information for a subproperty "children" to "don't fetch from databsae if not given by incoming data" from the PropertyMappingConfiguration.

• Create a custom TypeConverter
• Create a custom Domain Model for updating