#105847Generation of fallback files of non-web format fileExtensions uses wrong file extension
Description
When converting an image to a non-suitable target format, a fallback mechanism is in place which will use a ‘gif_or_jpeg’ method to format the output:
<f:image src="fileadmin/ImageViewHelperTest.jpg" width="200" fileExtension="tif" />
The expected filename result would be “ImageViewHelperTest.jpg” but instead “ImageViewHelperTest.tif” is returned.
The file contents contain the actual JPG target format (not TIF). Depending on how a webserver is configured and file extensions are used for MIME type matching, this would lead to a broken image.
The image extension should instead use the fallback file extension.
Tests which were added with #105846 showcase this behaviour. This bug probably exists in all TYPO3 versions, but set to supported v12 for now.
Reviews 2
Related issues 1
History 47
-
Garvin Hicking changed Related to #105846 <span data-processor="relativetime" data-value="2024-12-19T09:03:56+00:00" > 12/19/24, 09:03 </span>
-
Garvin Hicking commented <span data-processor="relativetime" data-value="2024-12-21T14:23:31+00:00" > 12/21/24, 14:23 </span>
-
Gerrit Code Review pushed patch set 3 for main to change 87567 status
AcceptedUnder Review <span data-processor="relativetime" data-value="2024-12-21T14:24:58+00:00" > 12/21/24, 14:24 </span> -
Gerrit Code Review pushed patch set 4 for main to change 87567 <span data-processor="relativetime" data-value="2025-01-02T13:50:41+00:00" > 01/02/25, 13:50 </span>
-
Gerrit Code Review pushed patch set 1 for 13.4 to change 87625 <span data-processor="relativetime" data-value="2025-01-02T16:26:38+00:00" > 01/02/25, 16:26 </span>
-
Garvin Hicking commented and changed status
Under ReviewResolved done0 %100 % <span data-processor="relativetime" data-value="2025-01-02T16:40:08+00:00" > 01/02/25, 16:40 </span>Applied in changeset commit:2455718e64da30ea616a0e1f6c6e07438a3d6fc0.
-
Benni Mack changed status
ResolvedClosed <span data-processor="relativetime" data-value="2025-12-02T14:27:31+00:00" > 12/02/25, 14:27 </span>
Please note: This faulty behaviour currently would only be triggerd by the new AVIF implemention, or in very rare edge-cases using the old ‘web’ pseudo-format, only when calling ->convert() manually in code.