#82240Editing page and save changes results with error: No file found for given UID.
Description
Editing page and save changes results with error: No file found for given UID.
The page has an relation to an nonexisting file.
Deleting the Relation solves the problem.
Exists also in TYPO3 version 7.
Relations (sys_file_reference) to nonexisting files (sys_file) should be deleted automatically.
Reviews 0
No change resolves or names this issue in its commit message, and no comment links one.
History 5
-
Riccardo De Contardi commented and changed status
NewNeeds Feedback 01/29/18, 12:17 -
Andreas Kienast commented 05/05/18, 19:00
I can reproduce this if I delete the sys_file record in the database. Deleting the file in the file system only does not trigger that issue for me.
-
Riccardo De Contardi changed status
Needs FeedbackNew 05/05/18, 19:09 -
Susanne Moog commented and changed status
NewNeeds Feedback 03/06/19, 13:35@Andy I’d say if you manually and willfully destroy your system we can’t fix that for you. The tests Riccardo performed are what I consider valid behaviour, as we maybe don’t want to delete those references automatically in case the editor just made a mistake and restores the file (or the storage was temporarily offline which might happen in cloud/nfs setups). I’d close this issue tbh.
-
Susanne Moog commented and changed status
Needs FeedbackClosed 03/06/19, 13:48Andy says he’s fine with closing :)
I’ve performed the following test with TYPO3 8.7.9
1) load a file example.png in /fileadmin/Images/
2) create a page and a text with image content element
2.1) edit the text of the element
2.2) add the image example.png in Images tab
2.3) Save and close
3) I’ve deleted the image example.png (without using TYPO3, directly on the filesystem)
4) edit again the content element
Results
1) The relation in “Images” tab is still there, but there is no thumbnail
2) If I click on the “info” button I see the “File is missing!” orange box
3) the content element can be still edited and saved without any error message
4) on frontend, there is a “broken” image but no error.
Should I perform a different test? Or the issue can be considered solved? Thank you.