- Feb 16, 2024
-
-
Oliver Bartsch authored
To allow `BackendUtility::getProcessedValue()` to properly resolve the labels for select options, added via TSconfig, the `pid` is now provided by `StandardContentPreviewRenderer`. Resolves: #103076 Releases: main, 12.4 Change-Id: I20777ae532b66800ea61143e1824c895c7673042 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/82978 Tested-by:
Oliver Bartsch <bo@cedev.de> Reviewed-by:
core-ci <typo3@b13.com>
-
- Feb 15, 2024
-
-
Christian Kuhn authored
There is no point to substitute GU::trimExplode() of the rather short TCA 'eval' string by substituting it with an md5() operation plus runtime cache object operations. Both things are most likely similarily quick, and the time consumed by queries in DH is multiple orders of magnitude bigger than this simple operation, a difference is not measurable. Let's thus simplify the code a bit. Resolves: #103125 Releases: main, 12.4 Change-Id: I474d3fbe6b503a99a9129856b0f59c777b171844 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/82977 Tested-by:
Oliver Klee <typo3-coding@oliverklee.de> Tested-by:
Christian Kuhn <lolli@schwarzbu.ch> Tested-by:
-
Oliver Bartsch authored
The EXT:form "version2" is using bootstrap 5, which requires <select> elements to use the `form-select` class. This is now fixed for corresponding form elements. Resolves: #103117 Releases: main, 12.4 Change-Id: I712cecfa4c5ac8facc84bc3cf0f742867ecc9613 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/82976 Reviewed-by:
-
Torben Hansen authored
Install tool suggests to set `$GLOBALS['TYPO3_CONF_VARS']['GFX']['processor_colorspace'] = sRGB` if images appear too dark. In general this is the correct suggestion, but the value must be quoted. This change adds the missing single quotes for the value. Resolves: #103124 Releases: main, 12.4 Change-Id: I2e1fd2ebebf1d67870145df29ec0e40b330a5065 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/82975 Tested-by:
-
- Feb 14, 2024
-
-
Oliver Bartsch authored
Due to the previously used pagination, the "items per page" option has been reset when searching in the record list. However, since the "new" pagination is able to handle such filtered list, resetting the "items per page" option is no longer necessary and therefore makes lists with a lot of matched items usable again. Resolves: #103107 Releases: main, 12.4 Change-Id: Ibeb5a65666a3796f98d3dd61c9efc0bd3bfb0c72 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/82974 Tested-by:
-
Nikita Hovratov authored
The BootCompletedEvent receives the constructor argument `$cachingEnabled`. However, the variable `$disableCaching` was passed in Bootstrap::init() which is the exact opposite. In fact, the caching is logically always enabled when reaching the dispatched event. Resolves: #103114 Releases: main, 12.4 Change-Id: I81c26027bb8e2cb4009fbfcd0bfd6015bd9c1dec Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/82973 Reviewed-by:
Nikita Hovratov <nikita.h@live.de> Tested-by:
-
Oliver Bartsch authored
It's now possible to use a TCA type `group` field as `foreign_selector` together with the `useCombination` functionality. The corresponding "child child table" information is in this case fetched from the `allowed` option. Side note: Using TCA type `group` for a `foreign_selector` field is not really documented, but it's also not forbidden. Actually, it's a valid use case and also working quite well as the new styleguide examples demonstrate. However, the documentation should be adjusted to mention that only one table can be defined in `allowed` for such fields. Resolves: #102904 Releases: main, 12.4 Change-Id: Icdde6a8acb1fb9166da8e6259758f6bf64d6c41f Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/82994 Tested-by:
-
- Feb 13, 2024
-
-
Andreas Kienast authored
This commit updates ckeditor5 to v41.1. See changelog at https://github.com/ckeditor/ckeditor5/releases/tag/v41.1.0. Executed commands: npm i --save \ @ckeditor/ckeditor5-alignment@^41.1.0 \ @ckeditor/ckeditor5-autoformat@^41.1.0 \ @ckeditor/ckeditor5-basic-styles@^41.1.0 \ @ckeditor/ckeditor5-block-quote@^41.1.0 \ @ckeditor/ckeditor5-clipboard@^41.1.0 \ @ckeditor/ckeditor5-code-block@^41.1.0 \ @ckeditor/ckeditor5-core@^41.1.0 \ @ckeditor/ckeditor5-editor-classic@^41.1.0 \ @ckeditor/ckeditor5-engine@^41.1.0 \ @ckeditor/ckeditor5-essentials@^41.1.0 \ @ckeditor/ckeditor5-find-and-replace@^41.1.0 \ @ckeditor/ckeditor5-heading@^41.1.0 \ @ckeditor/ckeditor5-horizontal-line@^41.1.0 \ @ckeditor/ckeditor5-html-support@^41.1.0 \ @ckeditor/ckeditor5-indent@^41.1.0 \ @ckeditor/ckeditor5-link@^41.1.0 \ @ckeditor/ckeditor5-list@^41.1.0 \ @ckeditor/ckeditor5-paragraph@^41.1.0 \ @ckeditor/ckeditor5-paste-from-office@^41.1.0 \ @ckeditor/ckeditor5-remove-format@^41.1.0 \ @ckeditor/ckeditor5-show-blocks@^41.1.0 \ @ckeditor/ckeditor5-source-editing@^41.1.0 \ @ckeditor/ckeditor5-special-characters@^41.1.0 \ @ckeditor/ckeditor5-style@^41.1.0 \ @ckeditor/ckeditor5-table@^41.1.0 \ @ckeditor/ckeditor5-theme-lark@^41.1.0 \ @ckeditor/ckeditor5-ui@^41.1.0 \ @ckeditor/ckeditor5-undo@^41.1.0 \ @ckeditor/ckeditor5-utils@^41.1.0 \ @ckeditor/ckeditor5-word-count@^41.1.0 npm i --save-dev \ @ckeditor/ckeditor5-dev-utils@^39.6.0 npm run build Resolves: #103069 Releases: main, 12.4 Change-Id: I571ccb8d8531108f99272f6c4cf11c351d3f5692 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/82971 Reviewed-by:
Andreas Kienast <a.fernandez@scripting-base.de> Tested-by:
-
Stefan Bürk authored
The constant editor has been revamped with #98357 using the new TypoScript parser introduced with TYPO3 v12 under the hood. For category and subCategory handling lower-cased keys have been used, missing to lower-case the custom categories and subcategories names (keys) integrator are able to add since aeons. That leads to a failing match later on, and adding constants to the generic `other` subcategory. The revamped code supports only one category per subCategory sorting value. The documentation say that this **should** be omitted, but it worked in the past and broke with the revamped implementation. This change fixes muliple issues with the constant editor: * Ensure that custom categories and subcategories are read lower-case, otherwise later lookup will fail and sorted into sub-categorie `other`. * Add addtional array level to have `subCategory->items` per second sorting value as array (to avoid overriding). * Add additional item loop to the fluid template to respect the additional array level. Note: In the past it was possible to display a constant in multiple categories/subcategories by adding them again with different category configure comment lines. This is not supported anymore and not considered as bug. Resolves: #103088 Related: #98357 Related: #97816 Releases: main, 12.4 Change-Id: I4403420cc957cdef4bf077365deac0f7af621c71 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/82972 Tested-by:
Stefan Bürk <stefan@buerk.tech> Reviewed-by:
-
Oliver Hader authored
Change-Id: I706b9d7328f06eff3e7f7fb86ae3a3138615bfd4 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/82966 Tested-by:
Oliver Hader <oliver.hader@typo3.org> Tested-by:
-
Oliver Hader authored
Change-Id: Ibd1ea27ced45de785a6a417758b33a0461a97d97 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/82965 Reviewed-by:
-
Oliver Hader authored
Write access to table `sys_file` is denied per default, unless data is being imported. In addition, write access to related FAL entities `sys_file_reference` and `sys_file_metadata` is denied in case a file on legacy storage (uid=0) is used or corresponding user does not have permissions to access a particular file. Resolves: #93969 Releases: main, 13.0, 12.4, 11.5 Change-Id: Ic8ac7132d732bd117aa63f6a33545ceb1d1f421d Security-Bulletin: TYPO3-CORE-SA-2024-006 Security-References: CVE-2024-25121 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/82950 Tested-by:
-
Benjamin Franzke authored
Resolves: #93571 Releases: main, 13.0, 12.4, 11.5 Change-Id: I9622bfa47ef9637cecaff4a790f742445f598682 Security-Bulletin: TYPO3-CORE-SA-2024-005 Security-References: CVE-2024-25120 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/82949 Reviewed-by:
-
Benjamin Franzke authored
The encryptionKey is a secret that must never be sent within any request, therefore it is now dropped from the editing interface in "Configure Installation-Wide Options". Resolves: #103046 Releases: main, 13.0, 12.4, 11.5 Change-Id: I260a8a2e9af29908543dfe48ac3658d8c45cc440 Security-Bulletin: TYPO3-CORE-SA-2024-004 Security-References: CVE-2024-25119 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/82948 Reviewed-by:
-
Oliver Hader authored
Backend form fields of TCA `type=password` should never expose the persisted value - especially, in case the value is explicitly configured not to be hashed (having TCA `hashed=false`). Resolves: #101965 Releases: main, 13.0, 12.4, 11.5 Change-Id: Ie05a708185c621b8a2120ad7851ac4caf180893f Security-Bulletin: TYPO3-CORE-SA-2024-003 Security-References: CVE-2024-25118 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/82947 Reviewed-by:
-
Benjamin Franzke authored
Resolves: #102799 Releases: main, 13.0, 12.4, 11.5 Change-Id: I673b6fbac853b0a977a5e5833a683c6952a55458 Security-Bulletin: TYPO3-CORE-SA-2024-002 Security-References: CVE-2024-22188 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/82946 Tested-by:
-
Oliver Hader authored
The File Abstraction Layer Local Driver did not verify whether a given absolute file path is allowed, and made it possible to access files outside of the project path, and to by-pass the setting in $GLOBALS['TYPO3_CONF_VARS']['BE']['lockRootPath']. In case lockRootPath is not set, any local file path must be at least located in the base directory of the current project. The lockRootPath setting now supports array values as well. The trailing slash is enforced automatically. Example: * instead of 'lockRootPath=/var/spe' previously matching the paths '/var/specs/' and '/var/specials/, * now both paths need to be declared explicitly, since 'lockRootPath=/var/spe' is evaluated as '/var/spe/' Resolves: #102800 Releases: main, 13.0, 12.4, 11.5 Change-Id: I6561df562c5dbaff1f77d33db24d5f1c6358b198 Security-Bulletin: TYPO3-CORE-SA-2024-001 Security-References: CVE-2023-30451 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/82945 Reviewed-by:
-
Benjamin Franzke authored
The autocomplete="off" parameter is ignored by current browsers, autocomplete="new-password" is to be used for disable autocompletion. The explicit request for autocompleting the password is autocomplete="current-password", which is now used in case config TCA autocomplete is set. See following article for more information: * https://web.dev/articles/sign-in-form-best-practices#new-password * https://web.dev/articles/sign-in-form-best-practices#current-password Resolves: #103067 Related: #97104 Releases: main, 12.4 Change-Id: Ice3c7a50020d7e17b14c51dc89c1c8e1700fe9a6 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/82836 Tested-by:
Benjamin Franzke <ben@bnf.dev> Reviewed-by:
-
Stefan Bürk authored
A new PHPStan version has been releases, which is pulled in automatically in the composerInstallMax nightly test. The higher version allows to remove a ignore pattern from the baseline and a superfluous key unset is detected. This change raises the PHPStan version, removes the superfluous `unset()` and regenerates the baseline to remove the invalid ignore pattern. Used command(s): > Build/Scripts/runTests.sh -s composer \ -- require --dev "phpstan/phpstan":"^1.10.58" > Build/Scripts/runTests.sh \ -s phpstanGenerateBaseline Resolves: #103105 Releases: main, 13.0, 12.4 Change-Id: I689079eaac7f9461084e6a71ff08ef716cf551e4 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/82933 Reviewed-by:
-
- Feb 12, 2024
-
-
Oliver Hader authored
Executed command: composer update composer/composer see https://github.com/advisories/GHSA-7c6p-848j-wh5h Resolves: #103102 Releases: main, 13.0, 12.4, 11.5 Change-Id: Ib3a0baa5c94f0a19b36b8440a30f47f25eab6e65 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/82901 Tested-by:
Markus Klein <markus.klein@typo3.org> Tested-by:
-
Oliver Bartsch authored
This fixes several bugs in FileList: 1. Properly initializing the `searchTerm` ensures it is kept while sorting. 2. Sorting for "filesize" is now working properly, using corresponding collator attribute. 3. Pagination is properly reset on searching. 4. Correct search term is kept on paginating. Resolves: #103053 Releases: main, 12.4 Change-Id: Ibf7dd278d13aed6142286d7408b9380588485801 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/82850 Tested-by:
-
Sybille Peters authored
Since the linktypes are automatically registered in Linkvalidator, it is no longer quite as easy to replace the "external" linktype. You cannot register another linktype using the same identifier "external", so a different identifier must be used. A minimal example is added to the developer section in the documentation. Resolves: #101673 Related: #96935 Releases: main, 12.4 Change-Id: I9afa1a77fe56675dff2dbc1bacc3635b1b9b36c6 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/82849 Tested-by:
Benni Mack <benni@typo3.org> Reviewed-by:
-
- Feb 11, 2024
-
-
Oliver Bartsch authored
The query for fetching extension versions is extended to also find "outdated" extension versions (review_state = -2). Note: For now, this does not change anything in the EM, since the remote XML does not use the -2 state currently, due to the wrong constraint. This can however now be properly fixed in XML. Resolves: #93082 Releases: main, 12.4, 11.5 Change-Id: I522a2c166c6d1af6e8b2a14de51d63a15c4211d2 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/82847 Reviewed-by:
-
Torben Hansen authored
The language labels for `noPluginSelected` and `edit` in StandardContentPreviewRenderer can not be resolved, because the extension path is wrong. This change fixes the extension path and additionally streamlines one label output, by using `htmlspecialchars` to escape the generated label similar to the other label output in this class. Additionally a similar wrong extension path in `ExampleLinkType.rst.txt` has been adapted. Resolves: #103095 Related: #100675 Releases: main, 12.4 Change-Id: I4882133025c938fc3b6928b36237e782e9465dcc Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/82846 Tested-by:
-
- Feb 10, 2024
-
-
Oliver Hader authored
Resolves: #103097 Releases: 12.4, 11.5 Change-Id: I9280a8489cd0b301a1d9c66efc8428bad206cb8c Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/82890 Reviewed-by:
-
Stefan Bürk authored
New core-testing-* images have been build and published in the TYPO3 testing-infrastructure repository and pulled to the core ci gitlab runner instances. [1][2] This change modifies `Build/Scripts/runTests.sh` to set new image version to ensure the usage for all changes based on this change. For information what changed in the image see the patches in the testing-infrastrucure repository linked below. * core-testing-php81 => 2.11 * core-testing-php82 => 1.10 * core-testing-php83 => 1.11 [1] https://git.typo3.org/typo3/CI/testing-infrastructure/-/commit/e6719d303eacf2f377e308c800b474b735145d61 [2] https://github.com/advisories/GHSA-7c6p-848j-wh5h Resolves: #103096 Releases: main, 13.0, 12.4, 11.5 Change-Id: If9c5ae00334acc4fa5a1417dcbf9f77d31dff62d Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/82886 Reviewed-by:
-
- Feb 09, 2024
-
-
Yann authored
An editor can trigger a TypeError exception leading to a 503 error message `trim() expects parameter 1 to be string, null given` in the backend page module by creating `menu_categorized_content` objects with `selected_categories` and then turning them into `menu_section` objects. This change mitigates the type error by using a null-coalesce fallback passing an invalid type to the `trim()` method in `StandardContentPreviewRenderer::generateListForMenuContentTypes()`. Resolves: #103052 Releases: main, 12.4, 11.5 Change-Id: I4c0ecbd20c7cdfee22fa324f6b80391be47a1b88 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/82845 Tested-by:
-
Oliver Bartsch authored
The "Export" button in the list module, used to trigger exporting a table does now also respect the `options.impexp.enableExportForNonAdminUser` TSconfig option, preventing a permission exception. The `mod.web_list.noExportRecordsLinks` is no longer used for managing the display of the "Download" button (displayed in the table's header row), but instead a dedicated TSconfig option `mod.web_list.displayRecordDownload` is introduced. Using per-table syntax, it's also possible to manage the "Download" Button for each table individually. Resolves: #99781 Releases: main, 12.4 Change-Id: I8b967218626ecc05dccf4bd7ac441db56a21a753 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/82883 Tested-by:
-
Oliver Bartsch authored
The ExtendedFileUtility component provides the file name as argument for the `fileNotDeletedHasReferences` label. This information is now displayed correctly by adding the missing placeholder to the label. Resolves: #103091 Releases: main, 12.4 Change-Id: Ic9e40034bdf4f3d14e874014210e5d22235cd8c8 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/82843 Tested-by:
-
Thomas Hohn authored
The so called "death star" range for replacements has to be used with caution [1] as it replaces all versions of the replaced packages, including old or insecure versions. That effectively means the replacing package marks itself as matching in queries for insecure versions, once a security advisory[2] is submitted for the replaced packages. The extension replacements are now adapted to use the more precise self.version qualifier to avoid matching named security advisories as suggested by: https://github.com/Roave/SecurityAdvisories/issues/127#issuecomment-1933647035 [1] https://getcomposer.org/doc/04-schema.md#replace [2] https://github.com/advisories/GHSA-cgr9-h9qq-x9fx Resolves: #103082 Releases: main, 13.0, 12.4, 11.5 Change-Id: I6353df15d6cbf039bab60644a103669495b26605 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/82874 Tested-by:
-
Andreas Kienast authored
In some cases it was missed to enable modal actions again after their execution in the Install Tool. This patch adds the necessary statements to enable said buttons again. Resolves: #101224 Releases: main, 12.4 Change-Id: I793f157302df15912f0506c376d9db2d6041ebcc Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/82871 Tested-by:
-
Andreas Kienast authored
Executed commands: npm install --save sortablejs@^1.15.2 npm run build Resolves: #103064 Releases: main, 12.4 Change-Id: I34c76bbd6b856c10a7a420d6fe652a47fbf0e095 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/82868 Tested-by: -
Benni Mack authored
This change ensures that `?id=` only validates against an integer-interpreted value, disallowing `?id=nonsense23` which previously resolved to "23" In case an invalid `?id=` parameter value is provided throw a page not found error. Resolves: #103057 Releases: main, 12.4 Change-Id: Iaeb3096944b6872b73b056b690bf4f7fabbe9a6b Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/82867 Tested-by:
-
- Feb 08, 2024
-
-
Benjamin Kott authored
The configured browser capabilities (`chromeOptions`) are passed by `codeception/module-webdriver` to `php-webdriver` as is. php-webdriver expects the PHP constant ChromeOptions::CAPABILITY to be used instead of hardcoding any strings. Therefore php-webdriver 1.15 changed this constants value from `chromeOptions` to `goog:chromeOptions` [1], which means that the option `chromeOptions` is no longer respected and the configured window size (and the headless flag) is ignored. We now use the newer W3C webdriver comaptible `goog:chromeOptions` option and define window size definition via codeception's respective option `window_size` while we are at it. [1] https://github.com/php-webdriver/php-webdriver/commit/235c2aa07 Resolves: #103081 Releases: main, 12.4 Change-Id: Iec345b5ec0226d38b62081aa8c3a51dd3100bdb7 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/82840 Tested-by:
-
- Feb 07, 2024
-
-
Simon Schaufelberger authored
A new test case is added to cover the case when a TCA definition exists without `ctrl`. The test case has been added to the test extension `blog_example` which is not part of the public extension. Resolves: #103025 Releases: main, 12.4, 11.5 Change-Id: Iccd4428ad544fd6a94ed48ec97264b2945463d04 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/82790 Tested-by:
-
Stefan Bürk authored
This change adds a composer command dispatcher to `Build/Scripts/runTests.sh` to allow the execution of any composer command without the hassle to have a proper composer installed on the host system. This also helps for onboarding new contributors not having a proper php and composer ecosystem installed on the host system. For example, to raise dependencies following can now be used: > Build/Scripts/runTests.sh -s composer -- require --dev \ typo3/testing-framework:dev-main Other examples: > Build/Scripts/runTests.sh -s composer -- dumpautoload > Build/Scripts/runTests.sh -s composer -- info | grep "symfony" Resolves: #103045 Releases: main, 12.4, 11.5 Change-Id: I65fa14e2c8d0d1a1204b3bed701d8c3458b6e3bb Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/82838 Reviewed-by:
-
Stefan Bürk authored
During branching for TYPO3 v13 the GitLab workflow cache keys has been adjusted. However, the generic cache key has been missed. Use the correct one now. Resolves: #103068 Releases: 12.4 Change-Id: I16a5e7e7bfbd9f1ca4c50d8057d1edfaae5b66c1 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/82831 Tested-by:
-
Andreas Kienast authored
Executed commands: npm install --save-dev sass@^1.17.0 npm run build Resolves: #103065 Releases: main, 12.4 Change-Id: Id8d3ad111a751299266bdc3abe59c54a15df010c Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/82835 Tested-by:
-
- Feb 06, 2024
-
-
Dimitri König authored
There have been quite a lot of patches around the pagelayout condition, which was introduced in early TYPO3 v11. It was broken in the beginning and got fixed with #98044. Soon after, a major refactoring of the ConditionMatcher has been applied with #100047, which re-introduced bugs regarding the pagelayout TypoScript condition. These have partially fixed with #100764 and #100921. The affected code is a bit messy due to a weird sorted array returned by the 'rootline' methods and classes, which we can't resolve right now. The fix itself revolves a last issue by reversing the rootline again. This was already done in the old backend ConditionMatcher. The frontend ConditionMatcher received the fullRootline, which is already reversed (deepest first). With the introduction of IncludeTreeConditionMatcherVisitor this has been unified, but the array_reverse was forgotten. In addition, the fullRootline from the frontend controller and BackendUtility::getPagesTSconfig() calls are sorted with `ksort` before passed over, meaning we always receive a top-down (root-first) rootline. Hence, the array_reverse is a viable fix for both backend and frontend. The patch covers BE pageTS, FE TypoScript and FE getData with tests to cover the situation once and for all. Resolves: #102268 Related: #100047 Related: #100764 Related: #100921 Related: #98044 Related: #97816 Releases: main, 12.4 Change-Id: Ibec77f3cf63073e40e4a711d69f584b9265b1ad6 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/82743 Reviewed-by:
-
Stefan Bürk authored
Doctrine DBAL 3.8.x comes with further deprecations, but also with the new `QueryBuilder::reset*()` methods as a mitigation for the deprecated generic QueryBuilder methods `resetQueryParams()` and `resetQueryParam()`. See [1] for release notes and [2] for changes from current minimum version towards 3.8.1. Raising the minimum version ensures that extension authors are able to create TYPO3 v12 and v13 compatible code. At least, they can rely on it with the TYPO3 release containing this change for non-Composer and Composer mode. Used command(s): > \ composer req --no-update --no-install \ -d typo3/sysext/redirects \ "doctrine/dbal":"^3.8.1" ; \ composer req --no-update --no-install \ -d typo3/sysext/core \ "doctrine/dbal":"^3.8.1" ; \ composer req --no-update --no-install \ -d typo3/sysext/install \ "doctrine/dbal":"^3.8.1" ; \ composer req -W \ "doctrine/dbal":"^3.8.1" [1] https://github.com/doctrine/dbal/releases/tag/3.8.1 [2] https://github.com/doctrine/dbal/compare/3.7.2...3.8.1 Resolves: #103031 Releases: 12.4 Change-Id: Ifb1b236c9c57a46a7cde7b753e813d6ae8cfbd01 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/82778 Reviewed-by:
-
