#106596Remove legacy form templates
Description
The old form templates were deprecated with TYPO3 12.0, and planned to be removed with v13: https://docs.typo3.org/c/typo3/cms-core/main/en-us/Changelog/12.0/Deprecation-95456-IntroduceBootstrap5CompatibleAndAccessibleTemplates.html
But TYPO3 v13 and the current main branch still use templateVariant: version1 as the default.
The newer templates, which are based on Bootstrap 5, can be customized more easily because of the increased use of YAML options for class names.
However, in the current state, form configuration with templateVariant: version2 is unnecessarily complex: we need to set custom properties via a form variant for each form element , due to the already existing variants in the TYPO3 core.
prototypes:
standard:
formElementsDefinition:
Form:
renderingOptions:
templateVariant: version2
variants:
– identifier: template-variant
renderingOptions:
fieldProperties:
descriptionClassAttribute: c-form__helptext
requiredMarkClassAttribute: required
visuallyHiddenClassAttribute: u-hidden-visually
formNavigation:
navigationWrapperClassAttribute: ~
navigationClassAttribute: ~
btnPreviousClassAttribute: ‘c-btn c-btn—secondary’
btnNextClassAttribute: ‘c-btn c-btn—secondary’
btnSubmitClassAttribute: ‘c-btn c-btn—secondary’
Text:
variants:
– identifier: template-variant
properties:
containerClassAttribute: c-form__item
elementClassAttribute: ~
elementErrorClassAttribute: ~
labelClassAttribute: c-form__label
I would recommend to delete the legacy templates and remove the `templateVariant` option altogether, so that the need for form variants on each form element becomes obsolete.
Reviews 4
Related issues 2
History 610
-
Sebastian Klein changed Related to #97916 <span data-processor="relativetime" data-value="2025-04-22T13:16:25+00:00" > 04/22/25, 13:16 </span>
-
Sebastian Klein commented <span data-processor="relativetime" data-value="2025-04-29T06:22:30+00:00" > 04/29/25, 06:22 </span>
Georg Ringer wrote in #note-2:
> wanna do a patch? that would be great!Yes, I will prepare a patch and check the migration steps for the changelog file.
-
Gerrit Code Review pushed patch set 1 for main to change 89355 status
NewUnder Review <span data-processor="relativetime" data-value="2025-05-10T17:24:05+00:00" > 05/10/25, 17:24 </span> -
Gerrit Code Review pushed patch set 2 for main to change 89355 <span data-processor="relativetime" data-value="2025-05-12T15:18:47+00:00" > 05/12/25, 15:18 </span>
-
Gerrit Code Review pushed patch set 3 for main to change 89355 <span data-processor="relativetime" data-value="2025-05-22T18:16:40+00:00" > 05/22/25, 18:16 </span>
-
Gerrit Code Review pushed patch set 4 for main to change 89355 <span data-processor="relativetime" data-value="2025-05-23T08:04:27+00:00" > 05/23/25, 08:04 </span>
-
Sebastian Klein commented and changed status
Under ReviewResolved done0 %100 % <span data-processor="relativetime" data-value="2025-05-26T06:10:10+00:00" > 05/26/25, 06:10 </span>Applied in changeset commit:6f445a5115e312f85a062b07a7272d83147b86ae.
-
Chris Müller changed Related to #107779 <span data-processor="relativetime" data-value="2025-10-18T14:10:37+00:00" > 10/18/25, 14:10 </span>
-
Benni Mack changed status
ResolvedClosed <span data-processor="relativetime" data-value="2025-12-02T14:21:17+00:00" > 12/02/25, 14:21 </span>
wanna do a patch? that would be great!