Bug #62480
closed
Deleting a file with broken references via BE module not possible
0%
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
Updated by Gerrit Code Review about 10 years ago
- Status changed from New to Under Review
Patch set 1 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at http://review.typo3.org/33562
Updated by Gerrit Code Review about 10 years ago
Patch set 2 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at http://review.typo3.org/33562
Updated by Cornel Boppart about 10 years ago
Updated by Gerrit Code Review about 10 years ago
Patch set 3 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at http://review.typo3.org/33562
Updated by Frans Saris about 10 years ago
Is running the update references commandant in the DB tools module not enough to cleanup the references?
Updated by Cornel Boppart about 10 years ago
Frans Saris wrote:
Is running the update references commandant in the DB tools module not enough to cleanup the references?
Updating the reference index does not help in this case. Apart from that, the System Module with all the DB tools inside is accessible for admins only.
To reproduce the error or testing the patch you can do this following few steps:- Create an image or textpic element
- Add an image to that element and save
- Now, delete the tt_content record from DB via command line or e.g. phpmyadmin
- Go to Module File>Filelist in Backend and try to delete that image which was added to the content element
Updated by Gerrit Code Review about 10 years ago
Patch set 4 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at http://review.typo3.org/33562
Updated by Gerrit Code Review almost 10 years ago
Patch set 5 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at http://review.typo3.org/33562
Updated by Gerrit Code Review almost 10 years ago
Patch set 6 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at http://review.typo3.org/33562
Updated by Gerrit Code Review almost 10 years ago
Patch set 7 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at http://review.typo3.org/33562
Updated by Gerrit Code Review almost 10 years ago
Patch set 8 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at http://review.typo3.org/33562
Updated by Gerrit Code Review almost 10 years ago
Patch set 1 for branch TYPO3_6-2 of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at http://review.typo3.org/35743
Updated by Wouter Wolters almost 10 years ago
- Status changed from Under Review to Resolved
Updated by 
