{"payload":{"feedbackUrl":"https://github.com/orgs/community/discussions/53140","repo":{"id":54374575,"defaultBranch":"main","name":"backend","ownerLogin":"TYPO3-CMS","currentUserCanPush":false,"isFork":false,"isEmpty":false,"createdAt":"2016-03-21T09:11:33.000Z","ownerAvatar":"https://avatars.githubusercontent.com/u/3920091?v=4","public":true,"private":false,"isOrgOwned":true},"refInfo":{"name":"","listCacheKey":"v0:1719905094.0","currentOid":""},"activityList":{"items":[{"before":"5a9dd8a0da167f015bdcf97751462381a27d897c","after":"d700273ada63da1cb63c439b213e5227cdf91c4a","ref":"refs/heads/main","pushedAt":"2024-07-06T17:27:29.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] Combine be_groups table permission read & write UI\n\nThe `tables_select` and `tables_modify` lists have the same\nitems listed, so instead of managing them through separate\nviews, the merges them into a single view.\n\nThe new (merged) table renders the three options \"No Access\",\n\"Read\" and \"Read & Write\" for each table. Those options are\naccompanied by the multi record selection options to\n\"Check All\", \"Uncheck All\" and to \"Toggle Selection\".\n\nTo render this new table view and handle its behavior, a\ndedicated form renderType `tablePermission` is introduced, which\nis now set for the `tables_modify` column. The `tables_select`\ncolumn has been changed to TCA type `passthrough`.\n\nThe new form element is defined through:\n`\\TYPO3\\CMS\\Backend\\Form\\Element\\TablePermissionElement`.\nIt uses a dedicated data provider defined in:\n`\\TYPO3\\CMS\\Backend\\Form\\FormDataProvider\\TcaTablePermission`.\nThe JavaScript code is handled by a new web component:\n`@typo3/backend/form-engine/element/table-permission-element.js`.\n\nWhen the TcaTablePermission data provider handles the\nconfiguration, it reads table lists from both the `tables_select`\nand `tables_modify` columns and combines them into a single array\nwith unique table names.\n\nResolves: #103521\nReleases: main\nChange-Id: Iae468d9209d346ef09fd34053cdcd2d1a8ef1f2c\nReviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/83743\nReviewed-by: Marcin Sągol \nReviewed-by: Oliver Bartsch \nTested-by: Georg Ringer \nTested-by: Marcin Sągol \nTested-by: Christian Kuhn \nReviewed-by: Georg Ringer \nTested-by: core-ci \nTested-by: Oliver Bartsch \nReviewed-by: Christian Kuhn ","shortMessageHtmlLink":"[FEATURE] Combine be_groups table permission read & write UI"}},{"before":"5b0aaf7219432ce40bb418fbcb2a8365b12dc399","after":"b8c94ebd8fda30a60308cdaf75569b077bd9e6a7","ref":"refs/heads/12.4","pushedAt":"2024-07-04T22:21:33.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] Use correct FlexForm field names in debug info\n\nThe debug information of each element\nin FormEngine now displays the correct\nfield names for FlexForm fields in a\ncontainer. Additionally, do the container\nelements itself display the correct\n(field) name now.\n\nResolves: #104303\nReleases: main, 12.4\nChange-Id: Ic2a92bc0deea4b3165f4aa77103c56050cb3dc63\nReviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/85109\nTested-by: Oliver Bartsch \nReviewed-by: Oliver Bartsch \nTested-by: core-ci ","shortMessageHtmlLink":"[BUGFIX] Use correct FlexForm field names in debug info"}},{"before":"77b9ee0eb7ad41dffebd29860e7d5e1604339f63","after":"5a9dd8a0da167f015bdcf97751462381a27d897c","ref":"refs/heads/main","pushedAt":"2024-07-04T22:19: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":"[BUGFIX] Use correct FlexForm field names in debug info\n\nThe debug information of each element\nin FormEngine now displays the correct\nfield names for FlexForm fields in a\ncontainer. Additionally, do the container\nelements itself display the correct\n(field) name now.\n\nResolves: #104303\nReleases: main, 12.4\nChange-Id: Ic2a92bc0deea4b3165f4aa77103c56050cb3dc63\nReviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/85096\nTested-by: Garvin Hicking \nReviewed-by: Garvin Hicking \nTested-by: Georg Ringer \nTested-by: core-ci \nReviewed-by: Georg Ringer \nReviewed-by: Oliver Bartsch \nTested-by: Oliver Bartsch ","shortMessageHtmlLink":"[BUGFIX] Use correct FlexForm field names in debug info"}},{"before":"2174618d6a75c14683edc18af47e19bed41fd570","after":"77b9ee0eb7ad41dffebd29860e7d5e1604339f63","ref":"refs/heads/main","pushedAt":"2024-07-04T11:42:25.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 BackendUtility::getTcaFieldConfiguration\n\nThe method getTcaFieldConfiguration is the first\nto fall in BackendUtility as we now have a new\nAPI for accessing information from TCA.\n\nThe last pieces have been migrated.\n\nHistorical fun fact: This method was introduced\nwith TYPO3 4.x to add support for IRRE in Workspaces\nin 2010 by ohader:\n\"Add feature #16374: Implement Inline Relational Record Editing (IRRE) in Workspaces\"\n\nKudos for this tremendous effort.\n\nResolves: #104304\nRelated: #104002\nRelated: #16374\nReleases: main\nChange-Id: I5c38592777ca4ee64e5a9155e338e17322ae452c\nReviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/85100\nReviewed-by: Oliver Hader \nTested-by: Oliver Bartsch \nReviewed-by: Oliver Bartsch \nTested-by: Christian Kuhn \nTested-by: core-ci \nReviewed-by: Christian Kuhn ","shortMessageHtmlLink":"[TASK] Deprecate BackendUtility::getTcaFieldConfiguration"}},{"before":"3c84c39c7a808020278735f58530bc4cd2fd1046","after":"5b0aaf7219432ce40bb418fbcb2a8365b12dc399","ref":"refs/heads/12.4","pushedAt":"2024-07-03T16:28:01.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] Prevent multiple FlexContainers of same name\n\nIt is possible in Flexform containers to set a XML\nconfiguration that uses the same input field names,\nbut within different sheets.\n\nThe `FlexFormSectionContainer::render()` method used a\nHTML DOM id attribute that did not consider\nthe Flexform sheet name, which has lead to the same id\nattribute being re-used. The JavaScript events (add\nand delete items from a container) would then\nfire only on the first instance, but as many times\nas there were wrongly regarded \"duplicate\" containers\nusing the same id.\n\nThis fix introduces another identifier section to the\nid attribute, containing the Flexform sheet name.\nThis XML attribute is compatible\nwith allowed CSS class names, so no further escaping is\ndone with it, similar to the use of `$flexFormFieldName`.\n\nResolves: #97042\nRelated: #99947\nReleases: main, 12.4\nChange-Id: Ic1c81c658b090cb7b9c1a4230c0b4e75c12560dc\nReviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/85097\nTested-by: Oliver Bartsch \nReviewed-by: Oliver Bartsch \nTested-by: core-ci ","shortMessageHtmlLink":"[BUGFIX] Prevent multiple FlexContainers of same name"}},{"before":"b9f267d893a0273535585a936c8697baee0218ec","after":"2174618d6a75c14683edc18af47e19bed41fd570","ref":"refs/heads/main","pushedAt":"2024-07-03T16:22: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] Prevent multiple FlexContainers of same name\n\nIt is possible in Flexform containers to set a XML\nconfiguration that uses the same input field names,\nbut within different sheets.\n\nThe `FlexFormSectionContainer::render()` method used a\nHTML DOM id attribute that did not consider\nthe Flexform sheet name, which has lead to the same id\nattribute being re-used. The JavaScript events (add\nand delete items from a container) would then\nfire only on the first instance, but as many times\nas there were wrongly regarded \"duplicate\" containers\nusing the same id.\n\nThis fix introduces another identifier section to the\nid attribute, containing the Flexform sheet name.\nThis XML attribute is compatible\nwith allowed CSS class names, so no further escaping is\ndone with it, similar to the use of `$flexFormFieldName`.\n\nResolves: #97042\nRelated: #99947\nReleases: main, 12.4\nChange-Id: Ic1c81c658b090cb7b9c1a4230c0b4e75c12560dc\nReviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/85083\nReviewed-by: Oliver Bartsch \nTested-by: core-ci \nTested-by: Simon Schaufelberger \nReviewed-by: Christian Kuhn \nReviewed-by: Simon Schaufelberger \nTested-by: Oliver Bartsch ","shortMessageHtmlLink":"[BUGFIX] Prevent multiple FlexContainers of same name"}},{"before":"977e1daf276fb28fc741d80976d6c99944ff0978","after":"b9f267d893a0273535585a936c8697baee0218ec","ref":"refs/heads/main","pushedAt":"2024-07-03T13:43: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":"[TASK] Bundle Flex DS check,migrate,prepare\n\nCentral single flex datastructure field TCA\nmigration and preparation has been established\nwith #104293.\n\nThis patch refactors the code another time to\navoid a recursion, merges the two traverse\noperations into one construct, and checks\nfor not supported data structure setups like\nsection containers defining TCA types with\nDB relations.\n\nThose checks for invalid data structures were\npreviously located within FormEngine related\nTcaFlexProcess, and are now relocated to the\nmore central FlexFormTools.\n\nResolves: #104300\nRelated: #104293\nRelated: #102970\nReleases: main\nChange-Id: Iba0bef3bee09d350e258d69c987e754a56297297\nReviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/85092\nTested-by: core-ci \nTested-by: Christian Kuhn \nTested-by: Oliver Bartsch \nReviewed-by: Christian Kuhn \nReviewed-by: Oliver Bartsch \nReviewed-by: Garvin Hicking \nTested-by: Garvin Hicking ","shortMessageHtmlLink":"[TASK] Bundle Flex DS check,migrate,prepare"}},{"before":"0446c3c01b96b235c29d660ea49b4a89b60d11e2","after":"977e1daf276fb28fc741d80976d6c99944ff0978","ref":"refs/heads/main","pushedAt":"2024-07-02T09:09:31.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] Introduce Leveled Surface Colors to Backend\n\nThis patch advances elevation streamlining by\nadding leveled surface colors to the backend.\nIt serves as a preliminary update, laying the\ngroundwork for future enhancements.\n\nWhile it initiates the introduction of surface\ncolors, additional work in other areas is\nrequired for a full rollout.\n\nResolves: #104285\nReleases: main\nChange-Id: Icbafaf616cbe28102476dcc0bd0c2f3c4e89cca6\nReviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/84032\nReviewed-by: Benjamin Kott \nTested-by: Andreas Kienast \nReviewed-by: Georg Ringer \nTested-by: Benjamin Kott \nReviewed-by: Benni Mack \nTested-by: Georg Ringer \nTested-by: core-ci \nTested-by: Benni Mack \nReviewed-by: Andreas Kienast ","shortMessageHtmlLink":"[TASK] Introduce Leveled Surface Colors to Backend"}},{"before":"b54405f1f1f29b4bfab2883f4fd8ce999ace5eaa","after":"0446c3c01b96b235c29d660ea49b4a89b60d11e2","ref":"refs/heads/main","pushedAt":"2024-07-02T07:37:01.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] Set TYPO3 version to 13.3.0-dev\n\nChange-Id: Ia8a718c96803f84f558dc5bfab35b9559491a8c1\nReviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/85078\nReviewed-by: Oliver Hader \nTested-by: Oliver Hader ","shortMessageHtmlLink":"[TASK] Set TYPO3 version to 13.3.0-dev"}},{"before":"6e32f923c025def01f6c28f8ebed26af195e75f2","after":"b54405f1f1f29b4bfab2883f4fd8ce999ace5eaa","ref":"refs/heads/main","pushedAt":"2024-07-02T07:23:34.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":"[RELEASE] Release of TYPO3 13.2.1\n\nChange-Id: Ieb4da6a77ab6da4ad0149d6b3f7f91bafc9ae13c\nReviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/85077\nTested-by: Benni Mack \nReviewed-by: Benni Mack ","shortMessageHtmlLink":"[RELEASE] Release of TYPO3 13.2.1"}},{"before":"af983b81082e181dd145e2b913a8f8b1945f2ed9","after":"6e32f923c025def01f6c28f8ebed26af195e75f2","ref":"refs/heads/main","pushedAt":"2024-07-02T07:06:15.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] Set TYPO3 version to 13.2.1-dev\n\nChange-Id: Idd321771d9772715595e7bbbf648fb16ead1de61\nReviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/85076\nReviewed-by: Benni Mack \nTested-by: core-ci \nTested-by: Benni Mack ","shortMessageHtmlLink":"[TASK] Set TYPO3 version to 13.2.1-dev"}},{"before":"af1ccf107ff2a0be7fe69ff6013684ef2465edb2","after":"af983b81082e181dd145e2b913a8f8b1945f2ed9","ref":"refs/heads/main","pushedAt":"2024-07-02T06:14: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] Repair composer.json from 13.2.0 release\n\nDue to a bug in TYPO3's packaging tool,\ncomposer.json files were malformed and are now repaired.\n\nReleases: main\nChange-Id: Ib489171cc0c1dc80b4cf8d3454d3d84c3f44622f\nReviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/85074\nTested-by: core-ci \nTested-by: Benni Mack \nReviewed-by: Benni Mack ","shortMessageHtmlLink":"[BUGFIX] Repair composer.json from 13.2.0 release"}},{"before":"505b74d10e3d6e77b89c1164c7b400b4459d62b4","after":"af1ccf107ff2a0be7fe69ff6013684ef2465edb2","ref":"refs/heads/main","pushedAt":"2024-07-02T05:36:33.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":"[RELEASE] Release of TYPO3 13.2.0\n\nChange-Id: I8727969ce901dcedca5aa86f8c830ca38bccf541\nReviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/85072\nTested-by: Benni Mack \nReviewed-by: Benni Mack ","shortMessageHtmlLink":"[RELEASE] Release of TYPO3 13.2.0"}},{"before":"ba4d9c507eb8bb3ab10e1d4968a14bcfcab4b5b1","after":"505b74d10e3d6e77b89c1164c7b400b4459d62b4","ref":"refs/heads/main","pushedAt":"2024-07-01T20:16:30.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] Fix image manipulation GUI only operating on 1st crop variant\n\nWhen multiple crop variants are defined (for example in EXT:styleguide\n\"Form engine elements - imageManipulation\" for \"crop_5\" with\n\"mobile\" and \"desktop), the currently selected aspect ratio\nand the size of the cropping box was only computed based on the\nfirst crop variant.\n\nThis patch uses a wrapping container for each variant and adjusts\nthe JavaScript to operate on that context.\n\nThe information for the current cropping box size is now also\nbased on this context.\n\nResolves: #103879\nReleases: main, 12.4\nChange-Id: I38e235ddb5ed5f7463a5f0931608944326097f9f\nReviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/84781\nTested-by: Benni Mack \nTested-by: Jasmina Ließmann \nReviewed-by: Benni Mack \nReviewed-by: Jasmina Ließmann \nTested-by: core-ci ","shortMessageHtmlLink":"[BUGFIX] Fix image manipulation GUI only operating on 1st crop variant"}},{"before":"9a33dd8f157a268854c0d81cd0d1799947bb3497","after":"3c84c39c7a808020278735f58530bc4cd2fd1046","ref":"refs/heads/12.4","pushedAt":"2024-07-01T20:14:33.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] Fix image manipulation GUI only operating on 1st crop variant\n\nWhen multiple crop variants are defined (for example in EXT:styleguide\n\"Form engine elements - imageManipulation\" for \"crop_5\" with\n\"mobile\" and \"desktop), the currently selected aspect ratio\nand the size of the cropping box was only computed based on the\nfirst crop variant.\n\nThis patch uses a wrapping container for each variant and adjusts\nthe JavaScript to operate on that context.\n\nThe information for the current cropping box size is now also\nbased on this context.\n\nResolves: #103879\nReleases: main, 12.4\nChange-Id: I38e235ddb5ed5f7463a5f0931608944326097f9f\nReviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/84963\nTested-by: Jasmina Ließmann \nReviewed-by: Jasmina Ließmann \nTested-by: core-ci ","shortMessageHtmlLink":"[BUGFIX] Fix image manipulation GUI only operating on 1st crop variant"}},{"before":"887e319063660f932884f6202627c9d8c6df318d","after":"ba4d9c507eb8bb3ab10e1d4968a14bcfcab4b5b1","ref":"refs/heads/main","pushedAt":"2024-07-01T15:49:31.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] Re-establish TcaMigration tests for flex form\n\nTcaMigration for flex form fields lived in FormEngine\nrelated TcaFlexPrepare, and has been moved to\nFlexFormTools with #99756.\nThe related tests were located within UnitDeprecated\nsince they trigger_error(, E_USER_DEPRECATED). Those\nhave been later removed with #101115 during v13\ndeprecation removals. This is bad, we do need to know\nif this recursive implemention works.\n\n* Move remaining FormEngine TcaFlexPrepareTest from\n unit to functional tests for simplified maintenance.\n* Use DI for TcaItemsProcessorFunctions - a class\n used as TCA 'itemsProcFunc' for special BE cases.\n* Add tests of flex form TcaMigration to functional\n FlexFormToolsTests. This is done using a dummy\n error handler to have them within casual (non\n deprecated) tests, which should prevent accidential\n removal in the future.\n* Move TcaItemsProcessorFunctionsTest unit tests to\n a functional test case for simplified maintenance.\n\nResolves: #104287\nRelated: #99756\nRelated: #101115\nReleases: main\nChange-Id: I8cfcdb8a42f9029d909cdde31f382541e2285096\nReviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/85050\nTested-by: Garvin Hicking \nTested-by: Christian Kuhn \nTested-by: Benni Mack \nReviewed-by: Christian Kuhn \nReviewed-by: Benni Mack \nReviewed-by: Garvin Hicking \nTested-by: core-ci ","shortMessageHtmlLink":"[TASK] Re-establish TcaMigration tests for flex form"}},{"before":"e954e6cb36d4695e97342039a392a866358efca3","after":"9a33dd8f157a268854c0d81cd0d1799947bb3497","ref":"refs/heads/12.4","pushedAt":"2024-07-01T10:48: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] Avoid implicitly nullable class method parameter in `EXT:backend`\n\nWith PHP 8.4 marking method parameter implicitly nullable\nis deprecated and will emit a `E_DEPRECATED` warning. One\nrecommended way to resolve this, is making it explicitly\nnullable using the `?` nullable operator or adding a null\ntype to an union type definition. [1]\n\nThis prepares the way towards PHP 8.4 compatibility.\n\n[1] https://php.watch/versions/8.4/implicitly-marking-parameter-type-nullable-deprecated\n\nResolves: #104278\nReleases: main, 12.4, 11.5\nChange-Id: Ia3a4bc344b369b8697c88ed14ac06354dd988dce\nReviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/85041\nTested-by: core-ci \nTested-by: Georg Ringer \nReviewed-by: Georg Ringer ","shortMessageHtmlLink":"[TASK] Avoid implicitly nullable class method parameter in EXT:backend"}},{"before":"b098a23baa3916b07477b2f3e7ee1bd2df4cdf88","after":"887e319063660f932884f6202627c9d8c6df318d","ref":"refs/heads/main","pushedAt":"2024-07-01T10:46:56.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 implicitly nullable class method parameter in `EXT:backend`\n\nWith PHP 8.4 marking method parameter implicitly nullable\nis deprecated and will emit a `E_DEPRECATED` warning. One\nrecommended way to resolve this, is making it explicitly\nnullable using the `?` nullable operator or adding a null\ntype to an union type definition. [1]\n\nThis prepares the way towards PHP 8.4 compatibility.\n\n[1] https://php.watch/versions/8.4/implicitly-marking-parameter-type-nullable-deprecated\n\nResolves: #104278\nReleases: main, 12.4, 11.5\nChange-Id: Ia3a4bc344b369b8697c88ed14ac06354dd988dce\nReviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/85040\nTested-by: Benni Mack \nTested-by: core-ci \nReviewed-by: Georg Ringer \nReviewed-by: Benni Mack \nTested-by: Georg Ringer ","shortMessageHtmlLink":"[TASK] Avoid implicitly nullable class method parameter in EXT:backend"}},{"before":"c1dc057e44f0d23ab01aa2bbe07506bbe6fe30c4","after":"77553ea2c245fd8d9afba1f6b3449ee81222d4a0","ref":"refs/heads/11.5","pushedAt":"2024-07-01T10:44: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":"[TASK] Avoid implicitly nullable class method parameter in `EXT:backend`\n\nWith PHP 8.4 marking method parameter implicitly nullable\nis deprecated and will emit a `E_DEPRECATED` warning. One\nrecommended way to resolve this, is making it explicitly\nnullable using the `?` nullable operator or adding a null\ntype to an union type definition. [1]\n\nThis prepares the way towards PHP 8.4 compatibility.\n\n[1] https://php.watch/versions/8.4/implicitly-marking-parameter-type-nullable-deprecated\n\nResolves: #104278\nReleases: main, 12.4, 11.5\nChange-Id: Ia3a4bc344b369b8697c88ed14ac06354dd988dce\nReviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/85042\nTested-by: Georg Ringer \nTested-by: core-ci \nReviewed-by: Georg Ringer ","shortMessageHtmlLink":"[TASK] Avoid implicitly nullable class method parameter in EXT:backend"}},{"before":"adbc226d8af5d996933c5c8d29b8d8c3af82a60d","after":"b098a23baa3916b07477b2f3e7ee1bd2df4cdf88","ref":"refs/heads/main","pushedAt":"2024-07-01T08:50: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":"[TASK] Make codemirror respect color-scheme\n\nWe are adapting the CodeMirror implementation to also\nrespect the current `color-scheme`, instead of purly rely on\n`prefers-color-scheme`.\n\nResolves: #104279\nReleases: main\nChange-Id: Iafcde4ee2581c68378874c32050855b1b54a8dee\nReviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/85039\nTested-by: Andreas Kienast \nReviewed-by: Andreas Kienast \nTested-by: core-ci \nReviewed-by: Oliver Bartsch \nTested-by: Oliver Bartsch ","shortMessageHtmlLink":"[TASK] Make codemirror respect color-scheme"}},{"before":"998abc711826e6c7ee66c3f1f41ac525e6a6fc8c","after":"adbc226d8af5d996933c5c8d29b8d8c3af82a60d","ref":"refs/heads/main","pushedAt":"2024-07-01T07:35:30.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] Inherit example color scheme when not set\n\nThe styleguide examples were forced into adaptive light dark\nmode instead of respecting the current inheritance. We are now\nonly forcing dedicated modes when the `colorschemes` option of\nthe CodeViewHelper is set.\n\nResolves: #104276\nReleases: main\nChange-Id: Iea2ceb3ad429af97a10902a3e9b4a1be9df7f653\nReviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/85038\nTested-by: core-ci \nReviewed-by: Andreas Kienast \nTested-by: Benjamin Kott \nTested-by: Oliver Bartsch \nReviewed-by: Oliver Bartsch \nReviewed-by: Benjamin Kott \nTested-by: Andreas Kienast ","shortMessageHtmlLink":"[TASK] Inherit example color scheme when not set"}},{"before":"a415800ee163b89adc706b3ecfa8f4f4f2398bfa","after":"c1dc057e44f0d23ab01aa2bbe07506bbe6fe30c4","ref":"refs/heads/11.5","pushedAt":"2024-07-01T06:09: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":"[TASK] Fix CGL issues\n\nApply the latest rules of php-cs-fixer for\nboth fixer (code and header-comment) also\nin the `Build/Scripts` folder.\n\nThe Build folder is now added to the usual\nphp-cs-fixer execution for code and header\nfixer scripts to avoid code style drifitng\nin this folder for the future.\n\nUsed command(s):\n\n Build/Scripts/runTests.sh -s cgl ; \\\n Build/Scripts/runTests.sh -s cglHeader\n\nResolves: #104274\nReleases: main, 12.4, 11.5\nChange-Id: I7977e2254b9e271c45b840c6696cd7600ab0b1aa\nReviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/85036\nReviewed-by: Stefan Bürk \nTested-by: core-ci \nTested-by: Stefan Bürk ","shortMessageHtmlLink":"[TASK] Fix CGL issues"}},{"before":"e0c3a12e194eea18c63976c4a9b3e4206d0abefa","after":"e954e6cb36d4695e97342039a392a866358efca3","ref":"refs/heads/12.4","pushedAt":"2024-07-01T05: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":"[BUGFIX] Prevent rendering FlexForm diff of deleted records in history\n\nWhen the record does not exist anymore, then the FlexForm definition\nmight also not exist anymore (imagine a removed plugin) and it results\nin an Exception.\n\nResolves: #102656\nReleases: main, 12.4\nChange-Id: I3eac287a50366ae8ca66416080738634eb65ae97\nReviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/84643\nTested-by: Georg Ringer \nReviewed-by: Georg Ringer \nReviewed-by: Stefan Bürk \nTested-by: core-ci \nTested-by: Stefan Bürk ","shortMessageHtmlLink":"[BUGFIX] Prevent rendering FlexForm diff of deleted records in history"}},{"before":"80deb1ca0e17b1b986dab0fbca07aa129b2924b5","after":"998abc711826e6c7ee66c3f1f41ac525e6a6fc8c","ref":"refs/heads/main","pushedAt":"2024-06-30T14:06:16.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 MockEventDispatcher\n\nThe MockEventDispatcher unit test fixture became\nuseless with introduction of NoopEventDispatcher.\n\nThe patch removes last remains: Most simply inject\nNoopEventDispatcher, some others create a mock of\nEventDispatcherInterface and use it for event\nmanipulation when testing $subjects that act on\nevent results.\n\nResolves: #104273\nRelated: #97449\nRelated: #98016\nReleases: main\nChange-Id: I0babc60cdd3c87bf9f25a931edfd3f47f642bfae\nReviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/85032\nTested-by: core-ci \nTested-by: Stefan Bürk \nTested-by: Anja Leichsenring \nReviewed-by: Stefan Bürk \nReviewed-by: Anja Leichsenring ","shortMessageHtmlLink":"[TASK] Avoid MockEventDispatcher"}},{"before":"29a0418954cf94d9395ae28970386f3edfa7c0f6","after":"80deb1ca0e17b1b986dab0fbca07aa129b2924b5","ref":"refs/heads/main","pushedAt":"2024-06-30T12:25:03.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] Have more DI in FlexFormTools\n\nFlexFormTools is a stateless service since #102229.\nThe - also stateless - TcaMigration dependency is\nnow injected. Get the service injected more often\nand adapt a few tests to deal with this.\n\nResolves: #104268\nRelated: #102229\nReleases: main\nChange-Id: I4cca73dc90ec652a4963b56c9a6ce5e2fccccf17\nReviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/85026\nTested-by: Andreas Nedbal \nReviewed-by: Christian Kuhn \nTested-by: Christian Kuhn \nReviewed-by: Stefan Bürk \nTested-by: core-ci \nReviewed-by: Andreas Nedbal \nTested-by: Stefan Bürk ","shortMessageHtmlLink":"[TASK] Have more DI in FlexFormTools"}},{"before":"ae0ae7c4a209ce8c3f1ff1fddf9ebb008123a394","after":"a415800ee163b89adc706b3ecfa8f4f4f2398bfa","ref":"refs/heads/11.5","pushedAt":"2024-06-29T13:16: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":"[BUGFIX] Fix invalid FormEngine HTML structure on edge-case\n\nWhen the TCA type \"group\" is rendered in FormEngine, under\ncertain circumstances the HTML structure would close add\n`
` elements without opening those first. This will\nlead to a record not being editable, because variables are\nwrongly transferred due to the browser-rendering of wrong\nHTML nesting levels.\n\nThis behaviour is an edge case and only happens with this TCA\nconfiguration:\n\n* either `config[hideMoveIcons]` is set to `true`\n* or `config[hideDeleteIcon]` is set to `true`\n\nResolves: #98436\nReleases: main, 12.4, 11.5\nChange-Id: Ibb28c6130051b3dae92b3285df0831e84634e210\nReviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/85012\nTested-by: Stefan Bürk \nReviewed-by: Stefan Bürk \nTested-by: core-ci ","shortMessageHtmlLink":"[BUGFIX] Fix invalid FormEngine HTML structure on edge-case"}},{"before":"56fa5170ec7e4696b033481e083a181793e14a28","after":"e0c3a12e194eea18c63976c4a9b3e4206d0abefa","ref":"refs/heads/12.4","pushedAt":"2024-06-29T13:14: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":"[BUGFIX] Fix invalid FormEngine HTML structure on edge-case\n\nWhen the TCA type \"group\" or \"folder\" is rendered in FormEngine,\nunder certain circumstances the HTML structure would close add\n`
` elements without opening those first. This will lead\nto a record not being editable, because variables are wrongly\ntransferred due to the browser-rendering of wrong HTML nesting\nlevels.\n\nThis behaviour is an edge case and only happens with this TCA\nconfiguration:\n\n* either `config[hideMoveIcons]` is set to `true`\n* or `config[hideDeleteIcon]` is set to `true`\n\nResolves: #98436\nReleases: main, 12.4, 11.5\nChange-Id: Ibb28c6130051b3dae92b3285df0831e84634e210\nReviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/84960\nTested-by: core-ci \nTested-by: Stefan Bürk \nReviewed-by: Stefan Bürk ","shortMessageHtmlLink":"[BUGFIX] Fix invalid FormEngine HTML structure on edge-case"}},{"before":"777be12bea133dff21935be1687d7780207f28d8","after":"29a0418954cf94d9395ae28970386f3edfa7c0f6","ref":"refs/heads/main","pushedAt":"2024-06-29T13:12: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":"[BUGFIX] Fix invalid FormEngine HTML structure on edge-case\n\nWhen the TCA type \"group\" or \"folder\" is rendered in FormEngine,\nunder certain circumstances the HTML structure would close add\n`
` elements without opening those first. This will lead\nto a record not being editable, because variables are wrongly\ntransferred due to the browser-rendering of wrong HTML nesting\nlevels.\n\nThis behaviour is an edge case and only happens with this TCA\nconfiguration:\n\n* either `config[hideMoveIcons]` is set to `true`\n* or `config[hideDeleteIcon]` is set to `true`\n\nResolves: #98436\nReleases: main, 12.4, 11.5\nChange-Id: Ibb28c6130051b3dae92b3285df0831e84634e210\nReviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/84897\nReviewed-by: Georg Ringer \nReviewed-by: Mogens Fiebrandt \nTested-by: Stefan Bürk \nTested-by: core-ci \nReviewed-by: Stefan Bürk \nTested-by: Markus Klein \nReviewed-by: Markus Klein \nTested-by: Georg Ringer \nTested-by: Mogens Fiebrandt ","shortMessageHtmlLink":"[BUGFIX] Fix invalid FormEngine HTML structure on edge-case"}},{"before":"9e762191944ad15a39359d56f717e03dacac6bc0","after":"777be12bea133dff21935be1687d7780207f28d8","ref":"refs/heads/main","pushedAt":"2024-06-28T18:09: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] Use DI in DataHandler\n\nDataHandler is now DI aware and gets a bunch of\nservices injected.\n\nWe're not injecting any potentially possible\nservice blindly - we're omitting stateful ones,\nand declare some common classes readonly\nalong the way to make this more clear.\n\nThe DataHandler unit test receives a slightly\nbigger update to deal with this properly.\n\nThis needs a raise of TF, which had a\n`new DataHandler()` in one place:\n\n> composer u typo3/testing-framework\n\nResolves: #104253\nRelated: #104245\nRelated: #104241\nRelated: #104240\nReleases: main\nChange-Id: Ie1e296b9884d8299ce699ed525fdd2b69d460ebd\nReviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/84993\nTested-by: Stefan Bürk \nTested-by: core-ci \nReviewed-by: Christian Kuhn \nTested-by: Christian Kuhn \nTested-by: Benni Mack \nReviewed-by: Stefan Bürk \nReviewed-by: Benni Mack ","shortMessageHtmlLink":"[TASK] Use DI in DataHandler"}},{"before":"39c3c053e0e7cf749ec49ab10894685a14b178a7","after":"9e762191944ad15a39359d56f717e03dacac6bc0","ref":"refs/heads/main","pushedAt":"2024-06-28T14:17:27.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 invalid object type in FileExtensionFilter\n\nfilter() retrieves 'DataHandler|DatabaseRecordList $dataHandler'\nas argument to call $dataHandler->deleteAction on it.\nDatabaseRecordList and extending classes have no such method.\n\nResolves: #104248\nRelated: #98479\nReleases: main\nChange-Id: I2fd425c5503a546e6cbf8ed3dae94145e2cb85d7\nReviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/84994\nReviewed-by: Oliver Bartsch \nTested-by: Christian Kuhn \nTested-by: Stefan Bürk \nTested-by: Oliver Bartsch \nReviewed-by: Christian Kuhn \nTested-by: core-ci \nReviewed-by: Oliver Klee \nReviewed-by: Stefan Bürk ","shortMessageHtmlLink":"[TASK] Avoid invalid object type in FileExtensionFilter"}}],"hasNextPage":true,"hasPreviousPage":false,"activityType":"all","actor":null,"timePeriod":"all","sort":"DESC","perPage":30,"cursor":"djE6ks8AAAAEeIPLsQA","startCursor":null,"endCursor":null}},"title":"Activity · TYPO3-CMS/backend"}