Bug #58019
FAL Indexer for broken files: Column 'width' cannot be null
| Status: | Rejected | Start date: | 2014-04-17 | |
|---|---|---|---|---|
| Priority: | Must have | Due date: | ||
| Assigned To: | - | % Done: | 0% |
|
| Category: | File Abstraction Layer (FAL) | Spent time: | - | |
| Target version: | 7.1 (Cleanup) | |||
| TYPO3 Version: | 6.2 | Is Regression: | Yes | |
| PHP Version: | 5.5 | Sprint Focus: | On Location Sprint | |
| Complexity: | easy |
Description
The FAL indexer fails to properly handle broken files.
To reproduce:
Create a text file with any content and name it test.jpg. Upload this via the backend or just place it in the fileadmin directory.
Visit the folder containing the file in the file module to trigger the indexing.
The indexing will fail and a NULL value is handled on to the database.
Note: I consider this to be a regression, because broken files did not break the file list before.
Related issues
History
#1 Updated by Oliver Hader about 1 year ago
- Status changed from Accepted to Needs Feedback
What is breaking in this regard? I followed your suggestion and uploaded a text/plain file and faked the "jpg" file name extension.
The file list tries to show an image, which of course does not work (thus, instead of using the extension, the MIME type should be used).
However, I don't get any warnings, errors or exceptions. Besides that sys_file_metadata.width is set to "0" in my case...
#2 Updated by Alexander Opitz 11 months 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.
#3 Updated by Philipp Gampe 11 months ago
- Status changed from Closed to Accepted
- PHP Version set to 5.5
Still present in master as of today: 424a9e331f45226bad2334af2ee97e9764351d5b
caller TYPO3\CMS\Core\Database\DatabaseConnection::exec_INSERTquery
ERROR Column 'width' cannot be null
lastBuiltQuery INSERT INTO sys_file_processedfile (width,height,size,checksum,name,identifier,storage,configuration,task_type,configurationsha1,original,originalfilesha1,tstamp,crdate) VALUES (NULL,NULL,'0','13c99f5990','preview_fake-jpeg_13c99f5990.jpg','/_processed_/preview_fake-jpeg_13c99f5990.jpg','1','a:0:{}','Image.Preview','8739602554c7f3241958e3cc9b57fdecb474d508','14607','0828324174b10cc867b7255a84a8155cf89e1b8b','1410823214','1410823214')
debug_backtrace require(o3/sysext/filelist/mod1/index.php),o3/mod.php#32 // TYPO3\CMS\Filelist\Controller\FileListController->main#21 // TYPO3\CMS\Filelist\FileList->generateList#308 // TYPO3\CMS\Filelist\FileList->getTable#189 // TYPO3\CMS\Filelist\FileList->formatFileList#339 // TYPO3\CMS\Core\Resource\File->process#657 // TYPO3\CMS\Core\Resource\ResourceStorage->processFile#307 // TYPO3\CMS\Core\Resource\Service\FileProcessingService->processFile#1224 // TYPO3\CMS\Core\Resource\Service\FileProcessingService->process#90 // TYPO3\CMS\Core\Resource\ProcessedFileRepository->add#127 // TYPO3\CMS\Core\Database\DatabaseConnection->exec_INSERTquery#131 // TYPO3\CMS\Core\Database\DatabaseConnection->debug#202
#4 Updated by Philipp Gampe 11 months ago
- File fake-jpeg.jpeg added
#5 Updated by Philipp Gampe 11 months ago
You need to enable preview images and reload the file list after upload.
You might only see this error if you have set DB debug >0.
#6 Updated by Alexander Opitz 11 months ago
- Subject changed from Column 'width' cannot be null to FAL Indexer for broken files: Column 'width' cannot be null
#7 Updated by Mathias Schreiber 7 months ago
- Target version set to 7.1 (Cleanup)
- Sprint Focus set to On Location Sprint
#8 Updated by Philipp Gampe 6 months ago
You might need to enable Display thumbnails.
#9 Updated by Philipp Gampe 6 months ago
- Status changed from Accepted to Rejected
The real issue is #64616. Closing is duplicate.