In this bugfix, a method has been added to check if the requested file exists on the S3 storage before trying to fetch a file for local processing or trying to extract metadata of the file.
This adjustment prevents errors in the TYPO3 logs while opening the file list, fetching the file for file processing, extracting metadata on the file and requesting the file from within the frontend.
With this changed behaviour, the ResourceStorage now can correctly mark a file as missing because the php is_file() method returned true if the $fileIdentifier was formatted correctly as a file identifier, and it was not checking if the file would exist on the storage.
This behaviour has only been added to the fileExists method, because S3 does not have folders, so adding the same headObject in the folderExists method would always get to the catch block and return false. The same behaviour as described on https://stackoverflow.com/a/17681486 still applies to S3 and its 'folders'.
In this bugfix, a method has been added to check if the requested file exists on the S3 storage before trying to fetch a file for local processing or trying to extract metadata of the file.
This adjustment prevents errors in the TYPO3 logs while opening the file list, fetching the file for file processing, extracting metadata on the file and requesting the file from within the frontend.
With this changed behaviour, the ResourceStorage now can correctly mark a file as missing because the php
is_file()method returned true if the$fileIdentifierwas formatted correctly as a file identifier, and it was not checking if the file would exist on the storage.This behaviour has only been added to the
fileExistsmethod, because S3 does not have folders, so adding the sameheadObjectin thefolderExistsmethod would always get to thecatchblock and return false. The same behaviour as described on https://stackoverflow.com/a/17681486 still applies to S3 and its 'folders'.