Project

General

Profile

Actions
Copy link

Bug #62480

closed

Deleting a file with broken references via BE module not possible

Added by Cornel Boppart about 10 years ago. Updated about 6 years ago.

Status:
Closed
Priority:
Must have
Assignee:
-
Category:
File Abstraction Layer (FAL)
Target version:
next-patchlevel
Start date:
2014-10-26
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
6.2
PHP Version:
5.4
Tags:
Complexity:
Is Regression:
No
Sprint Focus:

Description

A file with broken FAL references cannot get deleted via the TYPO3 backend module File>Filelist. Such broken references for instance could occure after a manual data migration/import or deletion of one or more referenced records by executing db queries via command line.
Currently, a fatal error occures in cause of that $shortcutRecord is NULL and not type of array but is passed as the second argument of method \TYPO3\CMS\Backend\Utility\IconUtility::getSpriteIconForRecord().

A redactor which only has access to files via BE module wouldn't be able to delete such a physical file but would see a thrown error [1].

This patch [3] will solve this issue by deleting the file with corrupt relations anyway and outputting a common flash message by informing about there were broken references [2].

[1] error-fileWithBrokenReferences.png
[2] info-FileWithBrokenReferences.png
[3] deleteFileWithBrokenReferences.png

Files

Download all files
error-fileWithBrokenReferences.png (91.8 KB) error-fileWithBrokenReferences.png Cornel Boppart, 2014-10-26 19:45
info-FileWithBrokenReferences.png (14.2 KB) info-FileWithBrokenReferences.png Cornel Boppart, 2014-10-26 19:45
deleteFileWithBrokenReferences.patch (7.21 KB) deleteFileWithBrokenReferences.patch Cornel Boppart, 2014-10-26 19:45
onSuccess-fileWithBrokenReferences.png (25.7 KB) onSuccess-fileWithBrokenReferences.png Info message after a successful deletion Cornel Boppart, 2014-10-27 09:34
Actions
Copy link

Also available in: Atom PDF