[BUGFIX] Image rendering of non-existing files throws exception 93/19393/2
authorOliver Hader <oliver@typo3.org>
Fri, 22 Mar 2013 09:31:29 +0000 (10:31 +0100)
committerOliver Hader <oliver.hader@typo3.org>
Wed, 27 Mar 2013 19:10:24 +0000 (20:10 +0100)
commitdddf13d4ed5211376e9725e429d02aa5b977da97
tree6ec7410b7ee3bd5285e4a8afb086a29e22baf07c
parent1c9901fea695bf10b3676366ef359add3c202bd5
[BUGFIX] Image rendering of non-existing files throws exception

Rendering an image that has no accordant file in a storage in
the frontend (e.g. in TypoScript) fails with an exception like
"Object with identifier xyz does not exist in storage".

A new ResourceDoesNotExistException is introduced to cover
files and folders and is thrown instead of RuntimeException.
This way, the exception is caught in the ContentObjectRenderer
and the frontend rendering just does not output the error,
which is logged instead.

Change-Id: I0affa15a8f0a50bf30a7176972994f209d18daf4
Fixes: #46535
Releases: 6.0, 6.1
Reviewed-on: https://review.typo3.org/19393
Reviewed-by: Oliver Hader
Tested-by: Oliver Hader
typo3/sysext/core/Classes/Resource/Exception/FileDoesNotExistException.php
typo3/sysext/core/Classes/Resource/Exception/FolderDoesNotExistException.php
typo3/sysext/core/Classes/Resource/Exception/ResourceDoesNotExistException.php [new file with mode: 0644]
typo3/sysext/core/Classes/Resource/ResourceFactory.php