Bug #51562

Task #50876: Handling of deleted files in FAL

sys_file records marked as deleted crash file list (AKA: remove sys_file.deleted flag)

Added by Francois Suter over 8 years ago. Updated over 3 years ago.

Status:
Closed
Priority:
Should have
Category:
File Abstraction Layer (FAL)
Target version:
Start date:
2013-08-30
Due date:
% Done:

100%

Estimated time:
TYPO3 Version:
6.1
PHP Version:
5.3
Tags:
Complexity:
Is Regression:
No
Sprint Focus:

Description

If some sys_file records have their "deleted" flag set to 1, the File > Filelist module will crash with exception "No file found for given UID". It seems like the deleted flag is not used anymore, but was obviously used at some point in the past, since I have a few records with such a status in my database. I guess I'm not the only one.

Reproducing the error condition is easy: access the sys_file table in some DB management tool, set the deleted flag of some file to 1 and try to access the folder where it is stored in the File module. This results in an exception.

I'm not sure how this is best corrected. I have seen that there's an intention to drop the deleted flag entirely, which seems fine if it is not used anyway, but that would be for 6.2 only. Something must be done for 6.0 and 6.1.


Related issues

Related to TYPO3 Core - Bug #52245: Revert BackendUtility::BEenableFields in FALRejected2013-09-25

Actions
Blocks TYPO3 Core - Bug #51929: Creation of sys_file-table fails due to incorrect keyClosed2013-09-12

Actions

Also available in: Atom PDF