TYPO3 Core

Is it the same as #45696 ?

I am not sure where the issue happens in #45696 ?
If I delete the file and browse to it in fileadmin?

This is only a change in fluid, so if the image is accessed via fluid then yes, otherwise not.

I think there should be some kind of logging if the file is missing.

I'm not sure, but I think that #45696 refers to frontend

Patch set 2 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/44796

Patch set 1 for branch TYPO3_6-2 of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/45122

Patch set 2 for branch TYPO3_6-2 of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/45122

Patch set 2 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/45123

Patch set 3 for branch TYPO3_6-2 of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/45122

Hmm, silently catching the exception, and doing nothing ... is this supposed to be a solution, or just a hack? ;)

maybe we should consider also for 6.2 the solution used upstream:

https://review.typo3.org/#/c/40212/6/typo3/sysext/fluid/Classes/Core/ViewHelper/AbstractViewHelper.php

I think this should also be fixed for at least 6.2 LTS? Target 7.6.1?? If you have multiple sites and you want to update them all this will be released in 2018.

Like to hear your thoughts about this.

Patch set 2 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/45166

Patch set 1 for branch TYPO3_6-2 of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/45170

Patch set 2 for branch TYPO3_6-2 of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/45170

@Christiaan Wiesenekker:
Please see applied patchsets for this ticket, the bugfix has also been backported and merged for 6.2, so it will be included in the next 6.2 release.

The bugfix ist not yet included in the current TYPO3 version 6.2.16

It is includeded. I checked the source code of the .zip file.
However the change only affects f:image and f:uri.image Viewhelpers.
It is still possible that other cases e.g. custom Viewhelpers or extensions (or other parts of the core) have that issue.