Review main Merged Breaking

90675[!!!][FEATURE] Introduce System Resource API to resolve files/assets

Helmut Hummel CR +2 V +2 Nightmare +5493 −1735 updated 10/28/25, 09:12

Commit message

This patch introduces a **System Resource API**
for resolving system resources and generating URIs for them.

The API provides objects as intermediate representations
of system resources and defines a canonical string format
for their representation.

This addresses several long-standing issues especially the problem
that when passing strings through different APIs,
each API previously had to check and validate what the string actually meant:

* whether it was an absolute file path or URL,
* a relative file path or URL,
* and relative to what?

At best, this led to scattered code for checking file existence,
prepending paths, detecting URI schemes, or handling `EXT:` syntax
all implemented in slightly different ways across the code base.

At worst, the meaning of strings could only be guessed,
not recognized at all, or misinterpreted
(e.g. a URL reused to construct a file system path,
leading to bugs such as #105205).

This not only resulted in error-prone code,
but also hindered the implementation of alternative
resource publishing strategies beyond symlinking a file
into a hashed folder within an `_assets` directory.

By introducing a dedicated API to:

1. resolve strings into objects, and
2. generate URIs from those objects,

we eliminate these shortcomings and enable the implementation
of new publishing and URL generation strategies.

The new API for generating URIs requires a request to be passed,
as it uses the request to determine the absolute URL prefix.
This requirement is now explicit, unlike in API calls
such as `GeneralUtility::locationHeaderUrl`, which use the superglobal request
and thereby undermine proper request/response encapsulation.

When no request can be passed (e.g. in CLI contexts),
`null` can be used instead.
In that case, `/` is assumed as the URL prefix.
All generated URLs therefore have an absolute path,
and instead of a plain string, a `UriInterface`-implementing
object is returned.

This change not only introduces the new API
but also refactors all code locations where
resource identifiers could be passed into the system.

Every URL generated from provided resources now
originates from a single code path.

As a result:

- fixing bugs will address all usages simultaneously,
- implementing new features or deprecating legacy behavior can be done in one place.

This change primarily affects code related
to **public resources** and URI generation.
Areas that deal exclusively with **private resources**
such as Fluid templates or language files
will be addressed in future changes.

The object representation of resources already reflects
this distinction by providing separate objects for
public and private resources, though further additions
will be required when extending the system
to the remaining areas.

Review

  • Code review CR +2 Done
    • Helmut Hummel +2
    • Garvin Hicking +1
    • Simon Praetorius +1
    • Christian Kuhn +1
    • Benni Mack +1
  • Verified V +2 Done
    • Helmut Hummel +2
    • Garvin Hicking +1
    • Christian Kuhn +1
    • Benni Mack +1
    • core-ci +1 CI

Issues 5

Files 192

Show 172 more files

Review log 129211

Show 105186 earlier messages
  1. Helmut Hummel uploaded patch set 1 09/12/25, 12:51

  2. Helmut Hummel marked it work in progress 09/12/25, 12:51

  3. core-ci voted on patch set 1 V -1 09/12/25, 13:04 Core CI is not happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/84915

  4. Helmut Hummel uploaded patch set 2 V -1 09/17/25, 21:09

  5. Helmut Hummel uploaded patch set 3 09/17/25, 21:16

  6. core-ci voted on patch set 2 V -1 09/17/25, 21:30 Core CI is not happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/85097

  7. core-ci voted on patch set 3 V -1 09/17/25, 21:34 Core CI is not happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/85101

  8. Helmut Hummel uploaded patch set 4 V -1 09/22/25, 21:26

  9. Helmut Hummel uploaded patch set 5 09/22/25, 21:27

  10. core-ci voted on patch set 4 V -1 09/22/25, 21:39 Core CI is not happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/85348

  11. core-ci voted on patch set 5 V -1 09/22/25, 21:42 Core CI is not happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/85349

  12. Helmut Hummel uploaded patch set 6 V -1 09/29/25, 07:21

  13. core-ci voted on patch set 6 V -1 09/29/25, 07:32 Core CI is not happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/85682

  14. Helmut Hummel uploaded patch set 7 V -1 10/01/25, 20:40

  15. core-ci voted on patch set 7 V -1 10/01/25, 20:49 Core CI is not happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/85841

  16. Helmut Hummel uploaded patch set 8 V -1 10/02/25, 08:03

  17. Helmut Hummel rebased onto patch set 9 10/02/25, 08:04

  18. core-ci voted on patch set 8 V -1 10/02/25, 08:14 Core CI is not happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/85880

  19. core-ci voted on patch set 9 V -1 10/02/25, 08:15 Core CI is not happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/85881

  20. Helmut Hummel uploaded patch set 10 V -1 10/02/25, 09:17

  21. core-ci voted on patch set 10 V -1 10/02/25, 09:26 Core CI is not happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/85891

  22. Helmut Hummel uploaded patch set 11 V -1 10/02/25, 09:46

  23. core-ci voted on patch set 11 V -1 10/02/25, 09:56 Core CI is not happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/85894

  24. Helmut Hummel uploaded patch set 12 V -1 10/02/25, 11:00

  25. core-ci voted on patch set 12 V -1 10/02/25, 11:14 Core CI is not happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/85904

  26. Helmut Hummel uploaded patch set 13 V -1 10/02/25, 11:45

  27. core-ci voted on patch set 13 V -1 10/02/25, 11:58 Core CI is not happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/85914

  28. Helmut Hummel uploaded patch set 14 V -1 10/02/25, 13:11

  29. core-ci voted on patch set 14 V -1 10/02/25, 13:24 Core CI is not happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/85919

  30. Helmut Hummel uploaded patch set 15 V -1 10/07/25, 19:26

  31. core-ci voted on patch set 15 V -1 10/07/25, 19:35 Core CI is not happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/86182

  32. Helmut Hummel uploaded patch set 16 V -1 10/07/25, 21:01

  33. core-ci voted on patch set 16 V +1 10/07/25, 21:08 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/86189

  34. Helmut Hummel uploaded patch set 17 V +1 10/08/25, 08:27

  35. core-ci voted on patch set 17 V -1 10/08/25, 08:35 Core CI is not happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/86210

  36. Helmut Hummel uploaded patch set 18 V -1 10/08/25, 10:41

  37. core-ci voted on patch set 18 V +1 10/08/25, 10:48 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/86219

  38. Helmut Hummel uploaded patch set 19 V +1 10/12/25, 19:52

  39. core-ci voted on patch set 19 V -1 10/12/25, 19:59 Core CI is not happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/86495

  40. Helmut Hummel uploaded patch set 20 V -1 10/12/25, 21:39

  41. core-ci voted on patch set 20 V +1 10/12/25, 21:46 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/86496

  42. Helmut Hummel uploaded patch set 21 V +1 10/12/25, 22:02

  43. core-ci voted on patch set 21 V -1 10/12/25, 22:08 Core CI is not happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/86497

  44. Helmut Hummel uploaded patch set 22 V -1 10/12/25, 22:33

  45. Helmut Hummel marked it ready for review 10/12/25, 22:33

  46. Helmut Hummel uploaded patch set 23 10/12/25, 22:36

  47. core-ci voted on patch set 22 V -1 10/12/25, 22:41 Core CI is not happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/86498

  48. core-ci voted on patch set 23 V +1 10/12/25, 22:43 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/86499

  49. Benni Mack commented on patch set 23 10/13/25, 06:14

    FakeProjectPackage.php:41

    smart use!

    UriResource.php:27

    is it a UriResource or a ResourceUri :)

    ResourceViewHelper.php:25

    I'd assume this is just a systemResource VH now?

    TypoScriptFrontendController.php:207

    this is a good example: Reading the docs, I dont fully understand if it's OK to use the EXT: syntax anymore and in what places exactly.
  50. Oliver Hader commented on patch set 23 10/13/25, 09:38

    SystemResourceUri.php:41

    Should we be explicitly distinguish extension from package here? e.g. * `t3://resource?extension=core` * `t3://resource?package=typo3/cms-core` (actually `...?package=typo3%2Fcms-core` url-encoded)
  51. Oliver Hader commented on patch set 23 10/13/25, 10:14

    FalFileUri.php:28

    In case `uid` is numeric-only, it probably should be `%1$d`

    SystemUri.php:27

    Our `Uri` implementation is very HTTP-centric. Maybe we should have a dedicated implementation for non-HTTP cases (thus, not extending `TYPO3\CMS\Core\Http\Uri`, but still being compatible to `UriInterface`).

    SystemUri.php:66

    I don't understand that condition yet (maybe I'll find a corresponding counterpart later during the review).

    FakeProjectPackage.php:29

    `Fake` does sound "suspicious" to me 😊 What about `Virtual`, `Emulated`, `Artificial`, ...?
  52. Helmut Hummel uploaded patch set 24 V +1 10/14/25, 13:04

  53. core-ci voted on patch set 24 V -1 10/14/25, 13:17 Core CI is not happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/86630

  54. Helmut Hummel uploaded patch set 25 V -1 10/14/25, 15:41

  55. core-ci voted on patch set 25 V -1 10/14/25, 15:50 Core CI is not happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/86651

  56. Helmut Hummel uploaded patch set 26 V -1 10/14/25, 15:54

  57. core-ci voted on patch set 26 V +1 10/14/25, 16:01 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/86652

  58. Garvin Hicking commented on patch set 26 CR -1 10/14/25, 17:58

    On it for some ReST changes
  59. Garvin Hicking uploaded patch set 27 CR -1 V +1 10/14/25, 18:34

  60. Garvin Hicking commented on patch set 27 10/14/25, 18:39

    Reply

    Done - hope I conserved your intention everywhere, otherwise feel free to revert wherever I made a mistake

    Feature-107537-SystemResourceAPIForSystemFileAccessAndPublicUriGeneration.rst:50

    As a reader, this is a bit confusing to me, that I have three possibilities here to reference a resource. I think we should state "EXT:" is the legacy notation which will be dropped in the future (or remain as "legacy" for...long?). Why though is "PKG:ext_name" something we want to support then? This feels like another upcoming legacy to me, when I believe we probably want to promote the `PKG:vendor/name` syntax I guess? Another idea for terminology came to my mind when writing this, how about using `EXT<vendor/name>:/Resources...`? We could then parse this on `EXT<` as a prefix, and people might not need to get used to "PKG", and keeping around the "non-composer" EXT:... syntax would be more understandable (sorry if I open up pandoras box of "naming things" again, feel free to resolve if this discussion is annoying).

    Feature-107537-SystemResourceAPIForSystemFileAccessAndPublicUriGeneration.rst:74

    This is not yet mentioned in the breaking ReST I believe?

    Feature-107537-SystemResourceAPIForSystemFileAccessAndPublicUriGeneration.rst:91

    I did not properly understand this. You want to state something like "Missing files in the scope of the legacy exemptions mentioned above will not add a cache busting URI argument"? Maybe this can be rephrased.
  61. core-ci voted on patch set 27 V -1 10/14/25, 18:43 Core CI is not happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/86654

  62. Helmut Hummel uploaded patch set 28 V -1 10/14/25, 19:11

  63. core-ci voted on patch set 28 V -1 10/14/25, 19:20 Core CI is not happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/86655

  64. Helmut Hummel commented on patch set 28 10/14/25, 19:25

    SystemResourceUri.php:41 Reply

    the syntax changed. but in any case, in current state, no, we can't distinguish, as the composer names are always aliased to the extension key. so PackageManager->getPackage() will always return the same package for both, the key and the composer name. also: we can't really promote composer names only, as there is non composer mode, where there sometimes are no composer names

    FakeProjectPackage.php:29 Reply

    thanks. went for Virtual

    FakeProjectPackage.php:41 Reply

    😊

    Feature-107537-SystemResourceAPIForSystemFileAccessAndPublicUriGeneration.rst:50 Reply

    as long as there is no composer mode and composer.json files for extensions are not mandatory for this mode, we can not easily promote composer names. if we manage to achieve enforced composer.json in all modes, then yes, we can go all in on composer names
  65. Helmut Hummel uploaded patch set 29 V -1 10/14/25, 20:23

  66. core-ci voted on patch set 29 V +1 10/14/25, 20:30 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/86658

  67. Helmut Hummel rebased onto patch set 30 V +1 10/14/25, 20:33

  68. core-ci voted on patch set 30 V -1 10/14/25, 20:41 Core CI is not happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/86659

  69. Helmut Hummel rebased onto patch set 31 V -1 10/14/25, 20:42

  70. core-ci voted on patch set 31 V +1 10/14/25, 20:48 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/86660

  71. Helmut Hummel uploaded patch set 32 V +1 10/15/25, 07:56

  72. Garvin Hicking commented on patch set 31 10/15/25, 07:57

    Feature-107537-SystemResourceAPIForSystemFileAccessAndPublicUriGeneration.rst:50 Reply

    I'm sorry then, I really thought composer.json files were mandatory even for non-compose mode for internal discovery. I always read https://docs.typo3.org/m/typo3/reference-coreapi/main/en-us/ExtensionArchitecture/FileStructure/ComposerJson.html#about-the-composer-json-file as a very hard recommendation. Couldn't we take this step in v14 now and make that file mandatory as a breaking change? This would make us bear considerably less cruft with a fresh new API like this one here. Maybe we could even internally create a "fake" (hehe) composer.json in case it's missing which just bears an internal composer name like "typo3-project/[extensionkey]"? Then such a scope could be used for resource links with `EXT<typo3-project/my_extension_key>:/Resources/...` and it wouldn't even sound bad to classic users with such a generic typo3-project fake key?
  73. core-ci voted on patch set 32 V +1 10/15/25, 08:03 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/86690

  74. Helmut Hummel uploaded patch set 33 V +1 10/15/25, 13:13

  75. core-ci voted on patch set 33 V -1 10/15/25, 13:27 Core CI is not happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/86728

  76. Helmut Hummel uploaded patch set 34 V -1 10/15/25, 19:46

  77. core-ci voted on patch set 34 V -1 10/15/25, 19:59 Core CI is not happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/86765

  78. Helmut Hummel uploaded patch set 35 V -1 10/16/25, 12:51

  79. core-ci voted on patch set 35 V -1 10/16/25, 13:05 Core CI is not happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/86813

  80. Helmut Hummel uploaded patch set 36 V -1 10/16/25, 15:49

  81. core-ci voted on patch set 36 V -1 10/16/25, 16:04 Core CI is not happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/86830

  82. Christian Kuhn commented on patch set 36 10/19/25, 14:25

    huge one. i read through it, but must admit i didn't grasp all details. i also have some dedicated questions, for instance related to fal getPublicUrl() - i recently stumbled there hard since this it one of the places that *obviously* needs the request (but does not receive it) and currently relies on quirky logic to circumvent the situation. reading the implications of getPublicUrl() alone, i came to the same conclusion we'll have to have a construct that can generate uri/url's based on given request, plus that FAL itself needs to be freed from this job entirely. i'm very glad this change materialized taking care of this need. also, i'm currently actively fiddling with tsfe absRefPrefix and i'd need at least an intermediate solution, somehow depending on how/if/when this change makes it. maybe we could align in a voice chat regarding that detail?

    ResourceUtility.php:38

    considering the fact this method is used exactly once and only in MainController, and since adminpanel is FE request related in many places, I think we can very well make $request non-optional and "soft break" here, maybe even without further notice. and while we are at it, we could then make this a non-static service and get the proper service api injected instead of using the intermediate method from PathUtility, or is this too early for your taste?

    AbstractFormEngineAjaxController.php:63

    this abstract could use inject* methods instead of makeInstance(), can't it? i'm fine if you say "this too early / too much with this patch", though.
  83. Helmut Hummel uploaded patch set 37 V -1 10/19/25, 18:35

  84. core-ci voted on patch set 37 V -1 10/19/25, 18:49 Core CI is not happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/87021

  85. Helmut Hummel uploaded patch set 38 V -1 10/19/25, 18:50

  86. core-ci voted on patch set 38 V -1 10/19/25, 19:06 Core CI is not happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/87022

  87. Helmut Hummel uploaded patch set 39 V -1 10/19/25, 19:31

  88. core-ci voted on patch set 39 V -1 10/19/25, 19:46 Core CI is not happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/87023

  89. Helmut Hummel uploaded patch set 40 V -1 10/19/25, 20:22

  90. core-ci voted on patch set 40 V -1 10/19/25, 20:37 Core CI is not happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/87024

  91. Helmut Hummel uploaded patch set 41 V -1 10/19/25, 20:57

  92. core-ci voted on patch set 41 V -1 10/19/25, 21:11 Core CI is not happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/87025

  93. Helmut Hummel uploaded patch set 42 V -1 10/19/25, 21:35

  94. Helmut Hummel uploaded patch set 43 10/19/25, 21:40

  95. Helmut Hummel uploaded patch set 44 10/19/25, 21:44

  96. core-ci voted on patch set 42 V -1 10/19/25, 21:46 Core CI is not happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/87026

  97. core-ci voted on patch set 44 V -1 10/19/25, 22:00 Core CI is not happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/87028

  98. Helmut Hummel uploaded patch set 45 V -1 10/20/25, 08:09

  99. core-ci voted on patch set 45 V -1 10/20/25, 08:30 Core CI is not happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/87057

  100. Helmut Hummel uploaded patch set 46 V -1 10/20/25, 09:05

  101. core-ci voted on patch set 46 V -1 10/20/25, 09:26 Core CI is not happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/87063

  102. Helmut Hummel uploaded patch set 47 V -1 10/20/25, 10:13

  103. core-ci voted on patch set 47 V -1 10/20/25, 10:40 Core CI is not happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/87068

  104. Helmut Hummel uploaded patch set 48 V -1 10/20/25, 11:32

  105. core-ci voted on patch set 48 V -1 10/20/25, 11:40 Core CI is not happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/87071

  106. Helmut Hummel uploaded patch set 49 V -1 10/20/25, 12:45

  107. core-ci voted on patch set 49 V +1 10/20/25, 12:52 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/87078

  108. Helmut Hummel uploaded patch set 50 V +1 10/20/25, 13:44

  109. core-ci voted on patch set 50 V -1 10/20/25, 13:57 Core CI is not happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/87084

  110. Helmut Hummel uploaded patch set 51 V -1 10/20/25, 14:35

  111. Helmut Hummel uploaded patch set 52 10/20/25, 14:35

  112. Helmut Hummel uploaded patch set 53 10/20/25, 14:38

  113. core-ci voted on patch set 52 V -1 10/20/25, 14:49 Core CI is not happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/87090

  114. core-ci voted on patch set 53 V -1 10/20/25, 14:49 Core CI is not happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/87091

  115. Helmut Hummel uploaded patch set 54 V -1 10/20/25, 15:59

  116. Helmut Hummel uploaded patch set 55 10/20/25, 16:01

  117. core-ci voted on patch set 55 V +1 10/20/25, 16:11 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/87096

  118. core-ci voted on patch set 54 V -1 10/20/25, 16:15 Core CI is not happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/87095

  119. Helmut Hummel uploaded patch set 56 V +1 10/21/25, 06:10

  120. Helmut Hummel commented on patch set 56 10/21/25, 06:13

    Feature-107537-SystemResourceAPIForSystemFileAccessAndPublicUriGeneration.rst:50 Reply

    Making composer.json required for classic mode would be a valuable change and the proposal here would indeed then benefit from some gained clarity. That still is some other cup of tea and not strictly tied to this proposal. However, I think you have valid concerns and, though not feasible to strictly enforce this, we can recommend using Composer package names for the PKG syntax. I will adapt the tests and docs accordingly
  121. core-ci voted on patch set 56 V -1 10/21/25, 06:24 Core CI is not happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/87135

  122. Helmut Hummel uploaded patch set 57 V -1 10/21/25, 06:42

  123. core-ci voted on patch set 57 V -1 10/21/25, 06:49 Core CI is not happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/87138

  124. Helmut Hummel commented on patch set 57 10/21/25, 06:49

    ResourceUtility.php:38 Reply

    Yes, absolutely considered this option. However, doing so for (currently) 21 usages takes significant time and also increases the size of this patch significantly. Therefore I propose to postpone this refactoring, which then remains a fun and relatively easy to do task to tackle usages one by one

    AbstractFormEngineAjaxController.php:63 Reply

    Done

    SystemResourceUri.php:41 Reply

    this basically is the same comment as from Garvin, so I adapted the PKG: syntax to always only use composer names (except for classic projects with extensions without composer name)

    Feature-107537-SystemResourceAPIForSystemFileAccessAndPublicUriGeneration.rst:74 Reply

    Done

    Feature-107537-SystemResourceAPIForSystemFileAccessAndPublicUriGeneration.rst:91 Reply

    Done
  125. Helmut Hummel commented on patch set 57 10/21/25, 07:02

    FalFileUri.php:28 Reply

    fixed, by changed identifier syntax

    SystemUri.php:27 Reply

    Fixed by changing the syntax and the naming and the implementation

    SystemUri.php:66 Reply

    this overly complicated condition was due to the misuse of our Uri implementation for identifiers. this is fixed by changing the identifier syntax

    UriResource.php:27 Reply

    It still is a resource. This abiguity is fixed by changed identifiers and naming for them in code

    ResourceViewHelper.php:25 Reply

    Done

    TypoScriptFrontendController.php:207 Reply

    some ambiguity is now resolved by using composer names only for PKG syntax and also by using the API throughout all user facing resource references. This means: EXT syntax will continue to work and at the same time PKG syntax will work in all places. I'll try my best to explain this in more detail in the docs
  126. Helmut Hummel commented on patch set 57 10/21/25, 07:07

    AbstractFormEngineAjaxController.php:63 Reply

    I stand corrected here. I switched to PathUtility because of https://git.typo3.org/typo3/CI/cms/-/jobs/4868973 Let's tackle this in an additional effort
  127. Helmut Hummel uploaded patch set 58 V -1 10/21/25, 07:14

  128. core-ci voted on patch set 58 V -1 10/21/25, 07:24 Core CI is not happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/87141

  129. Helmut Hummel uploaded patch set 59 V -1 10/21/25, 07:32

  130. core-ci voted on patch set 59 V +1 10/21/25, 07:41 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/87144

  131. Helmut Hummel uploaded patch set 60 V +1 10/21/25, 07:51

  132. core-ci voted on patch set 60 V -1 10/21/25, 08:04 Core CI is not happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/87146

  133. Helmut Hummel uploaded patch set 61 V -1 10/21/25, 08:22

  134. core-ci voted on patch set 61 V +1 10/21/25, 08:35 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/87153

  135. Helmut Hummel uploaded patch set 62 V +1 10/21/25, 10:21

  136. core-ci voted on patch set 62 V -1 10/21/25, 10:33 Core CI is not happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/87162

  137. Helmut Hummel uploaded patch set 63 V -1 10/21/25, 11:09

  138. core-ci voted on patch set 63 V -1 10/21/25, 11:23 Core CI is not happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/87173

  139. Helmut Hummel uploaded patch set 64 V -1 10/21/25, 18:37

  140. core-ci voted on patch set 64 V +1 10/21/25, 18:44 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/87196

  141. Helmut Hummel uploaded patch set 65 V +1 10/22/25, 10:02

  142. Helmut Hummel rebased onto patch set 66 10/22/25, 10:02

  143. Markus Klein commented on patch set 66 10/22/25, 10:18

    "than": is "like" meant here actually?
    will?
  144. core-ci voted on patch set 65 V -1 10/22/25, 10:20 Core CI is not happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/87234

  145. Markus Klein commented on patch set 66 10/22/25, 10:21

    .gitignore:7

    Not sure about this line and the 2 following. IMO none of these are needed. the .gitkeep is added to version control once and then not affected by the ignore file
  146. core-ci voted on patch set 66 V -1 10/22/25, 10:22 Core CI is not happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/87235

  147. Helmut Hummel uploaded patch set 67 V -1 10/22/25, 11:01

  148. Helmut Hummel commented on patch set 67 10/22/25, 11:03

    Reply

    other than, I'd say this is correct, no?

    Reply

    I WILL rewrite the commit message, stay tuned 😊
  149. Helmut Hummel commented on patch set 67 10/22/25, 11:06

    .gitignore:7 Reply

    to my understanding this is needed. what I want is: exclude everything, except a few files. but I can remove this from here and create a separate patch, as this isn't some key thing in this change
  150. Markus Klein commented on patch set 67 10/22/25, 11:08

    Reply

    then it should be "…of resource publishing strategies other than symlinking…" (but I'm no English teacher :-D )
  151. core-ci voted on patch set 67 V +1 10/22/25, 11:09 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/87245

  152. Markus Klein commented on patch set 67 10/22/25, 11:09

    .gitignore:7 Reply

    Normally I'd say "keep it", but this change is already so big that it's probably best to move this out. Thanks.
  153. Helmut Hummel uploaded patch set 68 V +1 10/22/25, 18:36

  154. core-ci voted on patch set 68 V -1 10/22/25, 18:43 Core CI is not happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/87288

  155. Helmut Hummel uploaded patch set 69 V -1 10/22/25, 19:41

  156. core-ci voted on patch set 69 V +1 10/22/25, 19:56 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/87295

  157. Helmut Hummel uploaded patch set 70 V +1 10/23/25, 06:19

  158. core-ci voted on patch set 70 V +1 10/23/25, 06:28 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/87374

  159. Benni Mack uploaded patch set 71 V +1 10/23/25, 11:08

  160. core-ci voted on patch set 71 V +1 10/23/25, 11:18 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/87406

  161. Helmut Hummel uploaded patch set 72 V +1 10/23/25, 12:08

  162. Helmut Hummel commented on patch set 72 10/23/25, 12:09

    Reply

    done
  163. Helmut Hummel uploaded patch set 73 10/23/25, 12:15

  164. core-ci voted on patch set 72 V +1 10/23/25, 12:16 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/87413

  165. Helmut Hummel commented on patch set 73 10/23/25, 12:21

    Reply

    done
  166. Helmut Hummel uploaded patch set 74 10/23/25, 12:23

  167. core-ci voted on patch set 73 V -1 10/23/25, 12:24 Core CI is not happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/87414

  168. Helmut Hummel uploaded patch set 75 10/23/25, 12:24

  169. Helmut Hummel uploaded patch set 76 10/23/25, 12:31

  170. core-ci voted on patch set 74 V -1 10/23/25, 12:32 Core CI is not happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/87416

  171. core-ci voted on patch set 75 V -1 10/23/25, 12:34 Core CI is not happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/87417

  172. core-ci voted on patch set 76 V +1 10/23/25, 12:38 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/87418

  173. Helmut Hummel uploaded patch set 77 V +1 10/23/25, 12:41

  174. core-ci voted on patch set 77 V +1 10/23/25, 12:50 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/87420

  175. Helmut Hummel uploaded patch set 78 V +1 10/23/25, 12:54

  176. core-ci voted on patch set 78 V +1 10/23/25, 13:02 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/87424

  177. Garvin Hicking uploaded patch set 79 V +1 10/24/25, 18:37

  178. core-ci voted on patch set 79 V -1 10/24/25, 18:50 Core CI is not happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/87530

  179. Helmut Hummel uploaded patch set 80 V -1 10/25/25, 10:03

  180. Helmut Hummel uploaded patch set 81 10/25/25, 10:05

  181. Helmut Hummel uploaded patch set 82 10/25/25, 10:08

  182. core-ci voted on patch set 80 V -1 10/25/25, 10:18 Core CI is not happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/87565

  183. core-ci voted on patch set 81 V -1 10/25/25, 10:19 Core CI is not happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/87566

  184. core-ci voted on patch set 82 V -1 10/25/25, 10:20 Core CI is not happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/87567

  185. Helmut Hummel uploaded patch set 83 10/25/25, 10:25

    Copied Votes: * Verified-1 (copy condition: "**changekind:NO_CHANGE**")
  186. core-ci voted on patch set 83 V -1 10/25/25, 10:37 Core CI is not happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/87568

  1. Helmut Hummel uploaded patch set 84 V -1 10/25/25, 10:53

  2. core-ci voted on patch set 84 V +1 10/25/25, 11:00 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/87570

  3. Benni Mack voted on patch set 84 CR +1 V +1 10/25/25, 11:12

  4. Christian Kuhn commented on patch set 84 CR -1 10/25/25, 11:30

    on it.
  5. Garvin Hicking commented on patch set 84 10/25/25, 12:56

    Deprecation-107537-getPublicResourcesWebPath.rst:62

    Should we explicitly say "please do not use $GLOBALS['TYPO3_REQUEST']"? And maybe also give an example how to "create" a fake request for CLI usage, utilizing a specific site?
  6. Helmut Hummel commented on patch set 84 10/25/25, 13:18

    Deprecation-107537-getPublicResourcesWebPath.rst:62 Reply

    Both are good advice, yet they are not specifically related to this change imho. Especially for CLI usage, we should actually work on API to create a request and site from a given --site argument, as many already existing core commands would benefit from it already
  7. Garvin Hicking commented on patch set 84 10/25/25, 13:46

    Deprecation-107537-getPublicResourcesWebPath.rst:62 Reply

    About the second thing, yes, definitely. However I'm a bit afraid that people might think "Hm, whats $request?! Let me use the global one then". I think it would help to mention this at this place (unless you think using the global var is fine, too - I can't tell).
  8. Garvin Hicking commented on patch set 84 10/25/25, 14:23

    Some doc notes - I love what you wrote up, this is very detailed and helpful. I did not want to push over the patch while others review/vote.

    Breaking-107537-UrlGenerationSystemResources.rst:23 Unresolved

    This bullet point has no later details with an example or "affected installations". I must admit as a reader I wouldn't immediately know what is meant with that to judge if I'm affected and it sounds a bit serious ;). Is this when using `f:uri.image src=` or `f:image src` I suppose, then we could maybe add this there? I would suppose if I had a directory like "/aws-mirror" set as a FAL storage (outside "fileadmin") and then used `f:image src="/aws-mirror/somefile.jpg"` this worked before, but now no longer works? We also don't have a suggestion/migration mentioned for this bulletpoint on what to do in such cases, unless I'm missing something?

    Breaking-107537-UrlGenerationSystemResources.rst:30

    ```suggestion .. _breaking-107537-gettext-path: getText "path" in TypoScript ``` Having anchors here will allow us to reference to that easily, which might be helpful for future pointers of the docs

    Breaking-107537-UrlGenerationSystemResources.rst:55

    ```suggestion .. _breaking-107537-fluid-uri-resource: f:uri.resource view helper in Fluid ```

    Breaking-107537-UrlGenerationSystemResources.rst:73

    ```suggestion .. _breaking-107537-cache-busting: All generated URLs now contain cache busting ```

    Breaking-107537-UrlGenerationSystemResources.rst:79

    ```suggestion .. _breaking-107537-query-strings: Additional query strings applied to the resource identifier ```

    Breaking-107537-UrlGenerationSystemResources.rst:105

    ```suggestion .. _breaking-107537-impact-gettext-path: getText "path" in TypoScript ```

    Breaking-107537-UrlGenerationSystemResources.rst:115

    ```suggestion .. _breaking-107537-impact-fluid-uri-resource: f:uri.resource view helper in Fluid ```

    Breaking-107537-UrlGenerationSystemResources.rst:121

    ```suggestion .. _breaking-107537-impact-cache-busting: All generated URLs now contain cache busting ```

    Breaking-107537-UrlGenerationSystemResources.rst:127

    ```suggestion .. _breaking-107537-impact-query-strings: Additional query strings applied to the resource identifier ```

    Deprecation-107537-CreateVersionNumberedFileName.rst:62

    I think for consistency, the same note about $request can be null like in the other deprecation could be stated here.

    Deprecation-107537-FilePathSanitizer.rst:50

    This might not have had the `$request` passed in before?

    Deprecation-107537-FilePathSanitizer.rst:75

    I think for consistency, the same note about `$request can be null` like in the other deprecation could be stated here.

    Deprecation-107537-GetDataPath.rst:14

    ```suggestion TypoScript :typoscript:`getData` has two ways to get a URL for a system resource, ```

    Deprecation-107537-getPublicResourcesWebPath.rst:6

    ```suggestion Deprecation: #107537 - `TYPO3\CMS\Core\Utility\PathUtility::getPublicResourceWebPath` ``` Otherwise it gets munged to `TYPO3CMSCoreUtilityPathUtility` (also please adjust length of the `===...` for two more, gerrit suggestions can only span one row)

    Feature-107537-SystemResourceAPIForSystemFileAccessAndPublicUriGeneration.rst:62

    ```suggestion #. composer name of the package (also possible for "classic mode" when using extensions that contain a :file:`composer.json`) ``` We could mention something like this to indicate that a package can have a composer name, even when the project itself runs in classic mode (right?)

    Feature-107537-SystemResourceAPIForSystemFileAccessAndPublicUriGeneration.rst:74

    ```suggestion An app resource is a file or folder within your TYPO3 installation. ```

    Feature-107537-SystemResourceAPIForSystemFileAccessAndPublicUriGeneration.rst:86

    ```suggestion it can be configured to be a different directory (e.g. `web`, `html` or `htdocs`). In that case, the correct public ``` Maybe mentioning these other well-known alternatives helps to understand.

    Feature-107537-SystemResourceAPIForSystemFileAccessAndPublicUriGeneration.rst:92

    ```suggestion While users are encouraged to prefer using package and app resources, ```

    Feature-107537-SystemResourceAPIForSystemFileAccessAndPublicUriGeneration.rst:160

    ```suggestion The :php:`TYPO3\CMS\Core\SystemResource\SystemResourceFactory` and an implementation of a system resource publisher is injected via ``` (this will allow the rendered doc page directly link to the API of the docs)

    Feature-107537-SystemResourceAPIForSystemFileAccessAndPublicUriGeneration.rst:162

    ```suggestion the interface :php:`TYPO3\CMS\Core\SystemResource\Publishing\SystemResourcePublisherInterface`. ```

    Feature-107537-SystemResourceAPIForSystemFileAccessAndPublicUriGeneration.rst:165

    ```suggestion In the future, different publishing strategies might be implemented, e.g. directly ```

    Feature-107537-SystemResourceAPIForSystemFileAccessAndPublicUriGeneration.rst:166

    ```suggestion publishing resources to a CDN and then generating CDN URIs directly. In one TYPO3 installation ```

    Feature-107537-SystemResourceAPIForSystemFileAccessAndPublicUriGeneration.rst:168

    ```suggestion when the interface is referenced. ```

    Feature-107537-SystemResourceAPIForSystemFileAccessAndPublicUriGeneration.rst:185

    ```suggestion Currently only the `<f:uri.resource>` ViewHelper accepts such resource objects, but more ```

    Feature-107537-SystemResourceAPIForSystemFileAccessAndPublicUriGeneration.rst:245

    ```suggestion public resource folders or files. ```

    Feature-107537-SystemResourceAPIForSystemFileAccessAndPublicUriGeneration.rst:247

    ```suggestion * Using this API in all areas, that consume private resources, most notably Fluid template files. ```

    Feature-107537-SystemResourceAPIForSystemFileAccessAndPublicUriGeneration.rst:250

    ```suggestion like Fluid templates, CSS files, logos, images, or even complete themes. ```
  9. Simon Praetorius commented on patch set 84 10/25/25, 14:37

    AbstractSvgIconProvider.php:82 Unresolved

    in the original code, there was a todo to deprecate certain variants. was this left out intentionally? And when would isExtensionPath() be true here?

    ImportMap.php:269 Unresolved

    maybe split into two lines and/or explain what is happening here and why? I'd guess that a public path without leading / is needed here?

    DefaultSystemResourceUriGenerator.php:76 Unresolved

    should the port also be added here if set?

    SystemResourceIdentifierFactoryTest.php:88 Unresolved

    these values are not used, are they?

    ResourceViewHelper.php:61

    should we trigger a deprecation then?
  10. Garvin Hicking commented on patch set 84 10/25/25, 15:27

    PageRenderer.php:2022 Unresolved

    Is "Url" right here or should it be "Uri"?

    CanNotResolveSystemResourceException.php:23 Unresolved

    May be personal taste ofc, but I think "UnresolvableSystemResourceException" would fit better with other exceptions in TYPO3 core

    SystemResourceIdentifierFactory.php:52

    ```suggestion throw new InvalidSystemResourceIdentifierException(sprintf('Can not resolve URI %s', $resourceIdentifier), 1758700314); ```

    SystemResourceIdentifierFactory.php:106

    ```suggestion throw new InvalidSystemResourceIdentifierException(sprintf('Can not create system URI from "%s"', $extensionPath), 1758884297, $e); ```

    SystemResourceIdentifierFactory.php:127

    ```suggestion throw new InvalidSystemResourceIdentifierException(sprintf('Can not create system URI. Unknown package "%s"', $packageKey), 1760989723, $e); ```

    DefaultSystemResourcePublisher.php:55

    ```suggestion throw new CanNotGenerateUriException(sprintf('Can not generate URI for an unpublished resource %s', $publicResource), 1761211273); ```

    DummyFileCreationService.php:25

    Nice and helpful one! :)

    ResourceViewHelper.php:41 Unresolved

    I find the new example a bit confusing because it uses f:resource() here and f:uri.resource only later; my first thought was I have an "identifier" attribute on f:uri.resource. So this viewhelper more shows the use of 'f:resource' and not 'f:uri.resource'. Not sure right now if two examples would help or if an additional sentence could mention that using 'f:resource' here for chaining is useful.
  11. Garvin Hicking commented on patch set 84 10/25/25, 15:37

    I tried to test this. My v14 setup is a rather special one: I use a wrapped composer setup, and I use composer packages, especially EXT:bootrap_package for my frontend. My frontend currently fails with an exception: ``` (1/1) ScssPhp\ScssPhp\Exception\CompilerException `/var/www/html/public/PKG:bk2k/bootstrap-package:Resources/Public/Scss/bootstrap5/theme.scss` file not found for @import: PKG:bk2k/bootstrap-package:Resources/Public/Scss/bootstrap5/theme.scss on line 1, at column 0 ``` the ext specifies the file via: ``` page { includeCSS { theme = EXT:bootstrap_package/Resources/Public/Scss/bootstrap5/theme.scss } } ``` if I uncomment this it starts working, but I have the feeling the notation should be good here?! The frontend is broken though for me of course; also I suppose because Scss compiling is involved the reason here is that bootstrap_packages internally evaluates this TypoScript and passes it along. But since the API tries to be backward compatible at this point I wonder if it's worth looking into. Second thing: For testing I had this Page TS Config: ``` page.includeCSS { 1=https://garv.in/css/style.css 1.external=0 2=https://google.com/nothing 2.external=0 3=/test.css 3.external=0 4=/nothing.css 4.external=0 5=../test2.css 1.external=0 6=../nothing2.css 6.external=0 10=https://garv.in/css/style.css?external=1 10.external=1 20=https://google.com/nothing?external=1 20.external=1 30=/test-external.css 30.external=1 } ``` This worked previously, but it breaks now with a TypeError: ``` TYPO3\CMS\Core\Utility\GeneralUtility::isValidUrl(): Argument #1 ($url) must be of type string, null given, called in /var/www/html/typo3-core/typo3/sysext/core/Classes/Resource/ResourceCompressor.php on line 259 ``` So I wonder if that needs to be added to the breaking changes document that certain includeCSS/JS configurations with invalid URIs may now fail, which previously silently worked.
  12. Helmut Hummel commented on patch set 84 10/25/25, 16:15

    ResourceViewHelper.php:61 Reply

    well, deprecation means it works, but is deprecated. However this has no effect setting it to false. I think though that the impact is pretty low, isn't it?
  13. Simon Praetorius commented on patch set 84 10/25/25, 17:14

    ResourceViewHelper.php:61 Reply

    Yes, it's low-impact. However, I'd like the argument to be removed eventually, since it will still appear in documentation and auto-completion. Currently, there isn't a better way: Either we just remove it or we let users know that it will be removed in the future via a deprecation in render().
  14. Christian Kuhn voted on patch set 84 CR +1 V +1 10/25/25, 18:25

  15. Christian Kuhn voted on patch set 84 V 0 10/25/25, 18:29

  16. Helmut Hummel commented on patch set 84 10/25/25, 18:32

    Reply Unresolved

    the problem here are the hooks. yes, this maybe needs to be mentioned in the breaking rst. All page renderer hooks need to be touched, when they search for certain existing (added) files and try to replace them. The fail to find them, because all added files in pageRenderer are now in PKG syntax. The second typoscript I will check out
  17. Simon Praetorius commented on patch set 84 10/25/25, 18:33

    ResourceViewHelper.php:61 Reply

    I've pushed a draft for the deprecation, if we want to take this route in a follow-up: https://review.typo3.org/c/Packages/TYPO3.CMS/+/91251
  18. Christian Kuhn voted on patch set 84 V +1 10/25/25, 18:38

  19. Helmut Hummel commented on patch set 84 10/25/25, 19:06

    ResourceViewHelper.php:61 Reply

    Ah, I think I get it. Using the argument will otherwise throw an exception when it is removed later on. So rather remove it now or deprecate it. I'm fine either way
  20. Simon Praetorius voted on patch set 84 CR +1 10/25/25, 19:13

  21. Garvin Hicking commented on patch set 84 CR +1 V +1 10/25/25, 19:22

    To not lose votes lets get it in and address the ReSt files, other BCs and VH argument as a followup. This is a great one, this brings us forward by a lot - thanks!
  22. Helmut Hummel commented on patch set 84 CR +2 V +2 10/25/25, 19:23

    Thank you so much for your detailed reviews. All comments will be tackled in followup changes!
  23. Helmut Hummel merged patch set 85 10/25/25, 19:31

  24. Garvin Hicking commented on patch set 85 10/25/25, 20:26

    I have resolved some of these in this follow-up: https://review.typo3.org/c/Packages/TYPO3.CMS/+/91252

    SystemResourceIdentifierFactory.php:52 Reply

    Done

    SystemResourceIdentifierFactory.php:106 Reply

    Done

    SystemResourceIdentifierFactory.php:127 Reply

    Done

    DefaultSystemResourcePublisher.php:55 Reply

    Done

    Breaking-107537-UrlGenerationSystemResources.rst:30 Reply

    Done

    Breaking-107537-UrlGenerationSystemResources.rst:55 Reply

    Done

    Breaking-107537-UrlGenerationSystemResources.rst:73 Reply

    Done

    Breaking-107537-UrlGenerationSystemResources.rst:79 Reply

    Done

    Breaking-107537-UrlGenerationSystemResources.rst:105 Reply

    Done

    Breaking-107537-UrlGenerationSystemResources.rst:115 Reply

    Done

    Breaking-107537-UrlGenerationSystemResources.rst:121 Reply

    Done

    Breaking-107537-UrlGenerationSystemResources.rst:127 Reply

    Done

    Deprecation-107537-CreateVersionNumberedFileName.rst:62 Reply

    Done

    Deprecation-107537-FilePathSanitizer.rst:50 Reply

    Done

    Deprecation-107537-FilePathSanitizer.rst:75 Reply

    Done

    Deprecation-107537-GetDataPath.rst:14 Reply

    Done

    Deprecation-107537-getPublicResourcesWebPath.rst:6 Reply

    Done

    Feature-107537-SystemResourceAPIForSystemFileAccessAndPublicUriGeneration.rst:62 Reply

    Done

    Feature-107537-SystemResourceAPIForSystemFileAccessAndPublicUriGeneration.rst:74 Reply

    Done

    Feature-107537-SystemResourceAPIForSystemFileAccessAndPublicUriGeneration.rst:86 Reply

    Done

    Feature-107537-SystemResourceAPIForSystemFileAccessAndPublicUriGeneration.rst:92 Reply

    Done

    Feature-107537-SystemResourceAPIForSystemFileAccessAndPublicUriGeneration.rst:160 Reply

    Done

    Feature-107537-SystemResourceAPIForSystemFileAccessAndPublicUriGeneration.rst:162 Reply

    Done

    Feature-107537-SystemResourceAPIForSystemFileAccessAndPublicUriGeneration.rst:165 Reply

    Done

    Feature-107537-SystemResourceAPIForSystemFileAccessAndPublicUriGeneration.rst:166 Reply

    Done

    Feature-107537-SystemResourceAPIForSystemFileAccessAndPublicUriGeneration.rst:168 Reply

    Done

    Feature-107537-SystemResourceAPIForSystemFileAccessAndPublicUriGeneration.rst:185 Reply

    Done

    Feature-107537-SystemResourceAPIForSystemFileAccessAndPublicUriGeneration.rst:245 Reply

    Done

    Feature-107537-SystemResourceAPIForSystemFileAccessAndPublicUriGeneration.rst:247 Reply

    Done

    Feature-107537-SystemResourceAPIForSystemFileAccessAndPublicUriGeneration.rst:250 Reply

    Done
  25. Helmut Hummel commented on patch set 85 10/28/25, 09:12

    ResourceViewHelper.php:61 Reply

    Done