[TASK] Streamline handling of TypoScript form overrides
Each form definition loaded by FormPersistenceManager can be overridden by TypoScript. When forms are to be rendered by using the FormFrontend controller (which should be the default way), TypoScript overrides are applied correctly. In contrast, when using alternative ways of rendering, it's currently impossible to override form definitions via TypoScript. In order to streamline the form definition management and therefore allow a centralized way of TypoScript overriding, the appropriate code has been moved from the FormFrontend controller to FormPersistenceManager. This way every rendering mechanism can now make use of the FormPersistenceManager and expect a streamlined form definition. Resolves: #92408 Releases: main Change-Id: Ib5c132bcef2356c6d66d617f817654c2f6d0e440 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/73678 Reviewed-by:Björn Jacob <bjoern.jacob@tritum.de> Reviewed-by:
waldhacker <hello@waldhacker.dev> Tested-by:
core-ci <typo3@b13.com> Tested-by:
Björn Jacob <bjoern.jacob@tritum.de> Tested-by:
waldhacker <hello@waldhacker.dev>
Showing
- typo3/sysext/form/Classes/Controller/FormFrontendController.php 0 additions, 28 deletions...sysext/form/Classes/Controller/FormFrontendController.php
- typo3/sysext/form/Classes/Mvc/Persistence/FormPersistenceManager.php 32 additions, 4 deletions...t/form/Classes/Mvc/Persistence/FormPersistenceManager.php
- typo3/sysext/form/Tests/Unit/Controller/FormFrontendControllerTest.php 0 additions, 130 deletions...form/Tests/Unit/Controller/FormFrontendControllerTest.php
- typo3/sysext/form/Tests/Unit/Mvc/Persistence/FormPersistenceManagerTest.php 135 additions, 0 deletions...Tests/Unit/Mvc/Persistence/FormPersistenceManagerTest.php
Please register or sign in to comment