- Sep 11, 2024
-
-
Andreas Nedbal authored
This patch adds the ability to switch the active color scheme using multiple different methods in the Backend User Interface. The two main methods are a selection of buttons in the user dropdown at the top right of the Backend, the other one being a setting present in User Settings. Additionally, if the "auto" setting (default) is selected, the backend is automatically using the systems preferred color scheme. Considering the dark color scheme is still regarded as experimental, the switching capabilities are currently disabled using a UserTS setting 'setup.fields.colorScheme.disabled'. Resolves: #104868 Releases: main Change-Id: I6704fba0930ac579582f1d21dd11368b3509328a Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/85935 Reviewed-by:
Benjamin Franzke <ben@bnf.dev> Tested-by:
Benjamin Kott <benjamin.kott@outlook.com> Tested-by:
core-ci <typo3@b13.com> Tested-by:
Andreas Nedbal <andy@pixelde.su> Reviewed-by:
Benni Mack <benni@typo3.org> Reviewed-by:
-
Simon Praetorius authored
This patch enables a template processor included in Fluid 4 for all Fluid instances in the Core. The template processor strips `<f:comment>` tags from Fluid template strings before the parsing starts. This prevents Fluid errors when invalid Fluid code is used inside `<f:comment>`. Original change in Fluid: https://github.com/TYPO3/Fluid/commit/faad81a9f5d991d688e1d4c673e0d7aaf41a7e94 Resolves: #104904 Releases: main Change-Id: Ieebb60ee21ae9f8d6f168e75b9fd22a7103a5f6a Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/86012 Reviewed-by:
Guido Schmechel <guido.schmechel@brandung.de> Tested-by:
Andreas Kienast <a.fernandez@scripting-base.de> Tested-by:
Stefan Bürk <stefan@buerk.tech> Tested-by:
Simon Praetorius <simon@praetorius.me> Reviewed-by:
Mathias Brodala <mbrodala@pagemachine.de> Reviewed-by:
-
Benjamin Kott authored
We are dropping the Bootstrap CSS definitions for all modals to have more control about the styling of the modal elements. From now on we are shipping custom css adapted to our needs. The new modal element styling is context aware and adapts to light and dark color schemes. Resolves: #104911 Releases: main Change-Id: I98d619c407708f6d5c969cb98fc304786e4c0c44 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/86015 Reviewed-by:
-
Stefan Froemken authored
Add missing "App" node to example in Changelog of notification actions. Resolves: #104903 Releases: main, 12.4, 11.5 Change-Id: Icc88a55c731c7f5b517740673c24acd21b83fa12 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/86010 Reviewed-by:
-
Oliver Bartsch authored
The RecordInterface is extended to require implementations to implement the `getRawRecord()` and `getSystemProperties()` methods as well as the PSR-11 `ContainerInterface`. This allows to change RecordFactory's `createRecord()` method to return the interface instead of the `Record` object. This will come in handy e.g. for the already existing `Page` object, which can now be used without extending `Record`. By using the `ContainerInterface` we allow access to the record and its properties via the has() and get() methods, which is supported since Fluid 4.0: https://github.com/TYPO3/Fluid/issues/1001. Resolves: #104859 Releases: main Change-Id: Ib8d20dc4eea343bf1c2160dbab6d4301930792ee Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/85925 Reviewed-by:
Oliver Bartsch <bo@cedev.de> Tested-by:
-
Jochen Roth authored
Previously, it was possible to allow editors to modify colPos and CType in FormEngine via connected CEs. This has been changed when editing translated CEs, that CType and colPos cannot be changed anymore. An upgrade wizard is added to ensure that all translated CEs really contain the same colPos and CType values as their default language pendants. Both fields are now set to l10n_mode=exclude to avoid future inconsistencies. Resolves: #60357 Releases: main Change-Id: Id04636d8c131ce8fbc7c9a87d5fc13a6b406eec2 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/85978 Tested-by:
André Buchmann <andy.schliesser@gmail.com> Tested-by:
-
Simon Praetorius authored
This patch raises the minimum Fluid dependency to the just released Fluid 4. The Fluid team has taken great care to plan this switch in the Core by introducing a lot of changes in advance, both with minor releases of Fluid 2 and code changes in the Core to avoid now deprecated Fluid features. There are no new deprecations with this release. All deprecations have already been announced and documented in previous raises of Fluid 2.x in the Core. One recently added test case needs to be adjusted with this change to account for the feature described in the attached feature RST file. For a full changelog and more information about the release, dedicated release notes are available on GitHub: https://github.com/TYPO3/Fluid/releases/tag/4.0.0 Executed commands: ``` composer req typo3fluid/fluid:^4.0 composer req -d typo3/sysext/adminpanel --no-update typo3fluid/fluid:^4.0 composer req -d typo3/sysext/core --no-update typo3fluid/fluid:^4.0 composer req -d typo3/sysext/fluid --no-update typo3fluid/fluid:^4.0 composer req -d typo3/sysext/redirects --no-update typo3fluid/fluid:^4.0 ``` Resolves: #104896 Releases: main Change-Id: Ia40b2a62ba43303bdc094f763e103465a0d5a03e Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/86008 Reviewed-by:
-
Benjamin Franzke authored
Site local settings (defined in the sites settings.yaml file) need to be taken into account in the site overview, only if they are based on definitions. Therefore the setting map (which is based on definitions) has to be evaluated instead of the flat settings map (which contains all settings, defined and legacy anonymous settings). Releases: main Resolves: #104886 Related: #104794 Change-Id: I49f8d01c3947302ff75a6aac0e3e64cdeca819c8 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/85998 Tested-by:
-
Oliver Bartsch authored
Resolves: #104891 Releases: main, 12.4 Change-Id: I7431cd142a1b92e7ca14dcfe1b5720f9a627be04 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/86002 Reviewed-by:
Jochen Roth <rothjochen@gmail.com> Tested-by:
Nikita Hovratov <nikita.h@live.de> Reviewed-by:
-
Benjamin Kott authored
Resolves: #104893 Releases: main Change-Id: I9cbee0ca23f33d58ad99cabf3f7511fc4620b0d0 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/86003 Tested-by:
-
Benjamin Franzke authored
Resolves: #104892 Releases: main Change-Id: I55ad0f3da6807d2b8bd624a95613f3d612ddc788 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/86004 Reviewed-by:
Lina Wolf <112@linawolf.de> Tested-by:
-
Michael Schams authored
This patch updates the English labels shown in the TYPO3 Dashboard and Dashboard widgets for System Notes. Resolves: #104888 Releases: main Change-Id: I4ecb3886d30459823529052ef084daf715715873 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/86000 Reviewed-by:
Frank Nägler <frank.naegler@typo3.com> Reviewed-by:
-
- Sep 10, 2024
-
-
Benjamin Franzke authored
A new Site Settings editor has been introduced that allows to configure per-site settings in `config/sites/*/settings.yaml`. The new backend module `Site Management > Settings` provides an overview of sites which offer configurable settings and makes them editable based on Site Set provided Settings Definitions. The editor shows a list of settings categories and respective settings. It will persist all settings into `config/sites/*/settings.yaml`. The module will only persist settings that deviate from the site-scoped default value. That means it will only change the minimal difference to the settings set defined by the active sets for the respective site. The backend module is currently available for administrators only, but will likely be extended to be made available for editors in future. Anonymous (undefined) site settings – as supported since TYPO3 v10 – will not be made editable, but will be preserved as-is when persisting changes through the settings editor. Resolves: #104794 Releases: main Change-Id: I7eea8445b86b50efa498238daa3436f0940f4b78 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/84342 Tested-by:
-
Nikita Hovratov authored
The label of palettes can be overridden in showitem. These labels are now also removed to correctly find and remove this system palettes. Resolves: #104836 Related: #104814 Releases: main Change-Id: I322ffd71fcc062ad07ff9b59f2f8dd32a381668f Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/85902 Tested-by:
Georg Ringer <georg.ringer@gmail.com> Reviewed-by:
-
Benni Mack authored
Resolves: #104884 Related: #104844 Releases: main Change-Id: I6361b841eededc837702f9fbe61c236c7502abd0 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/85994 Tested-by:
-
Benjamin Franzke authored
Executed commands: npm install @typo3/icons@4.3.1 npm run build Resolves: #104883 Releases: main, 12.4 Change-Id: Ib7b903322a566fbdeee5c336c1a755d8ba638ae0 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/85993 Tested-by:
-
ullio authored
This patch adds a new widget for EXT:dashboard, which shows a list of the latest changed pages inside the TYPO3 system. Resolves: #104878 Releases: main Change-Id: I33f86e1cc8d4a546136bb179f19f6338e2e734f3 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/85987 Reviewed-by:
-
Philipp Kuhlmay authored
This adds some widgets for EXT:dashboard, which shows a list of the corresponding sys_notes inside the TYPO3 system. The widgets are copied from EXT:treupo_sys_note_widgets which will not be developed further, as all the widgets are now inside the TYPO3 core. Resolves: #104844 Releases: main Change-Id: Iec0a1bef30919d96db282904885d8084ac02ac2c Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/85899 Tested-by:
-
Benjamin Kott authored
Resolves: #104881 Releases: main Change-Id: I9547fb7c2ef3e1c78856ace3577121388cb7720b Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/85991 Tested-by:
-
Benjamin Kott authored
Resolves: #104880 Releases: main Change-Id: Ibd6cf85648d6c6642281d9a879d8a314c8bbc097 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/85990 Tested-by:
-
Benjamin Kott authored
Resolves: #104879 Releases: main Change-Id: I849c23627ad2d8e0579d99690fa1da623d44b606 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/85989 Tested-by:
-
Markus Klein authored
Adds the possibility to configure Redis key prefixes for cache and session backends, which allows to use the same Redis database for multiple caches and/or TYPO3 instances. Resolves: #104451 Releases: main Change-Id: Id6aa2f7ba9a4a0dbfb2335150602aeb836e09b90 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/85324 Tested-by:
-
Oliver Bartsch authored
Because the Localization\State does currently not support columnsOverrides, the localization state selector wizard throws an exception when setting allowLanguageSynchronization via columnsOverrides. This is now mitigated by removing the non working option from TCA via TcaMigration and informing the integrator about it. Additionally is the Localization\State checked in the wizard and an early return is done to prevent null pointer exceptions. Resolves: #104693 Resolves: #104403 Releases: main, 12.4 Change-Id: Ice719b2b198a6bc26abf0866ecae6c11da20cbea Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/85721 Tested-by:
Oliver Hader <oliver.hader@typo3.org> Reviewed-by:
-
André Buchmann authored
The viewhelpers f:asset.css and f:asset.script are great but missed an option to render referenced files inline. A boolean option "inline" is now added to load the file contents as inline styles or scripts. This is especially useful for content elements which are used first in a page and need some custom css to improve the Cumulative Layout Shift (CLS). Resolves: #99510 Releases: main Change-Id: Ic4282cd4a6ff00594a0aa0cbdf51f49d80806489 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/84424 Tested-by:
Garvin Hicking <gh@faktor-e.de> Tested-by:
-
Thomas Hohn authored
If the 'contentSecurityPolicies' value is not filled properly in the site configuration, the call to $site->getConfiguration()['contentSecurityPolicies'] will fail. The access should we guarded with a null coalescing operator. Resolves: #104873 Releases: main, 12.4 Change-Id: Ie49a25d8ca9a194629c4a389b17b299091d44031 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/85977 Reviewed-by:
-
Benjamin Franzke authored
Labels for site sets and site settings – as added in #104831 - are now verified for completenes. The script checkIntegritySetLabels.php checks for required and optional labels to ensure labels.xlf and settings.definitions.yaml are in sync. Resolves: #104867 Related: #104831 Releases: main Change-Id: I7c91d9ce1fe79ac3137a06b53010fe36418cc896 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/85931 Reviewed-by:
-
Ayke Halder authored
This changes disabled record-action-buttons in workspace-review to use a `button`-tag with `disabled`-attribute. Thereby screenreaders can announce that a button is disabled. Before this a disabled record-action-button was rendered as `span`-tag with `class="disabled"`. Resolves: #104820 Releases: main Change-Id: I87214050361101ac85807c471ec41f362617fe05 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/85871 Tested-by:
-
Andreas Kienast authored
The package `mime-db` received some updates since its introduction, hence it is now updated to its latest version. Executed commands: cd Build npm install --save-dev mime-db@^1.53.0 ./Scripts/generateMimeTypes.php Resolves: #104743 Releases: main, 12.4, 11.5 Change-Id: I756eed3e8d1a6b02f7b2f855dc63623a0c97245e Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/85788 Reviewed-by:Wouter Wolters <typo3@wouterwolters.nl> Reviewed-by:
-
Benjamin Kott authored
We are removing the misused has-changed class for new records and replacing it with a dedicated is-new class. This class is used only to check if a record needs to be persisted before certain actions, such as closing or previewing a record, can be executed. Resolves: #104690 Related: #87890 Related: #104676 Releases: main, 12.4 Change-Id: Ie0ddd119de860f9539acc9d1353428529afa7f83 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/85975 Tested-by:
-
Ayke Halder authored
This changes the `disabled`-attribute of the recycler's search-submit-button. Thereby screen- readers can announce that the button is disabled. Before this there was toggling implemented for `class="disabled"`. Thereby the 'disabled' button was still active and could be activated by keyboard. Resolves: #104817 Releases: main Change-Id: Ifb99481624c5cc24f590c7e9d0f3a61ab9f997aa Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/85870 Reviewed-by:
-
Ayke Halder authored
This changes the `disabled`-attribute of the multi-record-selection buttons. Thereby screenreaders can announce that a button is disabled. Before this there was toggling implemented for `class="disabled"`. Thereby a 'disabled' button was still active and could be activated by keyboard. Multi-record-selection buttons are implemented in these sections: * TCA: SelectCheckboxElement * TCA: TablePermissionElement * backend: record-list * filelist: list * recycler: list * redirects: overview * scheduler: task-list * webhooks: overview * workspaces: record-table Resolves: #104703 Releases: main Change-Id: I178d430ea9b0da7c7aa43f9b203375eb56052f00 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/85731 Reviewed-by:
-
Benjamin Kott authored
We are dropping the Bootstrap CSS definitions for all navs to have more control about the styling of the nav elements. From now on we are shipping custom css adapted to our needs. The new nav element styling is context aware and adapts to light and dark color schemes. Resolves: #104865 Releases: main Change-Id: I8632b33c48162cbb407dc2b2a99eaab00518c635 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/85936 Tested-by:
-
Oliver Bartsch authored
The `AsController` has been added to v12 next to the `Controller` attribute. Later has been deprecated in v13 and will be removed in v14. Resolves: #104871 Related: #102631 Releases: main Change-Id: I4cdaff914faaff8f7eb8d4706ec226374c694142 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/85972 Reviewed-by:
-
Oliver Bartsch authored
Clean up of field types for TcaSchema. In detail: * Removes duplicate interface implementation * Move __set_state() to abstract * Introduces FieldFormat enum * Extends some FieldType's for convenience methods * Extends TcaSchema::getFields() to support list of fields * Adds styleguide example for type=none with format configuration Resolves: #104741 Releases: main Change-Id: I06afc6d52eb0f5fa299ffef5701f178378f7c942 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/85786 Tested-by:
-
Oliver Bartsch authored
Move TypolinkParameter to EXT:core and therefore remove a dependency from EXT:core to EXT:frontend. Resolves: #104869 Related: #104615 Releases: main Change-Id: I7474d31a722a4e27438461b8812e25299f0a72cb Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/85937 Tested-by:
-
Oliver Hader authored
Since AccessLifetime is allowed to be use in any module/route configuration, it should not be marked `@internal`. Resolves: #104870 Releases: main, 12.4 Change-Id: I7614f537e07d5d4c762bf1dc1ac42b0d5c91de87 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/85938 Tested-by:
-
- Sep 09, 2024
-
-
Stefan Bürk authored
PHPStan released a new version containing a bug starting to report an error if a class extends the native PHP `\SplObjectStorage` class [1]: Non-abstract class ... contains abstract method seek() from interface SeekableIterator. Sadly, this is a not-ignorable error and cannot be added to the baseline. This change upgrades the version to the faulty version and excludes the one file meanwhile. Not good, but the only suitable solution for now. Used command(s): > Build/Scripts/runTests.sh -s composer -- \ require --dev "phpstan/phpstan":"^1.12.3" [1] https://github.com/phpstan/phpstan/issues/11665 Resolves: #104866 Releases: main, 12.4 Change-Id: I8241b02310e6da3cff0292d1d37c8e69862ffb9a Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/85932 Tested-by:Christian Kuhn <lolli@schwarzbu.ch> Tested-by:
-
Christian Kuhn authored
Let's raise min versions of dependencies as much as we can in preparation of a good baseline for LTS. > composer req psr/log:^3.0.1 > composer req psr/log:^3.0.1 -d typo3/sysext/core --no-update > composer req psr/log:^3.0.1 -d typo3/sysext/redirects --no-update > composer req psr/http-client:^1.0.3 > composer req psr/http-client:^1.0.3 -d typo3/sysext/core --no-update > composer req typo3/cms-composer-installers:^5.0.1 > composer req typo3/cms-composer-installers:^5.0.1 -d typo3/sysext/core --no-update > composer req typo3/cms-cli:^3.1.1 > composer req typo3/cms-cli:^3.1.1 -d typo3/sysext/core --no-update > composer req nikic/php-parser:^5.1.0 > composer req nikic/php-parser:^5.1.0 -d typo3/sysext/install --no-update > composer req doctrine/annotations:^2.0.2 > composer req doctrine/annotations:^2.0.2 -d typo3/sysext/core --no-update > composer req doctrine/dbal:^4.1.1 > composer req doctrine/dbal:^4.1.1 -d typo3/sysext/core --no-update > composer req doctrine/dbal:^4.1.1 -d typo3/sysext/install --no-update > composer req doctrine/dbal:^4.1.1 -d typo3/sysext/redirects --no-update > composer req doctrine/event-manager:^2.0.1 > composer req doctrine/event-manager:^2.0.1 -d typo3/sysext/core --no-update > composer req doctrine/lexer:^3.0.1 > composer req doctrine/lexer:^3.0.1 -d typo3/sysext/core --no-update > composer req masterminds/html5:^2.9.0 > composer req masterminds/html5:^2.9.0 -d typo3/sysext/core --no-update > composer req phpdocumentor/reflection-docblock:^5.4.1 > composer req phpdocumentor/reflection-docblock:^5.4.1 -d typo3/sysext/extbase --no-update > composer req phpdocumentor/type-resolver:^1.8.2 > composer req phpdocumentor/type-resolver:^1.8.2 -d typo3/sysext/extbase --no-update > composer req symfony/console:^7.1.4 symfony/dependency-injection:^7.1.4 \ symfony/doctrine-messenger:^7.1.4 symfony/expression-language:^7.1.4 \ symfony/filesystem:^7.1.2 symfony/finder:^7.1.4 \ symfony/http-foundation:^7.1.3 symfony/mailer:^7.1.2 \ symfony/messenger:^7.1.4 symfony/mime:^7.1.4 symfony/process:^7.1.3 \ symfony/property-access:^7.1.4 symfony/property-info:^7.1.3 \ symfony/routing:^7.1.4 symfony/uid:^7.1.4 \ symfony/var-dumper:^7.1.4 symfony/yaml:^7.1.4 \ -w > composer req symfony/var-dumper:^7.1.4 -d typo3/sysext/adminpanel --no-update > composer req symfony/console:^7.1.4 symfony/dependency-injection:^7.1.4 \ symfony/doctrine-messenger:^7.1.4 symfony/expression-language:^7.1.4 \ symfony/filesystem:^7.1.2 symfony/finder:^7.1.4 \ symfony/http-foundation:^7.1.3 symfony/mailer:^7.1.2 \ symfony/messenger:^7.1.4 symfony/mime:^7.1.4 symfony/process:^7.1.3 \ symfony/routing:^7.1.4 symfony/uid:^7.1.4 \ symfony/yaml:^7.1.4 \ -d typo3/sysext/core --no-update > composer req symfony/dependency-injection:^7.1.4 \ symfony/property-access:^7.1.4 symfony/property-info:^7.1.3 \ -d typo3/sysext/extbase --no-update > composer req symfony/dependency-injection:^7.1.4 -d typo3/sysext/fluid --no-update > composer req symfony/expression-language:^7.1.4 -d typo3/sysext/form --no-update > composer req symfony/finder:^7.1.4 symfony/http-foundation:^7.1.3 \ -d typo3/sysext/install --no-update > composer req symfony/console:^7.1.4 -d typo3/sysext/redirects --no-update > composer req symfony/uid:^7.1.4 -d typo3/sysext/webhooks --no-update > composer req --dev composer/composer:^2.7.8 -w > composer req --dev phpunit/phpunit:^11.3.1 -w > composer req --dev friendsofphp/php-cs-fixer:^3.64.0 -w > composer req --dev phpstan/phpdoc-parser:^1.30.0 > composer req --dev symfony/translation:^7.1.3 > composer u dasprid/enum phpunit/php-code-coverage Resolves: #104788 Releases: main Change-Id: If4ee0a93483e5ff854a4d893304406b7d9bf1490 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/85836 Tested-by:
-
Lina Wolf authored
Releases: main Resolves: #104864 Change-Id: I0c5ee461bb9ea124c9e2931386e1b301b8d1f5f3 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/85930 Tested-by:
-
Simon Praetorius authored
A previous patch already avoided calls to the constructor of `TemplatePaths`, which is deprecated if called with an argument since Fluid v2.15. This follow-up covers remaining places. Furthermore, both usages of `GeneralUtility::makeInstance()` are converted to `new` to harmonize the creation of those objects in the Core. Now every occurrences use `new`. `ksort()` is removed because this is done internally in `TemplatePaths` setters. It was necessary before because of the merging behavior of `extractPathArrays()`, which is no longer used now (and is also deprecated in Fluid). Resolves: #104860 Related: #104823 Releases: main Change-Id: Ic16638e8512f6272dbd52bbf0f65fb405b8483cf Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/85926 Tested-by:
-
