[Flow] Persistence problems after implementing an image field with TYPO3.Media

[Felix Rupp]

Hey guys,

I have a severe issue in my intranet project, which came up after implementing an image field with TYPO3.Media.

My model „Member“ now has a field of the type \TYPO3\Media\Domain\Model\Image with corresponding setters and getters. The HTML forms for creating and editing this model have also been updated.

I can create „Members“ without problems, even if I specify an image to upload. The image is also displayed normally. No problems until now.

If I try to delete the image (via controllerAction), I receive no errors and even get the redirect back with the correct flashmessage (implemented try-catch-blocks around to catch possible errors). I assume the image being deleted, but that’s not the case. The problem expands to the fact, that I also can’t delete my „Member“ anymore, also no error messages. For me it feels like the remove process in the repository is not being persisted, while normal changes via editActions are persisted normally here.


One side effect is, that I also have problems with another model, called „LoanUnit“, an abstract entity for items a Member can borrow. The process of borrowing an item is implemented with an ajax function and the corresponding controllerAction. This worked until I implemented the image-field. It behaves just like the delete-problem, but even occurs when editing the „LoanUnit“. This model has not been touched since months, so I assume the problem is not with this code. 

All debugs and var_dumps show, that the editing is done correctly in the memory, but it’s not being persisted.

I already deleted and set up my database 2 times and updated to the current dev-master version via composer.

Please let me know if you need sourcecode, the project is very big and so I hope to get some abstract hints before bothering you with hundreds of lines of code.


Thank you for your help!


Regards,

Felix Rupp