{"payload":{"feedbackUrl":"https://github.com/orgs/community/discussions/53140","repo":{"id":54374659,"defaultBranch":"main","name":"core","ownerLogin":"TYPO3-CMS","currentUserCanPush":false,"isFork":false,"isEmpty":false,"createdAt":"2016-03-21T09:12:51.000Z","ownerAvatar":"https://avatars.githubusercontent.com/u/3920091?v=4","public":true,"private":false,"isOrgOwned":true},"refInfo":{"name":"","listCacheKey":"v0:1713856465.0","currentOid":""},"activityList":{"items":[{"before":"00e57496843fe96baa7c436b54cd5d0004775741","after":"2fb237377beda653d73a23fe49d2cdac85ef4e5e","ref":"refs/heads/main","pushedAt":"2024-05-10T07:21:43.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"TYPO3IncTeam","name":"TYPO3 GmbH","path":"/TYPO3IncTeam","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/20440329?s=80&v=4"},"commit":{"message":"[BUGFIX] Allow Resources/Public within asset paths\n\n\"Resources/Public\" may occur also within an\nasset path. Path detection code must therefore\nonly check for its first occurrence.\n\nResolves: #101701\nReleases: main, 12.4\nChange-Id: I8e0b62f5164593e472113ea8d294593e93abfe6c\nReviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/84181\nTested-by: Benjamin Franzke \nReviewed-by: Kevin Appelt \nReviewed-by: Benjamin Franzke \nReviewed-by: Garvin Hicking \nTested-by: Garvin Hicking \nTested-by: Josef Glatz \nReviewed-by: Josef Glatz \nTested-by: Willi Wehmeier \nReviewed-by: Willi Wehmeier \nTested-by: core-ci ","shortMessageHtmlLink":"[BUGFIX] Allow Resources/Public within asset paths"}},{"before":"8c4d6296e2c83d5808dc0da8201abb8033df4336","after":"6ed0d1ed6679525778379cea975fade95b154706","ref":"refs/heads/12.4","pushedAt":"2024-05-10T07:19:50.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"TYPO3IncTeam","name":"TYPO3 GmbH","path":"/TYPO3IncTeam","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/20440329?s=80&v=4"},"commit":{"message":"[BUGFIX] Allow Resources/Public within asset paths\n\n\"Resources/Public\" may occur also within an\nasset path. Path detection code must therefore\nonly check for its first occurrence.\n\nResolves: #101701\nReleases: main, 12.4\nChange-Id: I8e0b62f5164593e472113ea8d294593e93abfe6c\nReviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/84194\nTested-by: Benjamin Franzke \nReviewed-by: Benjamin Franzke \nTested-by: core-ci ","shortMessageHtmlLink":"[BUGFIX] Allow Resources/Public within asset paths"}},{"before":"a399919d845bb9af80c000566176d155f531af31","after":"d0f688d91d63dfdbe6b761e06fa1294281c77fea","ref":"refs/heads/11.5","pushedAt":"2024-05-06T15:42:20.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"TYPO3IncTeam","name":"TYPO3 GmbH","path":"/TYPO3IncTeam","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/20440329?s=80&v=4"},"commit":{"message":"[TASK] Add unicode license file next to .tbl files\n\nThe folder containing the charset conversion table files\nshould have the unicode license.txt file.\n\nThe license file is from https://unicode.org/license.txt\n\nResolves: #103796\nReleases: main, 12.4, 11.5\nChange-Id: I2577fea6e1b5326cd45da622ec6fbbc563bc140a\nReviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/84120\nReviewed-by: Benni Mack \nTested-by: core-ci \nTested-by: Benni Mack ","shortMessageHtmlLink":"[TASK] Add unicode license file next to .tbl files"}},{"before":"a2d2a294358dd3ef1b71ee0d0682773146cb4913","after":"8c4d6296e2c83d5808dc0da8201abb8033df4336","ref":"refs/heads/12.4","pushedAt":"2024-05-06T15:28:57.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"TYPO3IncTeam","name":"TYPO3 GmbH","path":"/TYPO3IncTeam","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/20440329?s=80&v=4"},"commit":{"message":"[TASK] Add unicode license file next to .tbl files\n\nThe folder containing the charset conversion table files\nshould have the unicode license.txt file.\n\nThe license file is from https://unicode.org/license.txt\n\nResolves: #103796\nReleases: main, 12.4, 11.5\nChange-Id: I2577fea6e1b5326cd45da622ec6fbbc563bc140a\nReviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/84119\nTested-by: Benni Mack \nReviewed-by: Benni Mack \nTested-by: core-ci ","shortMessageHtmlLink":"[TASK] Add unicode license file next to .tbl files"}},{"before":"ac4b4b35d971358e8f6cd46b01f4803ad24b4c29","after":"00e57496843fe96baa7c436b54cd5d0004775741","ref":"refs/heads/main","pushedAt":"2024-05-06T15:19:41.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"TYPO3IncTeam","name":"TYPO3 GmbH","path":"/TYPO3IncTeam","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/20440329?s=80&v=4"},"commit":{"message":"[TASK] Add unicode license file next to .tbl files\n\nThe folder containing the charset conversion table files\nshould have the unicode license.txt file.\n\nResolves: #103796\nReleases: main, 12.4, 11.5\nChange-Id: I2577fea6e1b5326cd45da622ec6fbbc563bc140a\nReviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/84150\nTested-by: Andreas Kienast \nTested-by: core-ci \nReviewed-by: Benni Mack \nReviewed-by: Andreas Kienast \nTested-by: Benni Mack ","shortMessageHtmlLink":"[TASK] Add unicode license file next to .tbl files"}},{"before":"c456775d03752fc75de1c30ccff4b5afd86661dc","after":"a2d2a294358dd3ef1b71ee0d0682773146cb4913","ref":"refs/heads/12.4","pushedAt":"2024-05-05T09:42:12.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"TYPO3IncTeam","name":"TYPO3 GmbH","path":"/TYPO3IncTeam","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/20440329?s=80&v=4"},"commit":{"message":"[BUGFIX] Update ISO language files\n\nExecuted commands:\n\n composer require --dev sokil/php-isocodes-db-i18n:^4.0.22\n Build/Scripts/updateIsoDatabase.php\n\nResolves: #103791\nReleases: main, 12.4\nChange-Id: I624ce17a6abaa2cb5c0479744db43bdf17cd069a\nReviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/84145\nReviewed-by: Andreas Kienast \nTested-by: core-ci \nTested-by: Andreas Kienast ","shortMessageHtmlLink":"[BUGFIX] Update ISO language files"}},{"before":"38945d71c41925a117cf029d1534d1f3f5630a9f","after":"ac4b4b35d971358e8f6cd46b01f4803ad24b4c29","ref":"refs/heads/main","pushedAt":"2024-05-05T09:40:19.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"TYPO3IncTeam","name":"TYPO3 GmbH","path":"/TYPO3IncTeam","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/20440329?s=80&v=4"},"commit":{"message":"[BUGFIX] Update ISO language files\n\nExecuted commands:\n\n composer require --dev sokil/php-isocodes-db-i18n:^4.0.22\n Build/Scripts/updateIsoDatabase.php\n\nResolves: #103791\nReleases: main, 12.4\nChange-Id: I624ce17a6abaa2cb5c0479744db43bdf17cd069a\nReviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/84144\nTested-by: Oliver Klee \nTested-by: core-ci \nTested-by: Andreas Kienast \nTested-by: Simon Schaufelberger \nReviewed-by: Simon Schaufelberger \nReviewed-by: Oliver Klee \nReviewed-by: Andreas Kienast ","shortMessageHtmlLink":"[BUGFIX] Update ISO language files"}},{"before":"60c3c23b47f7476c75b1434c505088042d584f41","after":"38945d71c41925a117cf029d1534d1f3f5630a9f","ref":"refs/heads/main","pushedAt":"2024-05-03T12:31:54.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"TYPO3IncTeam","name":"TYPO3 GmbH","path":"/TYPO3IncTeam","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/20440329?s=80&v=4"},"commit":{"message":"[TASK] Move table wizard Lit component to correct namespace\n\nThe module `@typo3/backend/element/table-wizard-element` is tightly\ncoupled to FormEngine's `TextTableElement`, therefore said module is\nmoved to the FormEngine namespace. Additionally, the element gets\nrenamed to `typo3-formengine-table-wizard`.\n\nResolves: #103725\nReleases: main, 12.4\nChange-Id: I1c020a4ec6045007ab4c1f42289fe0a9c842f794\nReviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/84022\nTested-by: core-ci \nReviewed-by: Benjamin Franzke \nTested-by: Andreas Kienast \nReviewed-by: Frank Nägler \nTested-by: Benjamin Franzke \nTested-by: Frank Nägler \nReviewed-by: Andreas Kienast ","shortMessageHtmlLink":"[TASK] Move table wizard Lit component to correct namespace"}},{"before":"402f7d6bf343f3059b5b13536a85c7e784e768c6","after":"c456775d03752fc75de1c30ccff4b5afd86661dc","ref":"refs/heads/12.4","pushedAt":"2024-05-03T12:29:42.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"TYPO3IncTeam","name":"TYPO3 GmbH","path":"/TYPO3IncTeam","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/20440329?s=80&v=4"},"commit":{"message":"[TASK] Move table wizard Lit component to correct namespace\n\nThe module `@typo3/backend/element/table-wizard-element` is tightly\ncoupled to FormEngine's `TextTableElement`, therefore said module is\nmoved to the FormEngine namespace. Additionally, the element gets\nrenamed to `typo3-formengine-table-wizard`.\n\nResolves: #103725\nReleases: main, 12.4\nChange-Id: I1c020a4ec6045007ab4c1f42289fe0a9c842f794\nReviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/84117\nReviewed-by: Andreas Kienast \nTested-by: core-ci \nTested-by: Andreas Kienast ","shortMessageHtmlLink":"[TASK] Move table wizard Lit component to correct namespace"}},{"before":"312b858e11ce4aeaef27c7c1f41b87672b53b7f1","after":"60c3c23b47f7476c75b1434c505088042d584f41","ref":"refs/heads/main","pushedAt":"2024-05-03T09:33:22.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"TYPO3IncTeam","name":"TYPO3 GmbH","path":"/TYPO3IncTeam","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/20440329?s=80&v=4"},"commit":{"message":"[TASK] Deprecate `MathUtility::convertToPositiveInteger()`\n\nTYPO3 has a method to ensure an integer is always positive:\n`MathUtility::convertToPositiveInteger()`. However, the method is\nrather \"heavy\" as it internally calls `MU::forceIntegerInRange()` and\ntherefore misuses a clamp mechanism to convert the integer to a\npositive number.\n\nAlso, the method name doesn't reflect what it actually does. Negative\nnumbers are not converted to their positive counterpart, but are\nswapped with `0`. Due to the naming issue and the fact that the method\ncan be superseded by a simple `max()` call, the method is therefore\ndeprecated.\n\nResolves: #103785\nReleases: main\nChange-Id: I4fd0548ec6bc7289008057ade4e64f9437c2da7b\nReviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/84141\nTested-by: Oliver Klee \nReviewed-by: Torben Hansen \nTested-by: Torben Hansen \nTested-by: core-ci \nReviewed-by: Oliver Klee \nReviewed-by: Benjamin Franzke \nTested-by: Andreas Kienast \nReviewed-by: Andreas Kienast ","shortMessageHtmlLink":"[TASK] Deprecate MathUtility::convertToPositiveInteger()"}},{"before":"be2605119f82d985bf5c3a4cae335cc945f21f0f","after":"a399919d845bb9af80c000566176d155f531af31","ref":"refs/heads/11.5","pushedAt":"2024-05-03T06:55:37.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"TYPO3IncTeam","name":"TYPO3 GmbH","path":"/TYPO3IncTeam","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/20440329?s=80&v=4"},"commit":{"message":"[TASK] Update package enshrined/svg-sanitize to 0.18.0\n\nCommands:\ncomposer req 'enshrined/svg-sanitize:^0.18.0'\ncomposer req 'enshrined/svg-sanitize:^0.18.0' \\\n -d typo3/sysext/core --no-update\n\nResolves: #103722\nReleases: main, 12.4, 11.5\nChange-Id: I9a20a46b27b3abbfd18f7ca6027e4def9ce5b59b\nReviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/84138\nTested-by: Benjamin Franzke \nReviewed-by: Benjamin Franzke \nTested-by: core-ci ","shortMessageHtmlLink":"[TASK] Update package enshrined/svg-sanitize to 0.18.0"}},{"before":"ba0f426e002f066dbe13e22c50d364a7667a4b8f","after":"402f7d6bf343f3059b5b13536a85c7e784e768c6","ref":"refs/heads/12.4","pushedAt":"2024-05-03T06:53:45.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"TYPO3IncTeam","name":"TYPO3 GmbH","path":"/TYPO3IncTeam","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/20440329?s=80&v=4"},"commit":{"message":"[TASK] Update package enshrined/svg-sanitize to 0.18.0\n\nCommands:\ncomposer req 'enshrined/svg-sanitize:^0.18.0'\ncomposer req 'enshrined/svg-sanitize:^0.18.0' \\\n -d typo3/sysext/core --no-update\n\nResolves: #103722\nReleases: main, 12.4, 11.5\nChange-Id: I9a20a46b27b3abbfd18f7ca6027e4def9ce5b59b\nReviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/84137\nTested-by: Benjamin Franzke \nReviewed-by: Benjamin Franzke \nTested-by: core-ci ","shortMessageHtmlLink":"[TASK] Update package enshrined/svg-sanitize to 0.18.0"}},{"before":"a8c622a2c5040a04c6d8d8d2107b35e2c0d3bf28","after":"312b858e11ce4aeaef27c7c1f41b87672b53b7f1","ref":"refs/heads/main","pushedAt":"2024-05-03T06:51:51.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"TYPO3IncTeam","name":"TYPO3 GmbH","path":"/TYPO3IncTeam","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/20440329?s=80&v=4"},"commit":{"message":"[TASK] Update package enshrined/svg-sanitize to 0.18.0\n\nCommands:\ncomposer req 'enshrined/svg-sanitize:^0.18.0'\ncomposer req 'enshrined/svg-sanitize:^0.18.0' \\\n -d typo3/sysext/core --no-update\n\nResolves: #103722\nReleases: main, 12.4, 11.5\nChange-Id: I9a20a46b27b3abbfd18f7ca6027e4def9ce5b59b\nReviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/84110\nReviewed-by: Oliver Klee \nReviewed-by: Benjamin Franzke \nTested-by: Benni Mack \nReviewed-by: Benni Mack \nTested-by: core-ci \nTested-by: Oliver Klee \nTested-by: Benjamin Franzke ","shortMessageHtmlLink":"[TASK] Update package enshrined/svg-sanitize to 0.18.0"}},{"before":"5e3509f1bf24d31ee4ee4315e278615f5b7dc23d","after":"a8c622a2c5040a04c6d8d8d2107b35e2c0d3bf28","ref":"refs/heads/main","pushedAt":"2024-05-03T06:30:58.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"TYPO3IncTeam","name":"TYPO3 GmbH","path":"/TYPO3IncTeam","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/20440329?s=80&v=4"},"commit":{"message":"[BUGFIX] Adopt return type of CommandUtility::exec()\n\nAllow the valid return type false which is returned by the function\nexec on failure.\n\nResolves: #103778\nReleases: main, 12.4\nChange-Id: I8f0391efb6f890ebc0095ddb8a1f93ee9c36e18c\nReviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/84135\nTested-by: core-ci \nTested-by: Andreas Kienast \nReviewed-by: Andreas Kienast \nTested-by: Benjamin Franzke \nReviewed-by: Benjamin Franzke ","shortMessageHtmlLink":"[BUGFIX] Adopt return type of CommandUtility::exec()"}},{"before":"7115a13e36e37ea3c9e70c95ed52425eb042c868","after":"ba0f426e002f066dbe13e22c50d364a7667a4b8f","ref":"refs/heads/12.4","pushedAt":"2024-05-03T06:27:12.000Z","pushType":"push","commitsCount":2,"pusher":{"login":"TYPO3IncTeam","name":"TYPO3 GmbH","path":"/TYPO3IncTeam","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/20440329?s=80&v=4"},"commit":{"message":"[BUGFIX] Adopt return type of CommandUtility::exec()\n\nAllow the valid return type false which is returned by the function\nexec on failure.\n\nResolves: #103778\nReleases: main, 12.4\nChange-Id: I8f0391efb6f890ebc0095ddb8a1f93ee9c36e18c\nReviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/84116\nTested-by: Benjamin Franzke \nTested-by: core-ci \nReviewed-by: Benjamin Franzke ","shortMessageHtmlLink":"[BUGFIX] Adopt return type of CommandUtility::exec()"}},{"before":"9fec3b6de1b6c37a6d5f90c44c22e1f03b4a3ea5","after":"5e3509f1bf24d31ee4ee4315e278615f5b7dc23d","ref":"refs/heads/main","pushedAt":"2024-05-03T06:25:17.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"TYPO3IncTeam","name":"TYPO3 GmbH","path":"/TYPO3IncTeam","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/20440329?s=80&v=4"},"commit":{"message":"[TASK] Update rollup to 4.17.2\n\nNewer rollup major versions feature optimizations in build output.\n\nThe rollup source files are now natively parsed as ESM modules by\nNodeJS. Earlier rollup versions implicitly transpiled ESM to CJS and\nallowed a mixture of ESM and CJS imports (both `import` statements and\n`require()` calls) in one module.\n\nWith the switch to ESM-only modules we now make use of `createRequire`\nutility method when node-require resolution is needed for CJS path\nlookups. Since our main project (Build/) is still in CJS mode by default\n(for grunt), we apply a sub-project module type overwrite for the\nBuild/rollup/ folder via Build/rollup/package.json to ensure rollup\nconfiguration runs in native ESM mode.\n\nSee https://nodejs.org/docs/latest-v18.x/api/packages.html\n> Node.js will treat the following as ES modules when passed to node as\n> the initial input, or when referenced by import statements or import()\n> expressions:\n> […]\n> * Files with a .js extension when the nearest parent package.json file\n> contains a top-level \"type\" field with a value of \"module\".\n\nExecuted commands:\n\n npm install --save-dev \\\n rollup@^4.17.2 \\\n @rollup/plugin-commonjs@^25.0.7 \\\n @rollup/plugin-node-resolve@^15.2.3 \\\n @rollup/plugin-replace@^5.0.5\n npm run build -- exec:rollup\n\nResolves: #103775\nReleases: main, 12.4\nChange-Id: I6793bd9233b2907ce5ed06d68c7008b349237360\nReviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/84102\nTested-by: core-ci \nReviewed-by: Andreas Kienast \nTested-by: Andreas Kienast \nTested-by: Benjamin Franzke \nReviewed-by: Benjamin Franzke ","shortMessageHtmlLink":"[TASK] Update rollup to 4.17.2"}},{"before":"486e5f617310fcd41edd84da1035eab1bf6cc3d4","after":"9fec3b6de1b6c37a6d5f90c44c22e1f03b4a3ea5","ref":"refs/heads/main","pushedAt":"2024-05-02T13:19:02.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"TYPO3IncTeam","name":"TYPO3 GmbH","path":"/TYPO3IncTeam","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/20440329?s=80&v=4"},"commit":{"message":"[BUGFIX] Cast to proper string type when performing str_contains\n\nWhen using integer types when calling the fallowing method like\n`ImageProcessingInstructions::fromCropScaleValues(.., .., '500m', 0)`,\na PHP type error for `str_contains` is issued.\n\nResolves: #103781\nReleases: main\nChange-Id: Ib36f8584f2a90d999a02dc2ea70249371b312461\nReviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/84108\nReviewed-by: Benjamin Franzke \nReviewed-by: Andreas Kienast \nTested-by: core-ci \nTested-by: Benjamin Franzke \nTested-by: Andreas Kienast ","shortMessageHtmlLink":"[BUGFIX] Cast to proper string type when performing str_contains"}},{"before":"f216cf942f8ee7ee5e5653223f47b90e1d44c444","after":"7115a13e36e37ea3c9e70c95ed52425eb042c868","ref":"refs/heads/12.4","pushedAt":"2024-05-02T10:36:43.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"TYPO3IncTeam","name":"TYPO3 GmbH","path":"/TYPO3IncTeam","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/20440329?s=80&v=4"},"commit":{"message":"[TASK] Add title and aria-label to clear input button\n\nThe clear-input button now has a proper title and additionally an\naria-label to guide visually impaired users.\n\nThe button isn't read out by screenreaders when navigating the site\nlinearly (due to tabindex=\"-1\") but when hold-pressing the button with\nthe mouse pointer, a screenreader will search for a human readable\nlabel. We therefore add an aria-label attribute. The title attribute is\nadded for sighted users but will be ignored by screenreaders since it's\nvalue equals the value of the aria-label attribute.\n\nResolves: #103417\nReleases: main, 12.4\nChange-Id: I4cbbe5200476a7d84ef1d675911ddd51f5899e87\nReviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/84106\nTested-by: Benjamin Franzke \nTested-by: core-ci \nReviewed-by: Benjamin Franzke ","shortMessageHtmlLink":"[TASK] Add title and aria-label to clear input button"}},{"before":"1a75273e33f2b700472e6181da983f7eee65f1d1","after":"486e5f617310fcd41edd84da1035eab1bf6cc3d4","ref":"refs/heads/main","pushedAt":"2024-05-02T10:34:49.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"TYPO3IncTeam","name":"TYPO3 GmbH","path":"/TYPO3IncTeam","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/20440329?s=80&v=4"},"commit":{"message":"[TASK] Add title and aria-label to clear input button\n\nThe clear-input button now has a proper title and additionally an\naria-label to guide visually impaired users.\n\nThe button isn't read out by screenreaders when navigating the site\nlinearly (due to tabindex=\"-1\") but when hold-pressing the button with\nthe mouse pointer, a screenreader will search for a human readable\nlabel. We therefore add an aria-label attribute. The title attribute is\nadded for sighted users but will be ignored by screenreaders since it's\nvalue equals the value of the aria-label attribute.\n\nResolves: #103417\nReleases: main, 12.4\nChange-Id: I4cbbe5200476a7d84ef1d675911ddd51f5899e87\nReviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/83501\nTested-by: Michael Telgkamp \nTested-by: core-ci \nReviewed-by: Michael Telgkamp \nReviewed-by: Benjamin Franzke \nTested-by: Frank Nägler \nReviewed-by: Frank Nägler \nTested-by: Benjamin Franzke ","shortMessageHtmlLink":"[TASK] Add title and aria-label to clear input button"}},{"before":"8018e6a85d1b410b9737a13b5caccabd65f95876","after":"1a75273e33f2b700472e6181da983f7eee65f1d1","ref":"refs/heads/main","pushedAt":"2024-05-02T05:59:00.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"TYPO3IncTeam","name":"TYPO3 GmbH","path":"/TYPO3IncTeam","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/20440329?s=80&v=4"},"commit":{"message":"[DOCS] Add hint about console command for listing site sets in changelog\n\nWith the introduction of site sets also a console command\nwas made available which lists all available site sets.\nKnowing this command makes it easier for integrators to set\nthe dependencies.\n\nResolves: #103771\nRelated: #103437\nReleases: main\nChange-Id: I86e45c1a63fc3ddc5aaf8a2b1b72da7b24febe08\nReviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/84098\nTested-by: Oliver Klee \nTested-by: Georg Ringer \nReviewed-by: Garvin Hicking \nReviewed-by: Oliver Klee \nTested-by: Benjamin Franzke \nTested-by: Garvin Hicking \nReviewed-by: Benjamin Franzke \nReviewed-by: Georg Ringer \nTested-by: core-ci ","shortMessageHtmlLink":"[DOCS] Add hint about console command for listing site sets in changelog"}},{"before":"a2d79df636c748c3c38247e6598591bcfc0d7498","after":"f216cf942f8ee7ee5e5653223f47b90e1d44c444","ref":"refs/heads/12.4","pushedAt":"2024-05-01T06:45:48.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"TYPO3IncTeam","name":"TYPO3 GmbH","path":"/TYPO3IncTeam","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/20440329?s=80&v=4"},"commit":{"message":"[TASK] Add possibility to create HashValue from actual payload\n\nThe new factory method `HashValue::hash('test')` creates the\nhash from the raw payload `'test'`. This is a simpler shortcut\nfor using `HashValue::create(hash('sha256', 'test', true))`.\n\nResolves: #103772\nReleases: main, 12.4\nChange-Id: Id201e166eeabc856b8d8dc498cc73cde8d5eb801\nReviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/84114\nTested-by: Georg Ringer \nTested-by: core-ci \nReviewed-by: Georg Ringer ","shortMessageHtmlLink":"[TASK] Add possibility to create HashValue from actual payload"}},{"before":"71a58d799b6f50b82284c4750dac377abb13814f","after":"8018e6a85d1b410b9737a13b5caccabd65f95876","ref":"refs/heads/main","pushedAt":"2024-05-01T05:39:35.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"TYPO3IncTeam","name":"TYPO3 GmbH","path":"/TYPO3IncTeam","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/20440329?s=80&v=4"},"commit":{"message":"[TASK] Add possibility to create HashValue from actual payload\n\nThe new factory method `HashValue::hash('test')` creates the\nhash from the raw payload `'test'`. This is a simpler shortcut\nfor using `HashValue::create(hash('sha256', 'test', true))`.\n\nResolves: #103772\nReleases: main, 12.4\nChange-Id: Id201e166eeabc856b8d8dc498cc73cde8d5eb801\nReviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/84100\nTested-by: core-ci \nReviewed-by: Benni Mack \nTested-by: Georg Ringer \nReviewed-by: Georg Ringer \nTested-by: Benni Mack \nReviewed-by: Markus Klein ","shortMessageHtmlLink":"[TASK] Add possibility to create HashValue from actual payload"}},{"before":"164de982d4a8f1acafeb5228da9867692811a053","after":"71a58d799b6f50b82284c4750dac377abb13814f","ref":"refs/heads/main","pushedAt":"2024-04-30T12:14:53.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"TYPO3IncTeam","name":"TYPO3 GmbH","path":"/TYPO3IncTeam","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/20440329?s=80&v=4"},"commit":{"message":"[FEATURE] Introduce ModifyRedirectUrlValidationResultEvent PSR-14 event\n\nThe frontend login extension currently validates a given redirect URL\nby ensuring, that the URL is either relative or the host is known to\nTYPO3. In some scenarios, it might however be useful to allow a\nredirect URL, which does not match the existing rules.\n\nThis change adds the `ModifyRedirectUrlValidationResultEvent` PSR-14\nevent, allowing developers to implement custom validation logic for\nthe redirect URL.\n\nResolves: #103019\nReleases: main\nChange-Id: I81b387f23e90adbaf4a586c9108766275f5e1273\nReviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/82763\nTested-by: core-ci \nReviewed-by: Simon Schaufelberger \nTested-by: Simon Schaufelberger \nReviewed-by: Guido Schmechel \nTested-by: Georg Ringer \nReviewed-by: Georg Ringer \nReviewed-by: Jörg Bösche \nReviewed-by: Nikita Hovratov ","shortMessageHtmlLink":"[FEATURE] Introduce ModifyRedirectUrlValidationResultEvent PSR-14 event"}},{"before":"157c0f7ca837a266094cca62a82407abcd3040d4","after":"a2d79df636c748c3c38247e6598591bcfc0d7498","ref":"refs/heads/12.4","pushedAt":"2024-04-30T08:54:53.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"TYPO3IncTeam","name":"TYPO3 GmbH","path":"/TYPO3IncTeam","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/20440329?s=80&v=4"},"commit":{"message":"[BUGFIX] Remove h4 from alerts to avoid breaking document hierarchy\n\nThis patch adjusts the flash message and notifications elements by\nremoving the h4 tag to prevent incorrect header flow throughout the\ncontent structure, allowing for better flexibility based on different\nuse cases.\n\nResolves: #103762\nReleases: main, 12.4\nChange-Id: Ide330150145d5c4965410fbf61973ef682bb96b0\nReviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/84093\nTested-by: core-ci \nReviewed-by: Benjamin Franzke \nTested-by: Benjamin Franzke ","shortMessageHtmlLink":"[BUGFIX] Remove h4 from alerts to avoid breaking document hierarchy"}},{"before":"36f6928dab29ff2e9a5a80e0b65a79afb87bf238","after":"164de982d4a8f1acafeb5228da9867692811a053","ref":"refs/heads/main","pushedAt":"2024-04-30T08:52:59.000Z","pushType":"push","commitsCount":2,"pusher":{"login":"TYPO3IncTeam","name":"TYPO3 GmbH","path":"/TYPO3IncTeam","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/20440329?s=80&v=4"},"commit":{"message":"[BUGFIX] Remove h4 from alerts to avoid breaking document hierarchy\n\nThis patch adjusts the flash message and notifications elements by\nremoving the h4 tag to prevent incorrect header flow throughout the\ncontent structure, allowing for better flexibility based on different\nuse cases.\n\nResolves: #103762\nReleases: main, 12.4\nChange-Id: Ide330150145d5c4965410fbf61973ef682bb96b0\nReviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/84082\nReviewed-by: Benjamin Franzke \nTested-by: Benjamin Kott \nTested-by: Georg Ringer \nReviewed-by: Benjamin Kott \nReviewed-by: Georg Ringer \nTested-by: Benjamin Franzke \nTested-by: core-ci ","shortMessageHtmlLink":"[BUGFIX] Remove h4 from alerts to avoid breaking document hierarchy"}},{"before":"6a3a60975669fb707f993bcbcb807777572d8f9f","after":"157c0f7ca837a266094cca62a82407abcd3040d4","ref":"refs/heads/12.4","pushedAt":"2024-04-30T08:51:02.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"TYPO3IncTeam","name":"TYPO3 GmbH","path":"/TYPO3IncTeam","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/20440329?s=80&v=4"},"commit":{"message":"[BUGFIX] Remove h4 from infobox to avoid breaking document hierarchy\n\nThis patch adjusts the infobox/callout element by removing the\nh4 tag to prevent incorrect ordering in the content structure,\nallowing for better flexibility based on different use cases.\n\nResolves: #103761\nReleases: main, 12.4\nChange-Id: I2556ea0df0e55ffcdf752c9c0574b843ffea44ff\nReviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/84094\nTested-by: core-ci \nTested-by: Benjamin Franzke \nReviewed-by: Benjamin Franzke ","shortMessageHtmlLink":"[BUGFIX] Remove h4 from infobox to avoid breaking document hierarchy"}},{"before":"d527dcd11880404fdf27db010ac4b54b926b25a5","after":"36f6928dab29ff2e9a5a80e0b65a79afb87bf238","ref":"refs/heads/main","pushedAt":"2024-04-29T07:43:48.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"TYPO3IncTeam","name":"TYPO3 GmbH","path":"/TYPO3IncTeam","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/20440329?s=80&v=4"},"commit":{"message":"[TASK] Use refindex in RootlineUtility, drop addRootLineFields\n\ntl;dr:\n\nThis patch switches from using RelationHandler to ReferenceIndex\nin (mostly) frontend request related RootlineUtility. It is the\nfirst patch actively using ReferenceIndex in frontend and has\nthe potential to significantly reduce database query load on\nnot-yet-cached pages in frontend, while creating better results\nat the same time. The patch obsoletes\n$GLOBALS['TYPO3_CONF_VARS']['FE']['addRootLineFields']. This\nis just the tip of the iceberg from a refactoring chain that has\nbeen prepared over a period of about three years already.\n\nThe long story:\n\nRendering times of complex pages in the frontend in general scale\nlinearly with the number of executed database queries (plus some\noffset), if no extension needs extensive calculation on the PHP side,\neven if the database is server-side local and not a remote instance,\nwhich adds additional TCP round-trip times per query.\nWith thousands of queries being triggered by RootlineUtility, this\narea is the most promising code path to optimize when response times\nof not-fully-cached pages should be reduced.\n\nRootlineUtility is *the* main performance bottleneck in\nnon-trivial TYPO3 instance frontend rendering: When rendering menus,\neach single entry needs to know its page row details and its path in\nthe rootline, using RootlineUtility. This can quickly lead to\nthousands of DB queries with bigger instances on cold caches,\ncatapulting the rendering times from milliseconds to seconds. This is\nworse when dealing with language overlays and workspaces.\n\nRootlineUtility does two main things:\nIt first resolves the rootline of the given pages-uid. This is\nan expensive operation since it needs a query per page level.\nWe'll change this towards a recursive query soon. Afterwards, it\nresolves some relations attached to the pages. This is - in default\ninstances - at least the 'media' field. This is done using\nclass RelationHandler per single field in question, which fires\nat least one query per page row and per field.\n\nAs such, beside the expensive rootline determination itself, we also\nhave an expensive operation to resolve relations of each pages row.\n\nResolving relations attached to pages in a more performant way\nis what this patch is about.\n\nThe list of relations being resolved can be extended using\n$GLOBALS['TYPO3_CONF_VARS']['FE']['addRootLineFields']. By default,\nonly field 'media' is resolved, resulting in one additional query\nper resolved page row. Instances tend to add more relations to\npages, and when adding these to 'addRootLineFields', they trigger\nadditional RelationHandler queries by RootlineUtility. Also,\nRootlineUtility *ignores* 'addRootLineFields' when resolving\nrelations when requesting non-default (sys_language_uid != 0) pages,\nand simply resolves *all* possible relation fields. This includes\n'category' and probably some of the TCA fields ext:seo adds to pages\nTCA. RelationHandler needs *at least* one query per field, more with\nlocalizations and even more when rendering a workspaces preview.\n\nThis situation makes relation resolving of page rows in\nRootlineUtility more expensive than resolving the rootline itself.\nOne option would be to skip resolving page relations in\nRootlineUtility, but that wouldn't help us much when instances\nactually need this data (which is likely).\nA better solution is to supply relations within pages in a more\nperformant way, ready for TypoScript and extensions to use.\n\nThe patch switches from using RelationHandler within\nRootlineUtility to query the ReferenceIndex instead: sys_refindex\ncontains all fields relevant for frontend since #103748. It allows\nquerying *all* relations of *all* page fields with just *one* query.\n\nThis allows us to remove 'addRootLineFields' by just always\nresolving all relations with close to no overhead, and turns into\nan advantage for integrators: One detail less to take care of.\n\nThe patch establishes a nifty - but very well indexed - query within\nRootlineUtility to fetch relations. With 'categories' (an MM foreign\nrelation) being attached to pages by default, it is a UNION query of\ntwo SELECT queries, with their result being sorted out in a rather\neffective result handling loop.\n\nThe patch comes with a todo list within RootlineUtility, but in\ngeneral, the result list is *better* than the result of the previous\nsingle field based RelationHandler solution. This is verified by the\npreviously establish test data sets:\n* hidden, starttime, endtime are resolved.\n* Workspace deleted placeholder rows are removed automatically.\n\nThere are a couple of details we may want to improve with further\nv13 patches, but in general, this new approach should work well\nalready.\n\nFuture:\n\n* This patch is a base to unlock a series of further performance\n related changes: When CTE's on RootlineUtility are established, it\n will allow fetching relations of not only one page, but of multiple\n pages with one query. Combined with a couple of other changes, the\n query load in frontend will ultimately collapse.\n\n* The patch is the base for ReferenceIndex usage in the frontend:\n We can potentially remove the doomed DatabaseQueryProcessor and\n other shenanigans for tt_content within the frontend rendering\n chain by always providing \"correct\" relation information\n automatically without overhead. Other pending patches are already\n preparing a central place taking care of tt_content for its\n relations to be resolved in a similar effective way.\n\n* Resolving relations of all fields attached to page rows voids the\n 'parent count' values of these fields. Those are a different\n de-normalization of relations \"if it's not 0, we have some\". With\n RootlineUtility dropping 'addRootLineFields' and always resolving\n relations, we can finally start dropping these 'count' fields, can\n release DataHandler from updating these fields, and can remove\n them from DB altogether.\n\nNumbers:\n\nThere was a recent blog post by Julian [1] looking at query load of\nbigger menus. With measurements for this patch, we confirm the\ngeneral numbers Julian came up with in his test setup. Thank to the\npublished test setup at [2], we ported it to TYPO3 v13, and slightly\nextended it to measure query load when all pages are localized, and\nwe're performing a request to a non-default language.\n\n* The main query count on a \"cold\" instance calling default language\n does *not* change with this patch. The reason is, default TYPO3\n includes only 'media' as relation that has a 'foreign_field' in\n RootlineUtility, which leads to only one query, which is now\n substituted by the new refindex query. The advantage of the new\n solution provided by the patch is to resolve *all* relation with\n the same query load.\n\n* When calling a localized page, the query load is at ~10200 queries\n on a non-cached-page frontend request. This shrinks to ~7900 with\n the patch being applied. That's a reduction of 1/5 by this patch,\n with further options up our sleeves.\n\n[1] https://www.in2code.de/aktuelles/menue-vergleich-der-techniken/\n[2] https://github.com/julianhofmann/typo3-menu-comparison\n\nResolves: #103752\nRelated: #103748\nRelated: #103735\nRelated: #103710\nRelated: #103680\nRelated: #103599\nRelated: #103598\nChange-Id: Ic7e152366dc2d4312ca55035c364db9ac02fabee\nReviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/83729\nTested-by: Anja Leichsenring \nTested-by: André Buchmann \nReviewed-by: Anja Leichsenring \nTested-by: Benni Mack \nTested-by: Stefan Bürk \nReviewed-by: André Buchmann \nReviewed-by: Benni Mack \nReviewed-by: Stefan Bürk \nReviewed-by: Christian Kuhn \nTested-by: core-ci \nTested-by: Christian Kuhn ","shortMessageHtmlLink":"[TASK] Use refindex in RootlineUtility, drop addRootLineFields"}},{"before":"bc4388b3a57583ef9533c1137c02ed511391834a","after":"d527dcd11880404fdf27db010ac4b54b926b25a5","ref":"refs/heads/main","pushedAt":"2024-04-28T18:09:32.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"TYPO3IncTeam","name":"TYPO3 GmbH","path":"/TYPO3IncTeam","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/20440329?s=80&v=4"},"commit":{"message":"[DOCS] Fix typo in changelog to TypoScript provider for sites and sets\n\nResolves: #103755\nRelated: #103675\nReleases: main\nChange-Id: Ic94dc6bbff56f09233fec1b7cda42091d07dad2f\nReviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/84077\nTested-by: Stefan Bürk \nReviewed-by: Stefan Bürk \nTested-by: core-ci ","shortMessageHtmlLink":"[DOCS] Fix typo in changelog to TypoScript provider for sites and sets"}},{"before":"4447f691893802f92a63aba3ba6edf5b3cd97aa9","after":"bc4388b3a57583ef9533c1137c02ed511391834a","ref":"refs/heads/main","pushedAt":"2024-04-28T10:25:39.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"TYPO3IncTeam","name":"TYPO3 GmbH","path":"/TYPO3IncTeam","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/20440329?s=80&v=4"},"commit":{"message":"[TASK] Enrich ReferenceIndex with more relation data\n\nReferenceIndex (table sys_refindex) has two main jobs:\n* It registers \"soft\" relations, for instance when a\n bodytext sets a link in its text string. Similar things\n are done for relations in anonymous flex form strings.\n* It is a registry of DB relations attached to TCA based\n table records.\n\nThis patch is about the DB relation part of refindex.\n\nWhen a TCA record needs to know all its database relations\nattached to it, it can either ask the (clumsy)\nRelationHandler for relations of each field, which then\nqueries the foreign table for relations, OR it could ask\nthe refindex for all relations with a single query. It\nis possible to do this for multiple records in one query.\n\nRefindex has significant test coverage within DataHandler:\nWith over a thousand functional tests validating the\nrefindex, we can be confident in the accuracy of the\nfunctionality. This coverage has been in place and\ncontinuously improved since TYPO3 v11.\n\nThis de-normalized nature of having a single table that\ntracks all TCA DB relations of all TCA tables is a powerful\nstructure that allows us to query relations in a performant\nway. This is currently only leveraged in a couple of places\nin the backend, though.\n\nIntegrating refindex within the frontend is promising to\nalleviate the query load on not-yet-cached pages, though:\nThere are various places that tend to hammer the database\nwith hundreds or thousand of queries to look up relations,\nRootlineUtility in particular is very demanding.\n\nRefindex however does not carry relation details important\nin the frontend: It does not know about hidden, starttime\nand endtime restrictions applied to single relations.\n\nThe patch changes this by adding a series of columns to\nsys_refindex, and adapts class ReferenceIndex to take care\nof them.\n\nAdding fields to sys_refindex has one drawback:\nPrimary key 'hash' is a hash of all columns. Adding\ncolumns invalidates all existing hashes, refindex needs\nto be rebuild. This is why the patch is so huge: All tests\nchecking refindex integrity need new rows. It also means\ninstances need to update refindex. The patch dedicates\nan Important.rst to this.\n\nWith forcing a full re-index for everyone, the patch takes\nthe opportunity to use xxh128 over md5 for the hash, which\nis a significantly quicker hash algorithm with good\ncollision protection, and with the same length of 128\nbit (128 bit = 16 bytes = 16 hex numbers = 32 chars).\n\nThe patch also adds more fine grained table column and\nindex definitions: Two changed indexes are designed to help\nqueries having the typical query signature, and queries can\nbe crafted to use large parts of the combined indexes.\n\nAnother detail is that 'endtime' defaults to a high value:\nWhen a casual endtime-aware TCA record has no endtime set,\nit's column value is 0. This requires an OR in the query.\nrefindex de-normalizes this to a high value instead, to\nalways query rows with a \"greater than now\" where clause.\n\nThe patch reveals a bug within MM when resorting rows. A\nsingle functional test is disabled for now. The situation\nwill be fixed with another patch.\n\nsys_refindex contains columns for the \"left\" / \"local\" side,\nand columns for the \"right\" / \"foreign\" side. Foreign side\ncolumns are prefixed with \"ref_\". A quick rundown of\nsys_refindex table columns:\n\nhash:\nprimaray key, xxh128 hash of the other column values\n\ntablename & ref_table:\nnames of the involved tables. tablename is \"_STRING\" when\ndealing with a softref row.\n\nrecuid & ref_uid:\nuids of the involved table rows.\n\nfield & (new)ref_field:\nnames of the involved table fields.\n\nsorting & ref_sorting:\nkeep relations in a deterministic order.\n\n(new)hidden & (new)ref_hidden:\nint '1' if the table is TCA hidden aware and the row is hidden.\n\n(new)starttime & (new)ref_starttime:\nstarttime timestamp of the row if the table is TCA starttime\naware and a value is set, else '0'.\n\n(new)endtime & (new)ref_endtime:\nendtime timestamp of the row if the table is TCA endtime aware\nand a value is set, else 2^31-1 (year 2038) since postgres 32-bit\nint is always signed. Could be extended later.\n\nworkspace:\ncalculated workspace-uid this refindex row is relevant in. With\nMM relations, there can be rows with workspace-uid 0 on one side\nand workspace-uid 1 on the other side, with the sys_refindex\nrow being valid for workspace-uid 1.\n\n(new)t3ver_state & (new)ref_t3ver_state:\nworkspace versionState value of the table row, default int 0.\nUsed to filter especially deleted placeholder rows (int 2).\n\nflexpointer, softref_key, softref_id, ref_string:\nsoftref and flex form path details fields.\n\nResolves: #103748\nRelated: #103735\nRelated: #103680\nRelated: #103655\nReleases: main\nChange-Id: I276eef06da4bbe5bd51d90fc850e27ebe6ff2130\nReviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/84050\nTested-by: Christian Kuhn \nReviewed-by: Anja Leichsenring \nTested-by: Anja Leichsenring \nTested-by: Stefan Bürk \nReviewed-by: Stefan Bürk \nTested-by: core-ci \nReviewed-by: Christian Kuhn ","shortMessageHtmlLink":"[TASK] Enrich ReferenceIndex with more relation data"}},{"before":"371f62ccd54549f041f33bcf39542eb2c2632d0e","after":"4447f691893802f92a63aba3ba6edf5b3cd97aa9","ref":"refs/heads/main","pushedAt":"2024-04-27T15:38:59.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"TYPO3IncTeam","name":"TYPO3 GmbH","path":"/TYPO3IncTeam","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/20440329?s=80&v=4"},"commit":{"message":"[TASK] Avoid sorting issue in RootlineUtilityTest\n\nA missing additional orderBy() in RelationHandler\nleads to the situation that different DB vendor\nmay return relations in different order, *if*\nthe MM table \"local sorting\" value isn't unique.\n\nPatch for issue #103735 added an according `@todo`\nfor this scenario in RelationHandler already.\n\nThe import CSV test set of RootlineUtilityTest\nfrom issue #103680 is a victim here since the\ncategory MM rows have no proper unique sorting\non the local side.\n\nThe patch fixes the import CSV to have proper\nsorting values.\n\nResolves: #103747\nRelated: #103735\nRelated: #103680\nReleases: main\nChange-Id: I5b37ae7445d5517fcde255e77ba8279800534d17\nReviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/84051\nTested-by: Christian Kuhn \nTested-by: Stefan Bürk \nTested-by: Andreas Nedbal \nTested-by: core-ci \nReviewed-by: Andreas Nedbal \nReviewed-by: Christian Kuhn \nReviewed-by: Stefan Bürk ","shortMessageHtmlLink":"[TASK] Avoid sorting issue in RootlineUtilityTest"}}],"hasNextPage":true,"hasPreviousPage":false,"activityType":"all","actor":null,"timePeriod":"all","sort":"DESC","perPage":30,"cursor":"djE6ks8AAAAERlE4EwA","startCursor":null,"endCursor":null}},"title":"Activity · TYPO3-CMS/core"}