Project

General

Profile

Actions

Bug #61491

closed

Error Handling when File Collection missing

Added by Gregor Favre about 10 years ago. Updated about 6 years ago.

Status:
Closed
Priority:
Could have
Assignee:
-
Category:
File Abstraction Layer (FAL)
Target version:
-
Start date:
2014-09-09
Due date:
% Done:

0%

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

Description

Using latest 6.1.10.

When a page is being rendered with a filelist CE, holding a reference to a sys_file_collection, but the sys_file_collection record got accidentally deleted by the user (by deleting its parent page), a spurious error message is shown in the frontend:

#1: PHP Catchable Fatal Error: Argument 1 passed to TYPO3\CMS\Core\Resource\FileCollectionRepository::createDomainObject() must be of the type array, boolean given, called in /typo3_src-6.1.10/typo3/sysext/core/Classes/Collection/RecordCollectionRepository.php on line 64 and defined in /typo3_src-6.1.10/typo3/sysext/core/Classes/Resource/FileCollectionRepository.php line 70 (More information)

Instead it would be helpful to show an error to the user, that there was a reference to a sys_file_collection record, for which the target doesn't exist anymore. Moreover, it would be nice to prevent dangling references at all.

Reproduce:
1. Create a page with a sys_file_collection record
2. On an other page, create a content element of type filelist, referencing the sys_file_collection from step 1
3. Delete the page created in step 1
4. Open the page created in step 2 in the FE
5. The error message ist shown
6. The error can be resolved by removing the dangling reference on page 2

Actions #1

Updated by Georg Ringer almost 10 years ago

  • Status changed from New to Resolved

Thanks for your report and helping to make TYPO3 CMS better!

I tested with 7.0 and this is handled there, I am guessing also in 6.2 as no real FAL related changes have been done.

Feel free to reopen the issue if still valid for you in 6.2

Actions #2

Updated by Benni Mack about 6 years ago

  • Status changed from Resolved to Closed
Actions

Also available in: Atom PDF