- Jul 12, 2024
-
-
Christian Kuhn authored
Brings PHP 8.4 fixes. Hard raise in v13, "composer u" in v12 and v11. > composer req psr/http-factory:^1.1.0 > composer req -d typo3/sysext/core --no-update psr/http-factory:^1.1.0 Resolves: #104384 Releases: main, 12.4, 11.5 Change-Id: I65b5955379e30c4f889ed76d0b211ae25c83057d Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/85247 Tested-by:
Christian Kuhn <lolli@schwarzbu.ch> Tested-by:
Garvin Hicking <gh@faktor-e.de> Reviewed-by:
Stefan Bürk <stefan@buerk.tech> Tested-by:
core-ci <typo3@b13.com> Tested-by:
-
Christian Kuhn authored
Brings fixes for PHP 8.4. > composer req typo3fluid/fluid:^2.13.0 > composer req -d typo3/sysext/adminpanel --no-update typo3fluid/fluid:^2.13.0 > composer req -d typo3/sysext/core --no-update typo3fluid/fluid:^2.13.0 > composer req -d typo3/sysext/fluid --no-update typo3fluid/fluid:^2.13.0 > composer req -d typo3/sysext/redirects --no-update typo3fluid/fluid:^2.13.0 Note v12 only updates composer.lock to latest fluid version and does not hard raise the dependency. For v11, we can neither hard raise nor 'composer u' since younger fluid versions don't support PHP 7.4 anymore. We're still striving for PHP 8.4 support for composer instances, though: Instances with raised dependencies should be able to run v11 with PHP 8.4 if all other things sort out well. Resolves: #104380 Releases: main, 12.4 Change-Id: I39af60e8d68f2086c1af349717da003267d380d9 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/85244 Tested-by:
Andreas Kienast <a.fernandez@scripting-base.de> Reviewed-by:
Simon Praetorius <simon@praetorius.me> Reviewed-by:
-
Jasmina Ließmann authored
Naturally, ViewHelpers convert their contents immediately, which means that in the examples of the "Styleguide" backend module, developers only see the converted code and not the ViewHelper actually used. To avoid this, code examples must use "non-intact" ViewHelpers. With this patch, the CodeViewHelper is extended to decode transmitted entities. As an example, the code examples on the "Avatar" component page have been adapted accordingly. In addition, the standard height in the CodeViewHelper's code mirror configuration has been reduced. Furthermore, new styling has been introduced for example uses and code examples. This has also been adapted as an example on the "Avatar" component page. Finally, the texts on the "Avatar" component page have been updated. Further adjustments to the other example pages in the "Styleguide" backend module will follow. Resolves: #104371 Releases: main Change-Id: I030e12cb144befb267dea1c3d5770787c8480c35 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/85231 Tested-by:
Jasmina Ließmann <minapokhalo+typo3@gmail.com> Reviewed-by:
-
Garvin Hicking authored
When a CType content element is registered with an empty label, the page preview of that element showed a warning: INVALID VALUE ("myPlugin") which is actually misleading, because not the value itself is wrong, but the label is missing. A new language variable is introduced to distinguish the difference of this misconfiguration issue, and now emits: MISSING LABEL ("myPlugin") Resolves: #104299 Releases: main, 12.4 Change-Id: I7fedaaa017c37f65841c0f00bafa42dd78fc91ef Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/85098 Tested-by:Georg Ringer <georg.ringer@gmail.com> Reviewed-by:
Karsten Nowak <captnnowi@gmx.de> Tested-by:
-
Benjamin Kott authored
We are dropping the Bootstrap CSS definitions for alerts to have more control about the styling of the alerts. From now on we are shipping custom css adapted to our needs. The new alert styling is context aware and adapts to light and dark color schemes. Resolves: #104374 Releases: main Change-Id: I3d2f06a638eccb42acef19ff760f5c453627a484 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/85225 Tested-by:
Benjamin Franzke <ben@bnf.dev> Tested-by:
-
Mathias Bolt Lesniak authored
Replaces execution of PHP's `exec()` function with Symfony's Process component within `TYPO3\CMS\Core\Utility\CommandUtility` while maintaining compatibility with the previous implementation. Migrating to Symfony Process implements a more widely compatible solution to command execution, simplifying installation in more limited environments. Because it is recommended best practice when using Symfony Process, this patch also adds the possibility to supply an array to the `$command` argument `TYPO3\CMS\Core\Utility\CommandUtility::exec()`. This patch also adds `symfony/process` as a direct dependency of `typo3/cms-core`. Resolves: #104045 Releases: main Change-Id: I4982d55ec03e3e36f96f23a331421dc5e14d6b14 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/84609 Reviewed-by:
Simon Schaufelberger <simonschaufi+typo3@gmail.com> Tested-by:
Benni Mack <benni@typo3.org> Tested-by:
-
Garvin Hicking authored
Resolves: #90503 Releases: main, 12.4 Change-Id: I3aa078bf231211580aa8f29c11860e002e7be2d0 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/84618 Tested-by:
-
Christian Kuhn authored
BcryptPasswordHash has an option to set a cost value. The lower barrier used to be identical to PHP constant PASSWORD_BCRYPT_DEFAULT_COST. Tests use the lower barrier to speed up tests. With PHP <8.4, PASSWORD_BCRYPT_DEFAULT_COST is 10, it has been raised to 12 with PHP 8.4. The patch frees our code from access to this constant and hard codes 10 as lower barrier check. This keeps the API as is, and this hash is by default set to 12 already in default options if none are provided. Resolves: #104373 Releases: main, 12.4, 11.5 Change-Id: I4c1e94fdc50aa3075570549ccdd3b81a2de2e98a Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/85235 Reviewed-by:
Oliver Bartsch <bo@cedev.de> Tested-by:
-
Christian Kuhn authored
As a PHP 8.4 preparation, phpunit is raised to latest version of current major version. > composer req --dev phpunit/phpunit:^11.2.7 -w Resolves: #104372 Releases: main, 12.4, 11.5 Change-Id: I395b8487bc3aca2dc34d4b7fe86c03d58a7a8709 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/85232 Tested-by:
-
Garvin Hicking authored
With the removal of the old hook `$GLOBALS['TYPO3_CONF_VARS'] ['SC_OPTIONS']['t3lib/class.t3lib_parsehtml_proc.php']['transformation']` there was only a limited way to handle RTE/persistence HTML transformations. With the introduction of four new PSR-14 events, the transformation logic can now also be influenced by extensions: * `TYPO3\CMS\Core\Html\Event\BeforeTransformTextForPersistenceEvent` * `TYPO3\CMS\Core\Html\Event\AfterTransformTextForPersistenceEvent` * `TYPO3\CMS\Core\Html\Event\BeforeTransformTextForRichTextEditorEvent` * `TYPO3\CMS\Core\Html\Event\AfterTransformTextForRichTextEditorEvent` Resolves: #104221 Related: #92992 Releases: main Change-Id: Id305ac526f4e63f1c585f101573c6d417fbfc476 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/85079 Tested-by:
Stephan Kellermayr <quellenform@gmail.com> Tested-by:
-
Georg Ringer authored
As only `Resources\File` provides the method `setMissing` an additional check is provided - just as on multiple other places in the class. Resolves: #95102 Releases: main, 12.4 Change-Id: I75dc0cb29c3f66e06e9658d9c5cb27da3a6ca816 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/85134 Tested-by:
-
Oliver Bartsch authored
When using boolean attributes there are two things to consider: 1. The default value must be FALSE 2. Presence of the attribute always means TRUE It's therefore not possible to have a boolean attribute, which defaults to TURE and it's also not possible to set an attribute to FALSE via its value (e.g. "0" or "false). See for reference: https://html.spec.whatwg.org/multipage/common-microsyntaxes.html#boolean-attributes Therefore, to properly handle the "is writeable" state in the language packs module, the default is set to FALSE an the attribute only gets added (which defines the TRUE state) in case corresponding data attribute is set in the template. Resolves: #104353 Releases: main, 12.4 Change-Id: I82f440ae4fbeba405c35bbfa859804e2bc0660c0 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/85217 Tested-by:
-
Oliver Bartsch authored
The `OtherLanguageThumbnails` field wizard renders thumbnails of each crop variant from the default language for images in translations. However, on the first view, the cropped (processed) image is not created yet, leading to the public url being an absolute url to the `image_processing` route, e.g. "https://example.com/typo3/image/process?token=abc&id=123". This URL can not be used by `getIconHtml()` to create the markup. However the function call is not needed at all, since we can just render the markup directly as no icon is about to be generated. Resolves: #104355 Releases: main, 12.4 Change-Id: Ic624f8fd7114da18e01d7f33a9c8714bc8db026c Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/85221 Tested-by:
-
Torben Hansen authored
When a CKEditor configuration by intention does not include the `softhyphen` toolbar item, the item is automatically added in `CKEditor5Migrator`. This change removes the forcibly added softhyphen toolbar item, allowing integrators to create a CKEditor configuration that does not include the `softhyphen` toolbar item. Resolves: #103919 Releases: main, 12.4 Change-Id: I72a926a75e5c1b791d90921b0ff4c94eb7e938b1 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/84407 Reviewed-by:
-
Marcin Sągol authored
Updated the labels for various sections in the access rights configuration form to improve clarity and usability. It was suggested to add a description text to the Modules section in the backend group configuration form, to notice users that it behaves differently than Limit To Languages section. Having additional description probably wasn't a good idea because there are also other sections that probably should have one added. Instead the seaction labels were updated to make them more self-explanatory, so now we have: Grouptitle --> Title Modules --> Allowed modules Dashboard widgets --> Allowed dashboard widgets Page types --> Allowed page types Allowed excludefields --> Allowed fields They align for example with already defined labels like: Allowed multi-factor authentication providers. The used/added Allowed word clearly states that by checking some checkboxes in such sections, we allow to use some elements. Resolves: #103968 Releases: main Change-Id: I9c367a88fb8729a357d1f162b2559c8331c21dea Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/84486 Tested-by:
-
Garvin Hicking authored
With issue #104074 a change was introduced that no longer required "typo3conf" to exist in composer mode. Sadly the installer performed a write check on the specific old "typo3conf" location instead of using the actual new location for config files since TYPO3 v12. The installer does not report back FlashMessages on failed AJAX requests, also those AJAX requests currently oddly do not even show up in browser's network panel. Without this, an enduser is not able to finish the installation, which could be done by just creating an empty "typo3conf" directory. This should be addressed in a follow-up, the FlashMessage is already prepared now to be contained in the JSON response. Resolves: #104306 Related: #104074 Releases: main Change-Id: Icabdee13e79f016ef17cdd3e2ab62cf078f63b4c Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/85106 Reviewed-by:
Guido Schmechel <guido.schmechel@brandung.de> Tested-by:
Markus Klein <markus.klein@typo3.org> Reviewed-by:
Björn Jacob <bjoern.jacob@tritum.de>
-
Benni Mack authored
When loading Record objects, and we use Relations in one of the next patches, the main issue will be that we might run in recursions when fetching relations. This can be resolved by re-using created Record objects by utilizing the Identity Map pattern (https://en.wikipedia.org/wiki/Identity_map_pattern) which keeps track (context-wise) of the loaded records. In a way to unify this logic, the "RecordRememeberer" for Page Module has now been removed as this is the exact purpose of the Identity Map. The next step is to actually utilize the Record API in the Page module replacing arrays there completely. Resolves: #104367 Related: #103783 Releases: main Change-Id: Idd56a49c421fd722ed35eedded365420a7479bea Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/85047 Reviewed-by:
Oliver Hader <oliver.hader@typo3.org> Tested-by:
-
- Jul 11, 2024
-
-
Xavier Perseguers authored
When the plugin is configured to use the referrer to redirect after a successful login, it should not honor it when the referrer is the password reset form and the user just updated their password. Resolves: #104214 Resolves: #101581 Related: #21943 Releases: main, 12.4 Change-Id: I6fcf3927de0a7157958c4d20682bfcf5390826c8 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/84925 Reviewed-by:
Torben Hansen <derhansen@gmail.com> Tested-by:
-
Christian Kuhn authored
Avoid $GLOBALS['TCA'] access in ReferenceIndex by using TcaSchema. This is a patch to learn about fiddly areas and pitfalls when using TcaSchema in scenarios with lots of different field related details and relations: The general API feels good, but it's sensitive to errors with such transition patches. Resolves: #104366 Related: #104002 Releases: main Change-Id: I3cce9cc9681348454ddb87fc5ebd90139dbc4776 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/85008 Reviewed-by:
-
Georg Ringer authored
Extend the identifier used within the DOM by an additional field, as already done in #97042 to make flexform sections within inline child records work. A styleguide example makes it easy to reproduce the edge case. Resolves: #100937 Related: #97042 Releases: main, 12.4 Change-Id: I40120ea13b892c6387833dab444dad86951cf96f Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/85189 Tested-by:
-
Christian Kuhn authored
"KEY lookup_string (ref_string(191))" is only used in a query performed by ext:form. This extension is a bit specific with using sys_refindex and is the only one that queries using "where ref_string=...". To reduce index size of sys_refindex a bit, that index is now moved to ext:form to be added only if that extension is loaded. Resolves: #104368 Releases: main Change-Id: I3315633590089bb7f7997865fbba34ecca9c250a Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/85228 Tested-by:
Anja Leichsenring <aleichsenring@ab-softlab.de> Reviewed-by:
-
Benni Mack authored
This change adds a new fixture extension with a content element with a relation to an inline table. Resolves: #104369 Releases: main Change-Id: I777d5dbdebaad4f278bab2dc2b87ebd92f331515 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/85227 Reviewed-by:
-
Simon Schaufelberger authored
Add test coverage for GeneralUtility::getFilesInDir with sorting by mtime. Resolves: #103817 Releases: main Change-Id: I298f63fef0369cf2fefd0876628ca55a152947c9 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/84190 Reviewed-by:
-
Benjamin Kott authored
We replace the default bootstrap `text-<color>` utility CSS classes with an own color-scheme aware implementation. In contrast to the original bootstrap color utilities we ensure that the new set is accessible and optimize the color contrast for all values. This results in darker colors for light-mode and lighter colors for dark-mode. Resolves: #104362 Releases: main Change-Id: I8e36394435aa523069aad784f54b632bff489eb8 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/85223 Reviewed-by:
Benjamin Kott <benjamin.kott@outlook.com> Tested-by:
-
Jasmina Ließmann authored
Over time, EXT:stylguide has expanded its range of functions. To clarify the separation between styles and components, as well as the functionality of creating example page trees, the contents of the backend module "Styleguide" are divided into submodules. Resolves: #104358 Releases: main Change-Id: I9548567265633b66da3fadd4f0f5b07f39f79ae8 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/85186 Reviewed-by:
-
Benjamin Kott authored
The callout component is now using the unified surface colors. The new callout styling is now context aware and adapts to light and dark color schemes. Resolves: #104359 Releases: main Change-Id: I8299aa0fde12aa41acae58a53eea3d00f3ed13ec Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/85222 Tested-by:
-
Andreas Nedbal authored
This patch removes the Bootstrap "card" component as the cards present in the Backend are implemented using the classes and styling of TYPO3. The conflict comes from a time in which Bootstrap (3.x) only had panel-* classes and for the new card component the classes were modelled after Bootstraps naming scheme. This did not end up matching what Bootstrap implemented finally, causing confusion within some developers when using cards in the backend. Resolves: #99233 Related: #94529 Releases: main Change-Id: Ia1bf1f453310cc452059ec9396c2f54be87c2150 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/76870 Tested-by:
-
Benjamin Kott authored
We are dropping the Bootstrap CSS definitions for badges to have more control about the styling of the badges. From now on we are shipping custom css adapted to our needs. The new badge styling is context aware and adapts to light and dark color schemes. Resolves: #104356 Releases: main Change-Id: I4a449feb4a4dc0bc32664d99fabd453fa969ddd4 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/85219 Reviewed-by:
-
- Jul 10, 2024
-
-
Andreas Kienast authored
The class `TypoScriptReferenceController` used by our code editor get some minor updates: * Removed unneded `$xmlDoc` property * Added missing type declarations * Resolved open @todo Resolves: #104352 Releases: main Change-Id: Iee855f7cf1f2f3fac80ba4f9482473d08420257c Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/85216 Tested-by:
-
Benjamin Kott authored
We are dropping the Bootstrap CSS definitions for buttons to have more control about the styling of the buttons. From now on we are shipping custom css adapted to our needs. The new button styling is context aware and adapts to light and dark color schemes. Resolves: #104350 Releases: main Change-Id: Id6a08557d6414f08cb213420db2a60e70ff4be08 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/85150 Reviewed-by:
-
Oliver Bartsch authored
Toggling the visibility of the new alert element, introduced with #103699, does actually lead to changing the `opacity` property. Therefore, the corresponding space of the alert element will stay, leaving empty spaces in the backend. This is now resolved by additionally toggling the `hidden` class, which works with the `display` property. Note: The `show` class has to stay due to the underlying functionality from the used bootstrap component. Resolves: #104346 Related: #103699 Releases: main Change-Id: Id85da0972be02b43ef78f79fd1118d74e8ff1662 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/85213 Tested-by:
Marcin Sągol <marcin@soee.pl> Reviewed-by:
-
Daniel Siepmann authored
PHP will cast array keys to int if they are valid integers. The code applies htmlspecialchars() on the keys. The function expects a string as first argument, which wouldn't be the case if the actual value would be an int. Therefore the key is casted to a string within the function call to prevent TypeError. Resolves: #104341 Releases: main, 12.4 Change-Id: Ic9aef0fd37f2e883a2a8fa626cfda2e813e3b289 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/85190 Tested-by:
-
Garvin Hicking authored
With the introduction of the new filelist functionality, the list view of folders no longer showed their last modification timestamps. Without this information, the list view could no longer sort the whole item list by date. With this patch, the information is now fetched not only for files, but also for folders. Folders and files are sorted on their own, so no file will be sorted in between a list of folders (and vice versa). (Note that for filesystem folders there is only one timestamp, so "last modified" and "created at" will use the same timestamps. Remote folders with their distinct drivers may provide distinguishable information.) Resolves: #100520 Releases: main, 12.4 Change-Id: I4e9ceb597946cc7532b76ec2ee4bec3d52d17fdc Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/85158 Tested-by:
Riccardo De Contardi <erredeco@gmail.com> Tested-by:
-
Marcin Sągol authored
A new web component called `<typo3-backend-alert>`, which is based on the Bootstrap alert component, is introduced. It will be used to streamline the use of this component through backend code. The web component can therefore be used in any JavaScript module or directly in HTML markup. This is the first step towards unifying the alert, notification, and callout components in the backend. These components share a lot of common logic and should therefore have a common ancestor. Note: The new component might receive further changes in the future and is therefore introduced as internal for now. Resolves: #103699 Releases: main Change-Id: Ie31ef032ad1d3bb28553f518eff0a7673b53257d Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/84535 Reviewed-by:
-
Andreas Kienast authored
The flatpickr integration in TYPO3 is configured to use luxon for date time formatting operations, which consumes different format tokens. This leads to the situation that aria labels generated by flatpickr are now broken. This commit changes the option `ariaDateFormat` to luxon's `DDDD` token, which renders a "localized date with full month and weekday", according to [1]. [1] https://moment.github.io/luxon/#/formatting?id=table-of-tokens Resolves: #104342 Releases: main, 12.4 Change-Id: I7902d39209ad59e0c3196db7f906b93533d7b7cf Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/85191 Tested-by:
-
- Jul 09, 2024
-
-
Christian Kuhn authored
The patch level release brings PHP 8.4 compat. Core v12 and v11 will have dedicated patches. > composer req lolli42/finediff:^1.1.1 > composer req --no-update -d typo3/sysext/core lolli42/finediff:^1.1.1 Resolves: #104339 Releases: main Change-Id: I6521f8d8fddce1d10d97350d4c6128de026df120 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/85183 Tested-by:
Oliver Klee <typo3-coding@oliverklee.de> Tested-by:
-
Christian Kuhn authored
* Inject service dependencies * Clean up doc headers * generate() can return string|int over string only to create better typed DB values up front * Various further minor type improvements * readonly classes where possible Resolves: #104336 Releases: main Change-Id: I2cda858d30b70d527f4024bce8c3e95b6176679e Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/85146 Tested-by:
Mogens Fiebrandt <mogens.fiebrandt@googlemail.com> Tested-by:
-
Andreas Kienast authored
The date time picker module `@typo3/backend/date-time-picker` uses flatpickr, but wasn't aware of it due loose `any` usages. The code is modified to make use of the typings shipped with flatpickr. To solve this long-standing issue, the module identifier is changed from `flatpickr/flatpickr.min` to `flatpickr`, which requires an additional entry in the `JavaScriptModules.php` configuration, but allows to remove a module declaration. Resolves: #104338 Releases: main, 12.4 Change-Id: I3feed53627c639e21e4812855fd4ce2defe91c14 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/85182 Reviewed-by:
-
Benni Mack authored
This change adds native PHP types to RelationHandler. The reasoning for the changes: - Even though some properties are public and not typed, setting an array property to null will fatal if Relation Handler already expects an array access - Some methods do not get full types, as some options can be string/int etc, whereas $tableName must be a string in any case, where a type is applied. This is a pre-patch as part of a bigger change in order to bring TcaSchema API and Record API into RelationHandler. Resolves: #104334 Releases: main Change-Id: I66c6ae10858d6a2bb37ee03792e191b755bd1968 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/85105 Reviewed-by:
-
Stefan Bürk authored
This change adds PHP8.4 as allowed version to the `Build/Scripts/runTests.sh` script as preparation to validate and check the Core and 3rd party libs with PHP8.4 locally. Note that unit tests already revealing deprecation and errors for 3rd party extension which can now be reported and for checked upstream updates. Resolves: #104337 Releases: main, 12.4, 11.5 Change-Id: I76d3e37b393c347173fcdbe874d6a0737fb76d33 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/85178 Tested-by:
-
