Project

General

Profile

Actions

Bug #64563

closed

Unable to delete images which have references

Added by Christian Zimmermann almost 10 years ago. Updated over 8 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
Backend User Interface
Target version:
-
Start date:
2015-01-28
Due date:
% Done:

0%

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

Description

When trying to delete an image from the file list nothing happens and the list view turns blank. The following error is logged:

Core: Error handler (BE): PHP Catchable Fatal Error: Argument 2 passed to TYPO3\CMS\Backend\Utility\IconUtility::getSpriteIconForRecord() must be of the type array, null given, called in
/typo3/sysext/core/Classes/Utility/File/ExtendedFileUtility.php on line 411 and defined in
/typo3/sysext/backend/Classes/Utility/IconUtility.php line 710

This error only occurs when the file is referenced in a content element (even if those references are in older revisions).


Files

screenshot.jpg (238 KB) screenshot.jpg PHP Debug Screenshot Christian Zimmermann, 2015-01-28 14:21
Actions #1

Updated by Christian Zimmermann almost 10 years ago

Added a screenshot

Actions #2

Updated by David Richter over 9 years ago

push - we are getting the exact same error too

For an editor it's very hard to get those files deleted, mainly because they can hardly find out where it is referenced, for deleting those contents.

Actions #3

Updated by Riccardo De Contardi almost 9 years ago

  • Status changed from New to Needs Feedback

Is this still true for 6.2.15 or 7.6.1-dev (latest master)?
The number of references for each file is shown on the filelist module; and as far as I can see on both versions, if you try to delete an image which is referenced, the CMS refuses to do that and lists the content element where the file is used.

Actions #4

Updated by Riccardo De Contardi over 8 years ago

  • Status changed from Needs Feedback to Closed

No feedback within the last 90 days => closing this issue.

If you think that this is the wrong decision or experience this issue again, then please write to the mailing list typo3.teams.bugs with issue number and an explanation or open a new ticket and add a relation to this ticket number.

Thank you

Actions

Also available in: Atom PDF