- Sep 22, 2021
-
-
Oliver Bartsch authored
With #93526, multi-factor authentication was introduced to TYPO3. This came with several configuration options, such as the possibility to require MFA for specific users and user groups. Previously, the only result of this option was a warning, displayed in the MFA configuration module. Obviously, this did not really help administrators, trying to enforce MFA in their system. Therefore, this patch adds the missing endpoint, which is automatically called for all users, required to set up MFA, as soon as they have successfully passed the first authentication step (e.g. username + password). While it's a new endpoint, the actions still call the MFA providers the same way, the MFA configuration module does. Therefore, no changes to the API. Resolves: #95287 Releases: master Change-Id: Ib82ae53cbd5bd0782418d81d166c1f3d7e9a7ab1 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/71132 Tested-by:
Oliver Hader <oliver.hader@typo3.org> Tested-by:
Benni Mack <benni@typo3.org> Tested-by:
core-ci <typo3@b13.com> Tested-by:
Oliver Bartsch <bo@cedev.de> Reviewed-by:
-
Oliver Bartsch authored
A couple of patches changed the amount of columns, shown in the filelist module listing. For example, since column selector component. Also multi record selection, introduced in #94906, adds an additional column, providing the checkbox. This patch therefore adjusts the DragUploader component to take this into account while dynamically adding rows for uploaded files. Resolves: #95300 Related: #84184 Related: #94906 Releases: master Change-Id: I0fcadc1c38da94a3365f6524c5407fe487fc4e21 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/71166 Tested-by:
-
Christian Kuhn authored
Ever wondered the icons of the main core extensions that use the TYPO3 logo all look subtly different, for instance in EM? The patch aligns them to the 'white logo with orange background' svg version. Resolves: #95310 Releases: master Change-Id: Ifd04c8bbe03e7988c44b0db34a15aa0a11b31eb0 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/71175 Tested-by:
Georg Ringer <georg.ringer@gmail.com> Tested-by:
Benjamin Franzke <bfr@qbus.de> Reviewed-by:
-
Benni Mack authored
ext_localconf.php still references "localconf.php" even though it is called "LocalConfiguration.php" since TYPO3 v6.0. Resolves: #95314 Releases: master, 10.4 Change-Id: Idd8f85bbc9351959b0be35e353f8237cf33b54e8 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/71183 Tested-by:
Christian Kuhn <lolli@schwarzbu.ch> Reviewed-by:
-
Benjamin Franzke authored
This change allows module URLs to be automatically framed by the TYPO3 main controller whenever they are directly opened in the browser address bar in a secure environment (e.g. https:// or .localhost TLD) (In this case the Sec-Fetch-Dest=document is sent by browsers). See: https://w3c.github.io/webappsec-fetch-metadata/#sec-fetch-dest-header Note: This header is already supported by Chrome, Edge and Firefox nightly, only Safari does not deliver this header yet. Non supporting browsers or unsafe http connections will gracefully fallback to showing the module contents without the TYPO3 main frame being added. This fallback behaviour is only triggered when a link is opened in a new tab. Regular clicks are intercepted and directly dispatched via module-router/iframe, as before. This change allows to render the module menu with anchor tags instead of buttons which lets users decide how and where a module should be opened. Long term goal is to improve accessibility by using real links not only in module menu (as we had in TYPO3 v7), but actually everywhere (for example in the database record list), in order for the user to decide whether to open a link in the current or a new tab. This will require enhancing FormEngine routes with module information and is therefore out of scope for this change. Resolves: #94084 Releases: master Change-Id: Iaad8fe62644ec6c9cb1aaa4c92ce2e8e3eeab7bd Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/69058 Tested-by:
-
Benni Mack authored
Resolves: #95299 Releases: master Change-Id: I4882a9ca07948718afdeb1a5fb5b3a518eb86c38 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/71163 Tested-by:
-
Benjamin Franzke authored
Commands executed: cd Build/ yarn upgrade lit@^2.0.0 lit-html@^2.0.0 lit-element@^3.0.0 @lit/reactive-element@^1.0.0 grunt rollup Releases: master Resolves: #95303 Change-Id: I7e67815cdc0d7e055c6974af4889d51cea76a45d Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/71168 Tested-by:
Wouter Wolters <typo3@wouterwolters.nl> Reviewed-by:
-
Susanne Moog authored
Fixes both admin panel and time tracker array access warnings with PHP8. Resolves: #95309 Releases: master Change-Id: I528c7dcb0f0daa1bd898dc342b5047120e27932d Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/71174 Tested-by:
Andreas Fernandez <a.fernandez@scripting-base.de> Tested-by:
-
Wouter Wolters authored
Resolves: #95234 Releases: master Change-Id: Ic6e8326d0e9f97429a727ac1ceae6aab2ff976d7 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/71078 Tested-by:
-
- Sep 21, 2021
-
-
Wouter Wolters authored
The variable $this->arguments['selected'] is not always set. Resolves: #95283 Releases: master Change-Id: I24ac026300c04bd9bf2e5f2bab580cdf847df5ad Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/71169 Tested-by:
-
Oliver Bartsch authored
Resolves: #95306 Releases: master Change-Id: I9dfeef91bc22eb4abf67759f1eb9286061c9b42c Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/71172 Tested-by:
-
Wouter Wolters authored
Update the following packages from TYPO3 itself to their latest version: typo3/cms-cli typo3/cms-composer-installers typo3/symfony-psr-event-dispatcher-adapter Composer commands used: composer req typo3/cms-cli:^3.1 composer req typo3/cms-cli:^3.1 -d typo3/sysext/core --no-update composer u typo3/cms-composer-installers composer u typo3/symfony-psr-event-dispatcher-adapter Resolves: #95304 Releases: master Change-Id: Icf3d4f3d8a577e01fbdbe1402170349282149aed Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/71170 Tested-by:
-
Oliver Bartsch authored
The clipboard component still suffers a lot of problems, due to its static integration in the list modules. For example, when clearing the clipboard, it's no longer possible to copy / cut a record via context menu, since the the previous GET parameters are included in the return URL, directly reverting the operation. The list modules should therefore not longer handle any clipboard logic directly, especially not via GET. This patch does the first step towards this goal and introduces a dedicated endpoint, only available via POST. The clipboard panel, used in recordlist and filelist is furthermore now integrated as a web component, making any form submit in the main module superfluous. Additionally some related bugs are fixed: * Elements moved to clipboard via context menu can now be remvoed from clipboard again * Non related elements are now always properly styled * File elements now correctly link to their parent folder in filelist * Buttons are only shown for the clipboard they influence Resolves: #95268 Resolves: #95267 Releases: master Change-Id: I7b1050c9b0f11a1e495ef09df4d0560dd84df882 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/70978 Tested-by:
-
Helmut Hummel authored
Environment::getFrameworkBasePath() API was created under the assumption that TYPO3 core extensions are always installed in a dedicated but fixed folder (typo3/sysext). Additionally this folder is assumed to be publicly accessible through a web server. Therefore this API is used in two contexts. 1. To resolve and check file system paths 2. To create URLs to public resources To at some point achieve the goal to allow all TYPO3 extensions to be installed in arbitrary locations (a configurable vendor folder), usage of such API must be removed. As a first step all usages are removed, that reference files within the boundaries of one extensions. Relative paths (relative to the file that references) are used instead, or, where possible EXT: syntax Releases: master Resolves: #95250 Change-Id: Ie7291b71d5d85d75add9bc5b352a4bd1cf065499 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/71102 Tested-by:
Helmut Hummel <typo3@helhum.io> Reviewed-by:
-
Benni Mack authored
With PHP 8.0 and symfony/polyfill-php80 it is possible to use native str_starts_with() and str_ends_with() methods. This way, the methods * StringUtility::beginsWith() * StringUtility::endsWith() are marked as deprecated. Resolves: #95293 Releases: master Change-Id: I46d15c2f8b93c5f8b487966b2015ebefb1711348 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/71135 Tested-by:
-
Christian Kuhn authored
Communication patch for an upcoming v12 change. We've had the situation a couple of times that core changed Fluid Viewhelpers to adapt them to current needs, keeping the template arguments, but changing internal handling and method signatures. It happened that developers then stepped up with "This broke my own Viewhelper!" and we had to act upon. The ImageViewHelper for instance has been a victim of this. From a framework point of view, Viewhelpers are specific implementations tailored for specific use. In most cases, they're small codewise. Extending these classes and changing their scope should not be supported. Developers should extend a matching abstract instead of extending specific VH's. The patch brings an Important.rst to pitch an upcoming v12 change that will declare all Viewhelpers final. The core currently of course also extends a couple of VH's itself, but this is too late for v11 now to change and adapt. Instead, we'll take the time in v12 to resolve these cases and will have a look at the abstract classes as well to see which VH functionality should be included in abstracts to simplify re-use and transition for extension authors and to sharpen core API. Resolves: #95298 Releases: master Change-Id: Ia3312829fad94e7429c0989f3aa3554c3cf944ec Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/71164 Tested-by:
Mathias Brodala <mbrodala@pagemachine.de> Reviewed-by:
-
Benni Mack authored
This change removes the language title and flag from each CE, and instead adds only the flag if the content element is set to "All Languages" (-1). In addition, the header is now based on flex-box instead of floats. Resolves: #95302 Releases: master Change-Id: I6d1a180915fba9f2ccf8df3979a2256134d18379 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/71116 Tested-by:
Rachel Foucard <rfoucard@w-seils.com> Tested-by:
-
Francois Suter authored
In the workspaces module, hide the mass action selector when no actions are available. In particular, this is the case when options.workspaces.enableMassActions = 0 has been set in User TSconfig. Releases: master Resolves: #95295 Change-Id: I81b5aa62ec5496b37dc70f042e4e3d779d84f874 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/71165 Tested-by:
-
Jochen Roth authored
Links without a target are actually buttons. Previously, the "Update extension" link in the reports module was furthermore removed while parsing, due to the missing target. Therefore this patch transforms the "link", which is using the ActionDispatcher, to be a button. Resolves: #95169 Releases: master Change-Id: I89847e1e1ec45fb7f5c797b2c25646f113905508 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/70985 Tested-by:
-
Francois Suter authored
The setting options.workspaces.enableMassActions is described in the extension manual as being a Page TSconfig option, whereas it is a User TSconfig option. Releases: master Resolves: #95296 Change-Id: Id0fc6a1c47323fddff018676bc52934f01cf2f13 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/71162 Tested-by:
Xavier Perseguers <xavier@typo3.org> Tested-by:
Stephan Großberndt <stephan.grossberndt@typo3.org> Reviewed-by:
-
Robert Kärner authored
Fix PHP8 related "undefined array key" warnings which occur in the backend by adding the required fallbacks. Resolves: #95239 Releases: master Change-Id: Id1477c95ac00e90b9d449271fb461f2b4dc34235 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/71100 Tested-by:
-
Christian Kuhn authored
When publishing workspace records with connected "true" MM relations (uid_local / uid_foreign columns and no TCA for that table), DataHandler triggers bugs: * It updates uid_local or uid_foreign rows to negative uids during the process as intermediate DB state. * It leaves "dangling" MM rows of the workspace record that has been pushed live. The involved code is relatively well encapsulated, it only kicks in for this "publish MM relations" scenario, the impact of this patch is limited to this area. The patch rewrites MM workspace publish handling: * Avoid parking state in a DataHandler class property only used in this scenario. * Avoid moving a list of stateful RelationHandler instances around and dynamically calling methods on those instances. * Avoid recursive flex form MM publish handling with indirect callback methods that change class state. * Obsolete a RelationHandler method used only in this scenario. * Reduce number of queries. The result is a simplified, better encapsulated and well commented solution. On a testing side, the patch brings a scenario to verify flex form MM relation handling. An according styleguide example is pending, too. This patch allows us to change auto created MM table definitions to unsigned uid_local and uid_foreign columns, which is of course the right way to go. Change-Id: I0d24f31cbd356f19937c2f8c18d432424e127b97 Resolves: #95275 Resolves: #81718 Releases: master Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/71097 Tested-by:
Stefan Bürk <stefan@buerk.tech> Tested-by:
-
Stefan Bürk authored
A functional test has been disabled for postgres execution due duplicate key issues using `setupFrontendRootPage` in functional testcases. As setUpFrontendRootPage has been fixed in the testing framework, this test is enabled again. Commands to test: $ Build/Scripts/runTests.sh -s functional -p 7.4 -d postgres -k 9.6 \ typo3/sysext/frontend/Tests/Functional/SiteHandling/MountPointTest.php $ Build/Scripts/runTests.sh -s functional -p 7.4 -d postgres -k 10 \ typo3/sysext/frontend/Tests/Functional/SiteHandling/MountPointTest.php $ Build/Scripts/runTests.sh -s functional -p 7.4 -d postgres -k 11 \ typo3/sysext/frontend/Tests/Functional/SiteHandling/MountPointTest.php $ Build/Scripts/runTests.sh -s functional -p 7.4 -d postgres -k 12 \ typo3/sysext/frontend/Tests/Functional/SiteHandling/MountPointTest.php $ Build/Scripts/runTests.sh -s functional -p 7.4 -d postgres -k 13 \ typo3/sysext/frontend/Tests/Functional/SiteHandling/MountPointTest.php $ Build/Scripts/runTests.sh -s functional -p 8.0 -d postgres -k 9.6 \ typo3/sysext/frontend/Tests/Functional/SiteHandling/MountPointTest.php $ Build/Scripts/runTests.sh -s functional -p 8.0 -d postgres -k 10 \ typo3/sysext/frontend/Tests/Functional/SiteHandling/MountPointTest.php $ Build/Scripts/runTests.sh -s functional -p 8.0 -d postgres -k 11 \ typo3/sysext/frontend/Tests/Functional/SiteHandling/MountPointTest.php $ Build/Scripts/runTests.sh -s functional -p 8.0 -d postgres -k 12 \ typo3/sysext/frontend/Tests/Functional/SiteHandling/MountPointTest.php $ Build/Scripts/runTests.sh -s functional -p 8.0 -d postgres -k 13 \ typo3/sysext/frontend/Tests/Functional/SiteHandling/MountPointTest.php Resolves: #95114 Releases: master Change-Id: I85d74f05e7ef347cd217843c0384d460194fac24 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/70897 Tested-by:
-
Oliver Hader authored
https://github.com/TYPO3/html-sanitizer/releases/tag/v2.0.11 composer req typo3/html-sanitizer:^2.0.11; \ composer req typo3/html-sanitizer:^2.0.11 \ -d typo3/sysext/core --no-update Resolves: #95289 Releases: master, 10.4, 9.5 Change-Id: I3a294c788f25ca5a1068f9eb79c924f65e21244d Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/71152 Tested-by:
-
- Sep 20, 2021
-
-
Benni Mack authored
One of our main utility methods "GeneralUtility::isFirstPartOfStr" can now replaced by PHP's native "str_starts_with()" function (see https://www.php.net/manual/en/function.str-starts-with.php) which is also available for PHP 7.4 thanks to Symfony's polyfill package. This way, we can a) slim down our own code base in favor of native PHP calls b) add a bit of performance due to native PHP calls c) move towards type-safety to ensure that we hand over strings to these methods, as our own method was a bit more "lax" on things Resolves: #95257 Releases: master Change-Id: I70617ab4419849353a72a10dfed31a2d96f58072 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/70444 Tested-by:
-
Oliver Hader authored
https://github.com/TYPO3/phar-stream-wrapper/releases/tag/v3.1.7 composer req typo3/phar-stream-wrapper:^3.1.7; \ composer req typo3/phar-stream-wrapper:^3.1.7 \ -d typo3/sysext/core --no-update Resolves: #95286 Releases: master, 10.4, 9.5 Change-Id: I077aca99a5fbcf44c957a808c072b69906e02cf9 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/71129 Tested-by:
-
Oliver Bartsch authored
With #88921 new events were introduced, which allowed to add additional markup to the columns in page layout. Those events however were never implemented in the fluid based page module. Making them useless in v11, since PageLayoutView can no longer be used. This patch therefore adds the events to the fluid based page module. Due to the changed functionality in the new code base, the events are extended and some methods are deprecated. A side effect from the fluid based page module is, that the events do now take effect in both modes, columns mode and languages mode, as well as for defLangBinding. Resolves: #95261 Related: #88921 Releases: master Change-Id: Icbf10f29f6a3bb9f3ce1b591ceccfde966380cb1 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/71118 Tested-by:
-
Jochen Roth authored
The language switch in FormEngine allows to either switch to an existing translation of the current record, or to create such a translation. This however currently does only work in case a default language record exists. Therefore, in case no default record exists, the "localize" option is skipped for the record, preventing PHP warnings. Resolves: #95160 Releases: master Change-Id: I01211b16fc51c8a18a7f97f5d5c8fa316a34ae49 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/70979 Tested-by:
-
Oliver Hader authored
* cleans up code, to avoid using "onclick" in variable name * adds deprecation comments to simplify removing snippets in TYPO3 v12.0 Resolves: #95276 Releases: master Change-Id: Ica1e9b24f831728d072a6ec12c48e4cfea2ce96a Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/71125 Tested-by:
-
Simon Gilli authored
ext:frontend uses the function mb_ord which is available since symfony/polyfill-mbstring v1.16 and to avoid issue this dependency is properly increased and also added to ext:frontend. Composer commands used: * composer require "symfony/polyfill-mbstring:^1.16" * composer require --no-update -d typo3/sysext/core "symfony/polyfill-mbstring:^1.16" * composer require --no-update -d typo3/sysext/frontend "symfony/polyfill-mbstring:^1.16" Resolves: #95279 Releases: master, 10.4, 9.5 Change-Id: I31aa9affa936ae96d5a02ad846aa011fb89af75d Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/71127 Tested-by:
-
Benni Mack authored
The navFrameScript / navigationFrameModule functionality, which adds an iFrame for the navigation frame for a specific module has now been deprecated in favor of native custom HTML tags / web components. Resolves: #94094 Releases: master Change-Id: Ieb89f9f87efe0f2f12dd6abe4a8111edda0cd24b Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/68923 Tested-by:
-
Oliver Hader authored
Resolves: #95274 Releases: master Change-Id: If60f410ff1e1ed6a8f52e30df32900a4be73ad27 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/71124 Tested-by:
-
Oliver Hader authored
This change allows using internal URIs (like t3://) in components of the backend user interface like * system news show below the backend login form * rich text details of system reports HTML sanitization is applied to mentioned components as well. Resolves: #95179 Related: #67556 Releases: master Change-Id: I94c91fbb27380b26b136eba604e5c1552061eab2 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/71020 Tested-by:
-
Oliver Hader authored
Substitutes inline `onclick` events for `ShortcutMenu` invocations in the backend user interface with corresponding HTML attributes handled by `ActionDispatcher.ts`. Resolves: #95260 Releases: master Change-Id: I8ca787056635aeff30ae3f4b1142f472fa5e1aa3 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/71119 Tested-by:
-
Oliver Hader authored
Introduces `<f:transform.html>` view-helper, providing capabilities to resolves system internal links, like `t3://`. Example: <f:transform.html selector="a.href,div.data-uri"> <a href="t3://page?uid=1" class="page">visit</a> <div data-uri="t3://page?uid=1" class="page trigger">visit</div> </f:transform.html> ... will be resolved and transformed to the following markup ... <a href="https://typo3.localhost/" class="page">visit</a> <div data-uri="https://typo3.localhost/" class="page trigger"> visit</div> Following Composer dependency is made explicit: composer req masterminds/html5:'^2.7' ext-dom:'*' Resolves: #95176 Releases: master Change-Id: Ib0101fbe120343dc404f0816da6d38946df0d931 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/70977 Tested-by:
Lina Wolf <112@linawolf.de> Tested-by:
-
- Sep 19, 2021
-
-
Christian Kuhn authored
Variable $uploadedFiles is carried around in DataHandler through various methods, but is in fact never used since TCA type=group with internal_type=file has been dropped in v10. The patch drops that argument. All method changes are detail implementations within DataHandler and either protected or marked @internal, the change does not raise backwards compatibility issues. Change-Id: I4ca56005d9e52255d3168358d16bbb66347d8974 Resolves: #95264 Related: #87428 Releases: master Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/71115 Tested-by:
-
- Sep 17, 2021
-
-
Nikita Hovratov authored
Since commit e09082f7 (v10 release) the possibility to override the preview header was gone. This patch moves the drawItem hook out of the renderPageModulePreviewContent method to be able to pass the before rendered previewHeader to it. Resolves: #91760 Relates: #90906 Releases: master Change-Id: Ia7d29333543d764f4ebaec0330df1817032dc8fe Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/68953 Tested-by:
-
Oliver Hader authored
Removes inline JavaScript from installer step "Create Administrative User & Specify Site Name". Also mark button as type="button" to avoid intercepting the form submit due to the toggling event handler. Resolves: #95266 Resolves: #95241 Releases: master Change-Id: I002fabc185bf8fdf88793abfdf6ca89b61847e3f Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/71121 Tested-by:
Simon Gilli <typo3@gilbertsoft.org> Tested-by:
-
Oliver Hader authored
Remaining individual inline JavaScript in `onclick` handler to open an URI in a new window is replaced with default frontend JavaScript (see #95041) in `AbstractPlugin::pi_openAtagHrefInJSwindow()`. Resolves: #95151 Releases: master Change-Id: I90e12d521efaf1a0ac0be0890c940f20b832aa21 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/70968 Tested-by:
Markus Klein <markus.klein@typo3.org> Reviewed-by:
-
Christian Kuhn authored
Methods FlexFormTools->getArrayValueByPath() and FlexFormTools->setArrayValueByPath() have well test covered counterparts in ArrayUtility since v7. Usages can be adapted easily and the outdated implementations can be deprecated. Change-Id: Ieb40369c883b95f6c7cc398cfdab3a9a08054b8f Resolves: #95254 Releases: master Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/71112 Tested-by:
Jochen <rothjochen@gmail.com> Tested-by:
-
