---
title: "Breaking: #106596 - Remove legacy form templates"
manual: "TYPO3 Core Changelog"
version: "main"
permalink: "https://docs.typo3.org/permalink/changelog:breaking-106596-1746896335"
source: "Changelog/14.0/Breaking-106596-RemoveLegacyFormTemplates.rst"
typo3-version: "14.0"
typo3-major: 14
type: "breaking"
issue: 106596
forge: "https://forge.typo3.org/issues/106596"
tags: ["Frontend", "YAML", "NotScanned", "ext:form"]
rendered: "2026-09-23T15:24:25+00:00"
---

# Breaking: #106596 - Remove legacy form templates {#breaking-106596-1746896335}

See [forge#106596](https://forge.typo3.org/issues/106596)

## Description {#description}

In earlier TYPO3 versions, the Form Framework provided two template variants
for frontend rendering:

-   The initial, legacy templates in
    `EXT:form/Resources/Private/Frontend/Templates` and
    `EXT:form/Resources/Private/Frontend/Partials`, which were deprecated
    in [forge#95456](https://forge.typo3.org/issues/95456)
-   The newer, Bootstrap 5 compatible and accessible templates in
    `EXT:form/Resources/Private/FrontendVersion2/Templates` and
    `EXT:form/Resources/Private/FrontendVersion2/Partials`, introduced
    with [forge#94868](https://forge.typo3.org/issues/94868)

The legacy form templates have now been removed. The rendering option
`templateVariant`, which toggled the template and form configuration
variant, has been removed as well.

The newer template variants have been moved to the original file paths of the
legacy templates.

## Impact {#impact}

The removal of the legacy templates and the `templateVariant`
configuration option simplifies the Form Framework rendering logic.

Developers no longer need to choose between multiple template variants,
reducing complexity and improving maintainability. Projects already using the
newer templates benefit from a cleaner configuration and a unified rendering
approach.

## Affected installations {#affected-installations}

All TYPO3 installations using the Form Framework are affected.

## Migration {#migration}

If you still rely on the legacy templates, you must migrate your templates and
partials to the structure of the newer templates.

Websites that use `templateVariant: version2` can simplify their form
configuration. Variants with the condition
`'getRootFormProperty("renderingOptions.templateVariant") == "version2"'`
are no longer necessary and can be removed.

**Before:**

```yaml
prototypes:
  standard:
    formElementsDefinition:
      Text:
        variants:
          -
            identifier: template-variant
            condition: 'getRootFormProperty("renderingOptions.templateVariant") == "version2"'
            properties:
              containerClassAttribute: 'form-element form-element-text mb-3'
              elementClassAttribute: form-control
              elementErrorClassAttribute: ~
              labelClassAttribute: form-label
```

**After:**

```yaml
prototypes:
  standard:
    formElementsDefinition:
      Text:
        properties:
          containerClassAttribute: 'form-element form-element-text mb-3'
          elementClassAttribute: form-control
          elementErrorClassAttribute: ~
          labelClassAttribute: form-label
```