97055[TASK] Offer content type restrictions in backend layout grid editor
Commit message
Review
-
Code review CR +2 Done
- Oli Bartsch +2
- Garvin Hicking +1
- Josua Vogel +1
- Simon Schaufelberger +1
-
Verified V +2 Done
- Oli Bartsch +2
- Garvin Hicking +1
- Josua Vogel +1
- Simon Schaufelberger +1
- core-ci +1 CI
Issues 2
Files 7
- Build/Sources/TypeScript/backend/tests/grid-editor-test.ts+29 −0
- Build/Sources/TypeScript/backend/grid-editor.ts+78 −3
- typo3/sysext/backend/Classes/Form/Element/BackendLayoutWizardElement.php+11 −0
- typo3/sysext/backend/Resources/Public/JavaScript/grid-editor.js+15 −13
- typo3/sysext/backend/Tests/Functional/Form/Element/BackendLayoutWizardElementTest.phpnew+118 −0
- typo3/sysext/core/Documentation/Changelog/14.1/Feature-108623-AllowContentElementRestrictionsPerColPos.rst+2 −3
- typo3/sysext/core/Resources/Private/Language/locallang_wizards.xlf+12 −0
Review log 1114
-
Oli Bartsch uploaded patch set 1 10/23/26, 08:01
-
core-ci voted on patch set 1 V -1 10/23/26, 09:13 Core CI is not happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/112238
-
Oli Bartsch rebased onto patch set 2
V -110/24/26, 18:44 -
core-ci voted on patch set 2 V -1 10/24/26, 18:53 Core CI is not happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/112425
-
Oli Bartsch uploaded patch set 3
V -110/24/26, 19:44 -
core-ci voted on patch set 3 V +1 10/24/26, 19:53 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/112433
-
Simon Schaufelberger commented on patch set 3 10/25/26, 15:27
I've tested this and it works but in my opinion it is not very user friendly. My idea to improve it would be to use some thing similar like the tca type "group" where you have a field with available ctypes and then select the ones that you want. This could be side by side or checkboxes or whatever. -
Oli Bartsch commented on patch set 3 10/25/26, 22:16
Reply
Hey, thanks for the feedback. I assume this is admin-only functionality and may even just be used to kick-start the config. It’s important to add this missing functionality, as it was initially overlooked. Given that, and the fact that we need to backport this change, I don’t see a reasonable way to introduce new UI functionality that hasn’t been defined yet. That said, I’d be happy to see a follow-up patch in v15 that improves these fields. -
Simon Schaufelberger commented on patch set 3 10/25/26, 22:26
Reply
I just wanted to mention it that it's not very user friendly as you need to look up all the ctypes which takes time and typos can also happen. -
Simon Schaufelberger voted on patch set 3 CR +1 V +1 10/25/26, 22:26
-
Josua Vogel voted on patch set 3 CR +1 V +1 10/26/26, 16:39
-
Garvin Hicking voted on patch set 3 CR +1 V +1 10/26/26, 16:51
-
Oli Bartsch voted on patch set 3 CR +2 V +2 10/26/26, 21:25
-
Oli Bartsch merged patch set 4 10/26/26, 21:25