TYPO3 Core

Hi Alexander,

The use case is :

• I have a record with a file attached (a user with a CV for example, look sample TCA in bug description)
• In FE, I want to edit informations for this record with actions : editAction() and updateAction()

function editAction() {
    $uid = GeneralUtility::makeInstance(Context::class)->getPropertyFromAspect('frontend.user', 'id', 0);
    $user = $this->userRepository->findByIdentifier($uid);
    $this->view->assign('user', $user);
}

Then in Edit.html the form look like this :

<f:form action="update" name="user" object="{user}" >
    <f:form.upload property="cv" additionalAttributes="{accept :'application/pdf'}" />
</f:form>

And in update action :

public function initializeUpdateAction(): void
{
    $fileUploadConfiguration = [
        UploadedFileReferenceConverter::CONFIGURATION_FILE_VALIDATORS => ['application/pdf'],
        UploadedFileReferenceConverter::CONFIGURATION_UPLOAD_FOLDER => $this->settings['folders']['cvFolder'],
    ];

    /** @var PropertyMappingConfiguration $newUserConfiguration */
    $newUserConfiguration = $this->arguments['user']->getPropertyMappingConfiguration();

    $newUserConfiguration->forProperty('cv')->setTypeConverterOptions(UploadedFileReferenceConverter::class, $fileUploadConfiguration);
}

public function updateAction(User $user): void
{
    $this->userRepository->update($user);
}

• so, in FE form, I upload a new file (CV) and this new file should replace the old one
• but the result is not as expected :
  - new file is attached to record : so far so good
  - old file is not removed for this record
• the you have two files attached to that record instead of one - have a look at picture in description

Hope it help,
Florian

Hi Florian,

with that code attached I understand your use case much better.

I am still not quite sure where we would find the error exactly. I would need to debug the data mapper and the property mapper to see what exactly happens here and why the current object storage does not completely override the old one. That does not even have anything to do with maxitems here. It seems that property relations are merged. I currently don't know what the desired behaviour would be (for all), what actually makes sense and why things are like they are.

It seems that the upload_example of Helmut (https://github.com/helhum/upload_example/) is used here.
As the example is only coded to add files and not to replace files there is a need of adapting the example's code.

Imho it's not a bug in the Core. It's a missing feature in the example.