{"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:1715675741.0","currentOid":""},"activityList":{"items":[{"before":"c702d6c65574ae1085240a682681c276ce2537b6","after":"342b66b7205415488075b863a95ae2b24c7ad369","ref":"refs/heads/main","pushedAt":"2024-06-04T11:37: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] IRRE: Rewrite stylesheet loading sequence\n\nThe stylesheet loading process in IRRE was kept for several years and\nmoved from version to version. A recent change in #103375 migrated a\nusage of `delete` to `.splice()`, breaking stylesheet loading as the\noriginal iterated object was modified.\n\nSince the code was quite dated and had other potental bugs, the whole\nloading sequence has been transformed to functional programming style\nto reduce complicated, potentially error-prone, array operations.\n\nResolves: #103971\nRelated: #103375\nReleases: main, 12.4\nChange-Id: I18caafc68ceebce53723b7208270043faafc7458\nReviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/84487\nTested-by: rogier Helmer \nTested-by: core-ci \nReviewed-by: rogier Helmer \nTested-by: Benjamin Franzke \nReviewed-by: Benjamin Franzke ","shortMessageHtmlLink":"[BUGFIX] IRRE: Rewrite stylesheet loading sequence"}},{"before":"e434948591fbe802d0446226860a69f604ca5a52","after":"8631f0208e3bac9720c46c1c3e1abb5bd77ab5d6","ref":"refs/heads/12.4","pushedAt":"2024-06-04T11:35: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":"[BUGFIX] IRRE: Rewrite stylesheet loading sequence\n\nThe stylesheet loading process in IRRE was kept for several years and\nmoved from version to version. A recent change in #103375 migrated a\nusage of `delete` to `.splice()`, breaking stylesheet loading as the\noriginal iterated object was modified.\n\nSince the code was quite dated and had other potental bugs, the whole\nloading sequence has been transformed to functional programming style\nto reduce complicated, potentially error-prone, array operations.\n\nResolves: #103971\nRelated: #103375\nReleases: main, 12.4\nChange-Id: I18caafc68ceebce53723b7208270043faafc7458\nReviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/84488\nTested-by: core-ci \nTested-by: Benjamin Franzke \nReviewed-by: Benjamin Franzke ","shortMessageHtmlLink":"[BUGFIX] IRRE: Rewrite stylesheet loading sequence"}},{"before":"fac8aa3797a372e7aa06d1bee74a0648bb39e5e6","after":"c702d6c65574ae1085240a682681c276ce2537b6","ref":"refs/heads/main","pushedAt":"2024-06-04T08:29: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] Reduce GU::makeInstance calls in Unit Tests\n\nAdditional potential functionality (DI, XClass resolving, etc.) of\nGU::makeInstance is usually not a wanted behaviour in unit tests.\nFor creation of system under test `new` should be used.\nDependencies, if necessary, should be mocks.\nThis patch reduces the obvious cases, more complicated ones will\nbe tackled with follow ups.\n\nResolves: #103902\nReleases: main, 12.4\nChange-Id: I07cbe6f10fe11e1239cdd5f0fe7496948eed5a44\nReviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/84386\nTested-by: Oliver Klee \nReviewed-by: Benjamin Franzke \nReviewed-by: Oliver Klee \nTested-by: Benjamin Franzke ","shortMessageHtmlLink":"[TASK] Reduce GU::makeInstance calls in Unit Tests"}},{"before":"16062dd1feed96a2ce7aa0e353b658966d684392","after":"e434948591fbe802d0446226860a69f604ca5a52","ref":"refs/heads/12.4","pushedAt":"2024-06-03T07:58: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":"[BUGFIX] Fix initialization of 00:00 time input\n\nThe value of the `time` input is sent as an ISO date to the\nFormEngine, except for the time \"00:00\", which is just submitted\nas \"0\".\n\nThis has lead to the input field not getting populated by\nthe JavaScript initialization, and the input \"00:00\" was lost.\n\nIn cases where such a `time` input is set as a required\nfield, the validation would then fail because of the field\ngetting interpreted as being empty/unset.\n\nWith this patch, a \"0\" value is also interpreted as a valid\n\"1970-01-01T00:00:00+00:00\" string, that is parseable by\nFormEngine. Note this only affects display within the\nFormEngine; the format of the stored data is not changed\n(converted by DataHandler to proper values and covered by\nexisting tests).\n\nIMPORTANT: This only applies to NULLABLE time|timesec\ninputs. Only for this configuration it is possible to\ndecide, that a stored \"0\" value in the database is\nactually \"00:00\" and not an unset entry.\n\nIntegrators/developers need to set 'nullable'\nTCA key to 'true' of the corresponding 'config' array,\nin case they want to make a time/timesec input picker\nbe able to store and retrieve \"00:00\" as a valid\ntimestamp.\n\nResolves: #102602\nReleases: main, 12.4\nChange-Id: Id5dae6564a5da9ab3abd99bdc14b718cc7064464\nReviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/84459\nTested-by: Benjamin Franzke \nReviewed-by: Benjamin Franzke \nTested-by: core-ci ","shortMessageHtmlLink":"[BUGFIX] Fix initialization of 00:00 time input"}},{"before":"1db07af707a96eb8ddbf714e115bb6fdac4d82be","after":"fac8aa3797a372e7aa06d1bee74a0648bb39e5e6","ref":"refs/heads/main","pushedAt":"2024-06-03T07:56: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":"[BUGFIX] Fix initialization of 00:00 time input\n\nThe value of the `time` input is sent as an ISO date to the\nFormEngine, except for the time \"00:00\", which is just submitted\nas \"0\".\n\nThis has lead to the input field not getting populated by\nthe JavaScript initialization, and the input \"00:00\" was lost.\n\nIn cases where such a `time` input is set as a required\nfield, the validation would then fail because of the field\ngetting interpreted as being empty/unset.\n\nWith this patch, a \"0\" value is also interpreted as a valid\n\"1970-01-01T00:00:00+00:00\" string, that is parseable by\nFormEngine. Note this only affects display within the\nFormEngine; the format of the stored data is not changed\n(converted by DataHandler to proper values and covered by\nexisting tests).\n\nIMPORTANT: This only applies to NULLABLE time|timesec\ninputs. Only for this configuration it is possible to\ndecide, that a stored \"0\" value in the database is\nactually \"00:00\" and not an unset entry.\n\nIntegrators/developers need to set 'nullable'\nTCA key to 'true' of the corresponding 'config' array,\nin case they want to make a time/timesec input picker\nbe able to store and retrieve \"00:00\" as a valid\ntimestamp.\n\nResolves: #102602\nReleases: main, 12.4\nChange-Id: Id5dae6564a5da9ab3abd99bdc14b718cc7064464\nReviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/82093\nTested-by: core-ci \nTested-by: Benjamin Franzke \nReviewed-by: Garvin Hicking \nTested-by: Garvin Hicking \nReviewed-by: Benjamin Franzke ","shortMessageHtmlLink":"[BUGFIX] Fix initialization of 00:00 time input"}},{"before":"ce8e76a4acfba0753b56dadd796b2c395384d32f","after":"16062dd1feed96a2ce7aa0e353b658966d684392","ref":"refs/heads/12.4","pushedAt":"2024-05-31T06:52: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] Remove unneeded `$siteMockRevelation` in SiteResolvingTest\n\nWith migration away from prophecy during v12 development, the variable\n`$siteMockRevelation` is not needed anymore as phpunit mocks don't know\nthe concept of revelations.\n\nResolves: #103958\nReleases: main, 12.4\nChange-Id: I92497737dfbba3ef1cd99e4fbd96751e00057a16\nReviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/84457\nTested-by: core-ci \nTested-by: Oliver Bartsch \nReviewed-by: Oliver Bartsch ","shortMessageHtmlLink":"[TASK] Remove unneeded $siteMockRevelation in SiteResolvingTest"}},{"before":"246e25640cc5456bb217105eaad9811cb2e59584","after":"1db07af707a96eb8ddbf714e115bb6fdac4d82be","ref":"refs/heads/main","pushedAt":"2024-05-31T06:45: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] Remove unneeded `$siteMockRevelation` in SiteResolvingTest\n\nWith migration away from prophecy during v12 development, the variable\n`$siteMockRevelation` is not needed anymore as phpunit mocks don't know\nthe concept of revelations.\n\nResolves: #103958\nReleases: main, 12.4\nChange-Id: I92497737dfbba3ef1cd99e4fbd96751e00057a16\nReviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/84449\nTested-by: core-ci \nReviewed-by: Oliver Bartsch \nTested-by: Anja Leichsenring \nReviewed-by: Kevin Appelt \nReviewed-by: Anja Leichsenring \nTested-by: Oliver Bartsch ","shortMessageHtmlLink":"[TASK] Remove unneeded $siteMockRevelation in SiteResolvingTest"}},{"before":"5e703239ec68e918e2829332b90683c4b5dfd88e","after":"246e25640cc5456bb217105eaad9811cb2e59584","ref":"refs/heads/main","pushedAt":"2024-05-31T06:30: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":"[BUGFIX] Fix some styling in color picker component\n\nThis commit updates some colors in the color picker component. The dark\nbackground is removed from focussed input fields. Also, the input\nstyling now matches FormEngine styling.\n\nResolves: #103891\nReleases: main\nChange-Id: I9a3a9e10c48be0bf49395d388be55cb8c8535693\nReviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/84379\nReviewed-by: Andreas Kienast \nTested-by: Benjamin Franzke \nTested-by: core-ci \nTested-by: Jasmina Ließmann \nTested-by: Andreas Kienast \nReviewed-by: Jasmina Ließmann \nReviewed-by: Benjamin Franzke ","shortMessageHtmlLink":"[BUGFIX] Fix some styling in color picker component"}},{"before":"596c12171a458ca1e2f2641b84d80b607052ae47","after":"ce8e76a4acfba0753b56dadd796b2c395384d32f","ref":"refs/heads/12.4","pushedAt":"2024-05-29T08:09: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] Use parent's module icon as fallback for shortcuts\n\nIf no icon is provided for submodule, use a fallback to the icon of the\nparent module instead of directly using the empty-empty icon.\n\nResolves: #103904\nReleases: main, 12.4\nChange-Id: I4e989483880fd88df904e9028f1d2cf6cd5c29f7\nReviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/84454\nTested-by: core-ci \nReviewed-by: Georg Ringer \nTested-by: Georg Ringer ","shortMessageHtmlLink":"[BUGFIX] Use parent's module icon as fallback for shortcuts"}},{"before":"e945c53076c2dc049083b898168eea78a3583dc2","after":"5e703239ec68e918e2829332b90683c4b5dfd88e","ref":"refs/heads/main","pushedAt":"2024-05-29T08:02:07.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 parent's module icon as fallback for shortcuts\n\nIf no icon is provided for submodule, use a fallback to the icon of the\nparent module instead of directly using the empty-empty icon.\n\nResolves: #103904\nReleases: main, 12.4\nChange-Id: I4e989483880fd88df904e9028f1d2cf6cd5c29f7\nReviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/84390\nTested-by: Riccardo De Contardi \nTested-by: core-ci \nTested-by: Georg Ringer \nTested-by: Garvin Hicking \nReviewed-by: Garvin Hicking \nReviewed-by: Georg Ringer ","shortMessageHtmlLink":"[BUGFIX] Use parent's module icon as fallback for shortcuts"}},{"before":"3ff5504b27a67e7f43da8817e61edbd95acd6b0c","after":"e945c53076c2dc049083b898168eea78a3583dc2","ref":"refs/heads/main","pushedAt":"2024-05-27T12:34:13.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 PHP attributes more often to configure DI\n\nUsing PHP attributes to configure DI within classes\ndirectly is more easy to understand since developers\ndon't need to constantly look up DI configuration\nServices.yaml files, but have everything in one place.\n\nThe patch switches all classes that previously\nused '@cache.xy' to get a specific cache injected\nto an `Autowire` attribute.\n\nResolves: #103921\nReleases: main\nChange-Id: I16b064242cdbc2bbcfbed89700c97afac012fdf8\nReviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/84406\nTested-by: Benjamin Franzke \nReviewed-by: Stefan Bürk \nReviewed-by: Benjamin Franzke \nTested-by: core-ci \nTested-by: Stefan Bürk ","shortMessageHtmlLink":"[TASK] Use PHP attributes more often to configure DI"}},{"before":"e936b12784ce6f53a5f1424fc0e0df4e57b7be48","after":"3ff5504b27a67e7f43da8817e61edbd95acd6b0c","ref":"refs/heads/main","pushedAt":"2024-05-27T12:29: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] Avoid implicitly nullable parameter on `DatabaseRecordException`\n\nWith PHP 8.4 marking method parameter implicitly nullable\nis depreacted and will emit a `E_DEPRECATED` warning. One\nrecommended way to resolve this, is making it explicitly\nnullable using the `?` nullable operator. [1]\n\nIn cases, where are implicitly nullable parameter exists\nbefore not-nullable parameters in a method or constructor,\nmaking it explicitly nullable will emit a\n\n Optional parameter declared before required\n parameter is implicitly treated as a required\n parameter\n\nsince PHP 8.0 [2].\n\nThis change removes the `null` default value and adds the `?`\nnullable operator to the previousException parameter for the\n`\\TYPO3\\CMS\\Backend\\Form\\Exception\\DatabaseRecordException`\nconstructor.\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[2] https://php.watch/versions/8.0/deprecate-required-param-after-optional\n\nResolves: #103926\nReleases: main, 12.4, 11.5\nChange-Id: I4d1506b24b3113a74b37b986fa4f23f24e6219fb\nReviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/84415\nReviewed-by: Oliver Klee \nTested-by: Christian Kuhn \nReviewed-by: Stefan Bürk \nReviewed-by: Christian Kuhn \nTested-by: Stefan Bürk \nTested-by: core-ci \nTested-by: Oliver Klee ","shortMessageHtmlLink":"[TASK] Avoid implicitly nullable parameter on DatabaseRecordException"}},{"before":"740c460f1f7317cfeab19f87214818870e593874","after":"596c12171a458ca1e2f2641b84d80b607052ae47","ref":"refs/heads/12.4","pushedAt":"2024-05-27T12:27:36.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 parameter on `DatabaseRecordException`\n\nWith PHP 8.4 marking method parameter implicitly nullable\nis depreacted and will emit a `E_DEPRECATED` warning. One\nrecommended way to resolve this, is making it explicitly\nnullable using the `?` nullable operator. [1]\n\nIn cases, where are implicitly nullable parameter exists\nbefore not-nullable parameters in a method or constructor,\nmaking it explicitly nullable will emit a\n\n Optional parameter declared before required\n parameter is implicitly treated as a required\n parameter\n\nsince PHP 8.0 [2].\n\nThis change removes the `null` default value and adds the `?`\nnullable operator to the previousException parameter for the\n`\\TYPO3\\CMS\\Backend\\Form\\Exception\\DatabaseRecordException`\nconstructor.\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[2] https://php.watch/versions/8.0/deprecate-required-param-after-optional\n\nResolves: #103926\nReleases: main, 12.4, 11.5\nChange-Id: I4d1506b24b3113a74b37b986fa4f23f24e6219fb\nReviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/84360\nTested-by: Stefan Bürk \nReviewed-by: Stefan Bürk \nTested-by: core-ci ","shortMessageHtmlLink":"[TASK] Avoid implicitly nullable parameter on DatabaseRecordException"}},{"before":"03e10ca8ceae7664361c28a8aed7f606c8512398","after":"73e83b0a4306d5207611add923eb496ff5ed1e2d","ref":"refs/heads/11.5","pushedAt":"2024-05-27T12:25:38.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 parameter on `DatabaseRecordException`\n\nWith PHP 8.4 marking method parameter implicitly nullable\nis depreacted and will emit a `E_DEPRECATED` warning. One\nrecommended way to resolve this, is making it explicitly\nnullable using the `?` nullable operator. [1]\n\nIn cases, where are implicitly nullable parameter exists\nbefore not-nullable parameters in a method or constructor,\nmaking it explicitly nullable will emit a\n\n Optional parameter declared before required\n parameter is implicitly treated as a required\n parameter\n\nsince PHP 8.0 [2].\n\nThis change removes the `null` default value and adds the `?`\nnullable operator to the previousException parameter for the\n`\\TYPO3\\CMS\\Backend\\Form\\Exception\\DatabaseRecordException`\nconstructor.\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[2] https://php.watch/versions/8.0/deprecate-required-param-after-optional\n\nResolves: #103926\nReleases: main, 12.4, 11.5\nChange-Id: I4d1506b24b3113a74b37b986fa4f23f24e6219fb\nReviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/84361\nTested-by: Stefan Bürk \nTested-by: core-ci \nReviewed-by: Stefan Bürk ","shortMessageHtmlLink":"[TASK] Avoid implicitly nullable parameter on DatabaseRecordException"}},{"before":"250275d285b5b6a6991a8de92a05c7551ceaedec","after":"e936b12784ce6f53a5f1424fc0e0df4e57b7be48","ref":"refs/heads/main","pushedAt":"2024-05-26T07:35:18.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] Respect TCA \"check\" default for auto-create DB fields\n\nChange #101653 introduced the auto-creation of DB fields for TCA\ntype \"check\", but used a hardcoded \"0\" as default.\n\nSince TCA definitions might define a different default, and\nrecords may not always be created using the DataHandler to\nrespect TCA defaults, this can lead to DB entries getting\ncreated with an unexpected default setting.\n\nIMPORTANT: This patch only fixes the root cause of the bug.\nIf an existing v13 installation has already created new\nrecords after the DB migration wizard update in 13.0, all\nrecords may have wrong defaults. Check the contents of\nyour database for the fields listed below and apply\nmanual adjustments as needed (for example, record storages\nhaving \"auto_extract_metadata\"=1 instead of 0).\n\nAn example symptom of this is the auto-creation of a\nfile storage record, which uses the QueryBuilder to\ncreate a record, without specifying the whole list\nof all possible fields. For example then leading to\nadded YouTube media files not auto-creating metadata\nrecords.\n\nThis patch uses the proper evaluation of the TCA\n\"default\" setting of an auto-created field.\n\nIn TYPO3 Core this only affected `be_users.options` and\n`sys_file_storage.auto_extract_metadata` default record\ncreation. The latter field has now been included\nto the default record creation as a fixed value like\nthe others. A follow-up patch could rewrite this\nfunctionality using the DataHandler or QueryBuilder\ndefault value injection.\n\nTests have been created to verify this regression,\nexisting tests for be_user creation have been\nadapted for the proper default values.\n\nExecuting the DB schema analyzer will now\nadjust the following fields:\n\n* be_users.options (0->3)\n* sys_file_storage.is_browsable (0->1)\n* sys_file_storage.is_writable (0->1)\n* sys_file_storage.is_online (0->1)\n* sys_file_storage.auto_extract_metadata (0->1)\n* sys_file_metadata.visible (0->1)\n* tt_content.sectionIndex (0->1)\n* tx_styleguide_palette.palette_1_1 (0->1)\n* tx_styleguide_palette.palette_1_3 (0->1)\n* tx_styleguide_valuesdefault.checkbox_1 (0->1)\n* tx_styleguide_valuesdefault.checkbox_2 (0->1)\n* tx_styleguide_valuesdefault.checkbox_3 (0->5)\n* tx_styleguide_valuesdefault.checkbox_4 (0->5)\n* sys_workspace.edit_allow_notificaton_settings (0->3)\n* sys_workspace.edit_notification_preselection (0->2)\n* sys_workspace.publish_allow_notificaton_settings (0->3)\n* sys_workspace.publish_notification_preselection (0->1)\n* sys_workspace.execute_allow_notificaton_settings (0->3)\n* sys_workspace.execute_notification_preselection (0->3)\n* sys_workspace_stage.allow_notificaton_settings (0->3)\n* sys_workspace_stage.notification_preselection (0->8)\n\nResolves: #103915\nRelated: #101653\nReleases: main\nChange-Id: Ia42e00b03d1369efe319e41e2b406b5303804854\nReviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/84402\nTested-by: Anja Leichsenring \nTested-by: Georg Ringer \nReviewed-by: Georg Ringer \nReviewed-by: Stefan Bürk \nReviewed-by: Anja Leichsenring \nReviewed-by: Oliver Wand \nTested-by: core-ci ","shortMessageHtmlLink":"[BUGFIX] Respect TCA \"check\" default for auto-create DB fields"}},{"before":"9f1e03030134680cef6367fb98074599e2ecf085","after":"250275d285b5b6a6991a8de92a05c7551ceaedec","ref":"refs/heads/main","pushedAt":"2024-05-26T07:07: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] Avoid unused arg in PageTsConfigRecordsOverviewController\n\nAnd rename the method since those general\ngetButtons() methods are ugly.\n\nResolves: #103914\nRelated: #103903\nReleases: main, 12.4\nChange-Id: Iaa428d711b98d2bf178aa0ba54ab507f7ca1c09b\nReviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/84399\nTested-by: core-ci \nReviewed-by: Anja Leichsenring \nTested-by: Anja Leichsenring \nTested-by: Stefan Bürk \nTested-by: Christian Kuhn \nReviewed-by: Christian Kuhn \nReviewed-by: Stefan Bürk ","shortMessageHtmlLink":"[TASK] Avoid unused arg in PageTsConfigRecordsOverviewController"}},{"before":"35cd6bbdc02945bcc6ec9c1c68097f913c1dda7b","after":"740c460f1f7317cfeab19f87214818870e593874","ref":"refs/heads/12.4","pushedAt":"2024-05-26T07:05: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] Avoid unused arg in PageTsConfigRecordsOverviewController\n\nAnd rename the method since those general\ngetButtons() methods are ugly.\n\nResolves: #103914\nRelated: #103903\nReleases: main, 12.4\nChange-Id: Iaa428d711b98d2bf178aa0ba54ab507f7ca1c09b\nReviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/84358\nTested-by: core-ci \nTested-by: Christian Kuhn \nReviewed-by: Christian Kuhn ","shortMessageHtmlLink":"[TASK] Avoid unused arg in PageTsConfigRecordsOverviewController"}},{"before":"74ef046c64081865be0a5e485466e9ec48475f20","after":"9f1e03030134680cef6367fb98074599e2ecf085","ref":"refs/heads/main","pushedAt":"2024-05-25T12:54: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] Resolve display name for shortcuts\n\nThe shortcut button requires the resolved name as display name and not\nthe LLL path.\n\nResolves: #103903\nReleases: main, 12.4\nChange-Id: I59e38bf9c40f0a940fecb6ac3178b2976f168069\nReviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/84388\nTested-by: Torben Hansen \nTested-by: core-ci \nReviewed-by: Christian Kuhn \nTested-by: Christian Kuhn \nReviewed-by: Torben Hansen ","shortMessageHtmlLink":"[BUGFIX] Resolve display name for shortcuts"}},{"before":"1d145ecc78226c8635270e031c79a6c596467015","after":"35cd6bbdc02945bcc6ec9c1c68097f913c1dda7b","ref":"refs/heads/12.4","pushedAt":"2024-05-25T12:52: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":"[BUGFIX] Resolve display name for shortcuts\n\nThe shortcut button requires the resolved name as display name and not\nthe LLL path.\n\nResolves: #103903\nReleases: main, 12.4\nChange-Id: I59e38bf9c40f0a940fecb6ac3178b2976f168069\nReviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/84398\nTested-by: core-ci \nTested-by: Christian Kuhn \nReviewed-by: Christian Kuhn ","shortMessageHtmlLink":"[BUGFIX] Resolve display name for shortcuts"}},{"before":"2f4fa43866805e9f3c113447f08b0d6e885fe2c4","after":"74ef046c64081865be0a5e485466e9ec48475f20","ref":"refs/heads/main","pushedAt":"2024-05-25T11:56:36.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 `alwan` to 2.1.1\n\nExecuted commands:\n\n npm install --save alwan@^2.1.1\n npm run build\n\nResolves: #103890\nReleases: main\nChange-Id: Id8cd17bbb1142a0522e1fd80f7dbd0f83455720a\nReviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/84378\nTested-by: Christian Kuhn \nReviewed-by: Oliver Klee \nTested-by: Georg Ringer \nReviewed-by: Christian Kuhn \nTested-by: Jasmina Ließmann \nReviewed-by: Jasmina Ließmann \nReviewed-by: Georg Ringer \nTested-by: core-ci ","shortMessageHtmlLink":"[TASK] Update alwan to 2.1.1"}},{"before":"3dbb4a5f14a30b9abf2769c83ab9c2149d815407","after":"03e10ca8ceae7664361c28a8aed7f606c8512398","ref":"refs/heads/11.5","pushedAt":"2024-05-25T10:27:14.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] Add proper check in TcaInputPlaceholders\n\nThe configuration `foreign_table` of the type `select` is optional.\nAdd a check to avoid PHP warnings.\n\nResolves: #103825\nReleases: main, 12.4, 11.5\nChange-Id: I65925bae287a0ed340c67923ac4e4a2c72ce9d28\nReviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/84394\nTested-by: Christian Kuhn \nTested-by: core-ci \nReviewed-by: Christian Kuhn ","shortMessageHtmlLink":"[BUGFIX] Add proper check in TcaInputPlaceholders"}},{"before":"607da1349f1bcabd46871e33f0293803d6863cff","after":"2f4fa43866805e9f3c113447f08b0d6e885fe2c4","ref":"refs/heads/main","pushedAt":"2024-05-25T10:25:14.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] Add proper check in TcaInputPlaceholders\n\nThe configuration `foreign_table` of the type `select` is optional.\nAdd a check to avoid PHP warnings.\n\nResolves: #103825\nReleases: main, 12.4, 11.5\nChange-Id: I65925bae287a0ed340c67923ac4e4a2c72ce9d28\nReviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/84391\nTested-by: core-ci \nReviewed-by: Christian Kuhn \nTested-by: Anja Leichsenring \nReviewed-by: Anja Leichsenring \nTested-by: Christian Kuhn ","shortMessageHtmlLink":"[BUGFIX] Add proper check in TcaInputPlaceholders"}},{"before":"5deaefab0284d9ea6a614bef35d6297417f57fed","after":"1d145ecc78226c8635270e031c79a6c596467015","ref":"refs/heads/12.4","pushedAt":"2024-05-25T10:23: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":"[BUGFIX] Add proper check in TcaInputPlaceholders\n\nThe configuration `foreign_table` of the type `select` is optional.\nAdd a check to avoid PHP warnings.\n\nResolves: #103825\nReleases: main, 12.4, 11.5\nChange-Id: I65925bae287a0ed340c67923ac4e4a2c72ce9d28\nReviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/84395\nTested-by: core-ci \nTested-by: Christian Kuhn \nReviewed-by: Christian Kuhn ","shortMessageHtmlLink":"[BUGFIX] Add proper check in TcaInputPlaceholders"}},{"before":"2235bbe338754a398d9f382bd43a6210ce28fd8e","after":"5deaefab0284d9ea6a614bef35d6297417f57fed","ref":"refs/heads/12.4","pushedAt":"2024-05-24T12:59:55.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 some `ThumbnailViewHelper` functional tests\n\nThis change adds some tests for the `EXT:backend`\nThumbnailViewHelper, mainly to cover fix #102571.\n\nResolves: #103846\nRelated: #102571\nReleases: main, 12.4\nChange-Id: Id1acf6ddf6bc68c2dff0bfb7875859e07768e2af\nReviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/84353\nTested-by: core-ci \nTested-by: Stefan Bürk \nReviewed-by: Stefan Bürk ","shortMessageHtmlLink":"[TASK] Add some ThumbnailViewHelper functional tests"}},{"before":"0409dbe245a4bf36ac48490dcc0bfcbf785854d6","after":"607da1349f1bcabd46871e33f0293803d6863cff","ref":"refs/heads/main","pushedAt":"2024-05-24T12:15: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":"[FEATURE] Group-based content fetching in Frontend\n\nThis change adds a new RecordCollector which is similar\nto CONTENT cObject, except that it does not render the records\ndirectly, but instead creates instances of a generic Record\nobject, so the Templating Engine can deal with the way of\nhow the record should be rendered.\n\nBased on the Page Layout / Backend Layout, all registered\ncolPos contents are fetched, and grouped, if the Backend Layout\nhas an \"identifier\" set via a new PageContentFetchingProcessor\n(\"page-content\").\n\nThe slide functionality can now be defined in the Page Layout as well\n(Backend Layout), with a Enum defining to Collect, CollectReverse\nand a simple Slide logic.\n\nThis feature brings a clearer separation of fetching\ncontent from the database and the actual representation\nin the output (fluid) in place, allowing for further\noptimizations.\n\nIn addition, one needs to write much less TypoScript\nto fetch all contents from a page.\n\nNext steps is then to enrich the records with their\nrelations (see next feature), and to optimize the Fluid-based\nrendering for any kind of content.\n\nResolves: #103894\nReleases: main\nChange-Id: I6a1a0efacefe8c83e86b9551b00199c93e284a28\nReviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/83638\nReviewed-by: Oliver Bartsch \nTested-by: Georg Ringer \nReviewed-by: Benni Mack \nTested-by: Oliver Bartsch \nReviewed-by: Georg Ringer \nTested-by: core-ci \nTested-by: Benni Mack ","shortMessageHtmlLink":"[FEATURE] Group-based content fetching in Frontend"}},{"before":"7f6d49bd4d33681a51954e926fccef67babaeab1","after":"0409dbe245a4bf36ac48490dcc0bfcbf785854d6","ref":"refs/heads/main","pushedAt":"2024-05-24T08:23: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] Streamline usage of `Persistent.loadFromServer()`\n\nPreviously, the internal method `loadFromServer()` from the module\n`@typo3/backend/storage/persistent` fetched the data, wrote it into an\ninternal property `data` and also returned it. The code is now\nsimplified to only return the response.\nSetting `data` is now done within the public `get()` method, which is\nnow also simplified a bit.\n\nResolves: #103886\nReleases: main\nChange-Id: I975a6ad0c2761afdadadfdc05dfa9c11a47779fa\nReviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/84374\nTested-by: Andreas Nedbal \nReviewed-by: Andreas Kienast \nReviewed-by: Frank Nägler \nReviewed-by: Marvin Buchmann \nReviewed-by: Willi Wehmeier \nTested-by: core-ci \nTested-by: Frank Nägler \nReviewed-by: Andreas Nedbal \nTested-by: Andreas Kienast ","shortMessageHtmlLink":"[TASK] Streamline usage of Persistent.loadFromServer()"}},{"before":"ea702dbdb22d058ebd823c932e819ed027a9fc0c","after":"7f6d49bd4d33681a51954e926fccef67babaeab1","ref":"refs/heads/main","pushedAt":"2024-05-22T11:47:09.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 some `ThumbnailViewHelper` functional tests\n\nThis change adds some tests for the `EXT:backend`\nThumbnailViewHelper, mainly to cover fix #102571.\n\nResolves: #103846\nRelated: #102571\nReleases: main, 12.4\nChange-Id: Id1acf6ddf6bc68c2dff0bfb7875859e07768e2af\nReviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/84283\nTested-by: Anja Leichsenring \nReviewed-by: Anja Leichsenring \nTested-by: core-ci \nReviewed-by: Christian Kuhn \nTested-by: Christian Kuhn ","shortMessageHtmlLink":"[TASK] Add some ThumbnailViewHelper functional tests"}},{"before":"b405c638d8ab70ed63c926508093cf9b8628189b","after":"ea702dbdb22d058ebd823c932e819ed027a9fc0c","ref":"refs/heads/main","pushedAt":"2024-05-21T12:48: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":"[TASK] Remove useless class doc comments\n\nSeveral classes in TYPO3 have class doc comments like\n`Class NameOfClass`. Those comments have no value\nand can therefore be removed.\n\nRegEx search:\n`/\\*\\*(\\n \\*.*)*\\n \\* Class [A-Z]`\n\nResolves: #103866\nRelated: #103862\nReleases: main\nChange-Id: Idb4ea9971d05686edb247cc6c96a03911baa19ae\nReviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/84332\nTested-by: Oliver Klee \nReviewed-by: Oliver Klee \nTested-by: Simon Schaufelberger \nReviewed-by: Simon Schaufelberger \nTested-by: Stefan Bürk \nReviewed-by: Christian Kuhn \nTested-by: Chris Müller \nTested-by: Torben Hansen \nReviewed-by: Torben Hansen \nReviewed-by: Stefan Bürk \nTested-by: Christian Kuhn \nTested-by: core-ci \nReviewed-by: Chris Müller ","shortMessageHtmlLink":"[TASK] Remove useless class doc comments"}},{"before":"6b2b38dafb712fc1d4a5c278a645e61611047dee","after":"b405c638d8ab70ed63c926508093cf9b8628189b","ref":"refs/heads/main","pushedAt":"2024-05-21T12:29:23.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 array to string conversion in BackendUtility\n\nThe value of an `label_alt` field might be\nan array, e.g. for TCA type `select` fields.\n\nThose values must not be formatted as this\nis done by `BU::getProcessedValue()` after\nresolving the correct record relation.\n\nResolves: #103838\nReleases: main, 12.4\nChange-Id: Ibfec36d2df94661fde2d82eb60bb2736205d17c3\nReviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/84334\nTested-by: core-ci \nTested-by: Oliver Bartsch \nReviewed-by: Johannes Schlier\nTested-by: Johannes Schlier\nTested-by: Stefan Bürk \nReviewed-by: Stefan Bürk \nReviewed-by: Oliver Bartsch ","shortMessageHtmlLink":"[BUGFIX] Prevent array to string conversion in BackendUtility"}},{"before":"77af53aa97af4c4684d071cf197bd90a33d46dca","after":"2235bbe338754a398d9f382bd43a6210ce28fd8e","ref":"refs/heads/12.4","pushedAt":"2024-05-21T12:27:23.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 array to string conversion in BackendUtility\n\nThe value of an `label_alt` field might be\nan array, e.g. for TCA type `select` fields.\n\nThose values must not be formatted as this\nis done by `BU::getProcessedValue()` after\nresolving the correct record relation.\n\nResolves: #103838\nReleases: main, 12.4\nChange-Id: Ibfec36d2df94661fde2d82eb60bb2736205d17c3\nReviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/84352\nReviewed-by: Oliver Bartsch \nTested-by: core-ci \nTested-by: Oliver Bartsch ","shortMessageHtmlLink":"[BUGFIX] Prevent array to string conversion in BackendUtility"}}],"hasNextPage":true,"hasPreviousPage":false,"activityType":"all","actor":null,"timePeriod":"all","sort":"DESC","perPage":30,"cursor":"djE6ks8AAAAEW_MVoQA","startCursor":null,"endCursor":null}},"title":"Activity · TYPO3-CMS/backend"}