#105403f:image and cache busting issue
Description
Since version 13.4, the following fluid code:
<f:image src="{f:uri.resource(path: 'Images/logo.svg', extensionName: 'template')}" />
Creates an exception:
#1509741911 TYPO3Fluid\Fluid\Core\ViewHelper\Exception
Unable to render image tag in "pages:1": Folder "/_assets/862beb08718fcccbd31886444eef60f1/Images/logo.svg?1634931243/" does not exist.
When disabling the cache-busting in the uri.resource ViewHelper with (useCacheBusting=“false”) the issue is gone.
The problem is the <f:image> ViewHelper that cannot handle the URL with cacheBusting timestamp, in version 12 the same code works. Found while upgrading a version 12 project to version 13.</f:image>
Reviews 2
Related issues 2
History 1014
-
Garvin Hicking changed Related to #99203 <span data-processor="relativetime" data-value="2024-10-24T21:51:49+00:00" > 10/24/24, 21:51 </span>
-
Christian Ludwig changed Related to #105953 <span data-processor="relativetime" data-value="2025-01-16T20:24:37+00:00" > 01/16/25, 20:24 </span>
-
Christian Ludwig changed
Related to #105953<span data-processor="relativetime" data-value="2025-01-16T20:24:56+00:00" > 01/16/25, 20:24 </span> -
Christian Ludwig changed Related to #105953 <span data-processor="relativetime" data-value="2025-01-16T20:25:44+00:00" > 01/16/25, 20:25 </span>
-
Benni Mack commented and changed status
NewNeeds Feedback <span data-processor="relativetime" data-value="2025-04-09T17:08:28+00:00" > 04/09/25, 17:08 </span>Does this happen in FE or BE?
-
Mathias Brodala commented <span data-processor="relativetime" data-value="2026-01-19T08:53:51+00:00" > 01/19/26, 08:53 </span>
As mentioned quite a few times and in the docs, you must not use
f:imagefor anything but FAL resources.Package resources should be rendered normally:
<img src="{f:uri.resource(path: 'Images/logo.svg', extensionName: 'template')}"> -
Georg Ringer commented and changed status
Needs FeedbackClosed <span data-processor="relativetime" data-value="2026-03-10T04:17:58+00:00" > 03/10/26, 04:17 </span>closing as lack of feedback and alternatives possible
-
Gerrit Code Review pushed patch set 1 for main to change 95067 status
ClosedUnder Review <span data-processor="relativetime" data-value="2026-08-02T14:35:18+00:00" > 08/02/26, 14:35 </span> -
Gerrit Code Review pushed patch set 2 for main to change 95067 <span data-processor="relativetime" data-value="2026-08-02T17:24:18+00:00" > 08/02/26, 17:24 </span>
-
Gerrit Code Review pushed patch set 3 for main to change 95067 <span data-processor="relativetime" data-value="2026-08-26T07:55:10+00:00" > 08/26/26, 07:55 </span>
-
Gerrit Code Review pushed patch set 4 for main to change 95067 <span data-processor="relativetime" data-value="2026-08-26T08:12:01+00:00" > 08/26/26, 08:12 </span>
-
Helmut Hummel commented and changed status
Under ReviewNeeds Feedback <span data-processor="relativetime" data-value="2026-09-03T12:21:57+00:00" > 09/03/26, 12:21 </span>Frank Nägler wrote:
> Since version 13.4, the following fluid code:
><f:image src="{f:uri.resource(path: 'Images/logo.svg', extensionName: 'template')}" />From my understanding this Fluid code should not be supported by TYPO3 at all.
f:uri.resource creates an URI and <f:image src= should, if anything, take a resource identifier and not a Resource URI
-
Benni Mack commented and changed status
Needs FeedbackClosed <span data-processor="relativetime" data-value="2026-11-14T18:22:49+00:00" > 11/14/26, 18:22 </span>Thanks for the report, and sorry for the long silence.
Passing the output of
f:uri.resourceinto thesrcargument off:imagewas never a supported use case:f:uri.resourcereturns a public URI (including the cache-busting query string), whereassrcexpects a resource identifier – a FAL identifier, a file uid or a path – not a URI. That it worked in v12 was a coincidence of how the path was resolved.Also note that the cache-busting part of the URI is not a stable format: with https://review.typo3.org/c/Packages/TYPO3.CMS/+/97627 it can be replaced by event listeners (e.g. with a content hash) or omitted entirely, so a generated URI is not something
f:imagecan reliably resolve back to a file.There are two supported ways to achieve this:
1. If the image does not need any processing, render a plain image tag:
<img src="{f:uri.resource(path: 'Images/logo.svg', extensionName: 'template')}" alt="" />2. Since TYPO3 v14/v15,
f:image(as well asf:uri.image) can handle extension resources directly via their identifier, including processing (width, height, crop):<f:image src="EXT:template/Resources/Public/Images/logo.svg" alt="" />As both options cover the use case, I am closing this issue. If you think there is still a scenario which is not covered, please let us know and we can reopen.
but why should someone do that and not use the native img tag?