---
title: "Feature: #109412 - Auto-discovery of form YAML configurations"
manual: "TYPO3 Core Changelog"
version: "main"
permalink: "https://docs.typo3.org/permalink/changelog:feature-109412-1742000001"
source: "Changelog/14.2/Feature-109412-FormYamlAutoDiscovery.rst"
typo3-version: "14.2"
typo3-major: 14
type: "feature"
issue: 109412
forge: "https://forge.typo3.org/issues/109412"
tags: ["YAML", "Frontend", "Backend", "ext:form"]
rendered: "2026-09-23T15:30:34+00:00"
---

# Feature: #109412 - Auto-discovery of form YAML configurations {#feature-109412-1742000001}

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

## Description {#description}

TYPO3 Form Framework can now discover YAML configuration files
from every active extension — with no PHP or TypoScript registration required.

The mechanism mirrors how [Site Sets](https://docs.typo3.org/m/typo3/reference-coreapi/main/en-us/ApiOverview/SiteHandling/SiteSets/Index.html#site-sets) work:
each extension may provide one or more *form sets* by placing files in a
conventional directory layout. TYPO3 scans all the active extensions and collects
every form set it finds, powered by a Symfony service configurator
(`FormYamlCollectorConfigurator`) that runs transparently when the form
service is first resolved.

### Directory layout {#directory-layout}

```none
EXT:my_extension/
  Configuration/
    Form/
      MyFormSet/
        config.yaml
```

The subdirectory name (`MyFormSet`) is arbitrary. An extension may ship
multiple sets in separate subdirectories.

### The `config.yaml` {#the-file-config-yaml}

Contains both the set metadata and the form configuration in a single
file. The metadata keys (`name`, `label`, `priority`) are reserved; all
other keys are treated as form configuration (prototype definitions, form
elements, validators, finishers, rendering options, etc.).

**EXT:my_extension/Configuration/Form/MyFormSet/config.yaml**

```yaml
# Unique identifier, vendor/name convention (like composer package names)
name: my-vendor/my-form-set

# Human-readable label for diagnostic output
label: 'My Custom Form Set'

# Load order: lower values are loaded first and act as base configuration.
# Extension sets should use a value > 10 to be merged on top of the
# TYPO3 core base set (typo3/form-base, priority: 10).
# Default: 100
priority: 200

# Form configuration follows directly below the metadata:
persistenceManager:
  allowedExtensionPaths:
    10: 'EXT:my_extension/Resources/Private/Forms/'
```

### Priority and merge order {#priority-and-merge-order}

Sets are sorted by ascending `priority` (lower = loaded first = acts as base,
higher = override). Each set's configuration is merged on top of the previous
one using `array_replace_recursive()`. This is identical to how the former TypoScript
mechanism worked.

### Migration from TypoScript registration {#migration-from-typoscript-registration}

Before TYPO3 v14.2, YAML files had to be registered explicitly via TypoScript:

**EXT:my_extension/Configuration/TypoScript/setup.typoscript**

```typoscript
plugin.tx_form.settings.yamlConfigurations {
    1732785702 = EXT:my_extension/Configuration/Form/MySetup.yaml
}
```

```typoscript
# Backend had to be registered separately:
module.tx_form.settings.yamlConfigurations {
    1732785703 = EXT:my_extension/Configuration/Form/MySetup.yaml
}
```

This registration mechanism has been deprecated and will be removed in
TYPO3 v15.0. See [Deprecation-109412](https://docs.typo3.org/permalink/changelog:deprecation-109412-1742000001)
for details.

After the migration:

1.  Create the directory `EXT:my_extension/Configuration/Form/MySet/`.
1.  Create `config.yaml` with `name`, optionally `priority`, and the
    form configuration in the same file.
1.  Remove TypoScript registrations from `setup.typoscript`.

**EXT:my_extension/Configuration/Form/MySet/config.yaml**

```yaml
name: my-vendor/my-form-set
label: 'My Custom Form Set'
priority: 200

# Form configuration (formerly your MySetup.yaml content) goes here:
prototypes:
  standard:
    formElementsDefinition:
      ...
```

### Disabling a form set {#disabling-a-form-set}

Because sets from active extensions are loaded automatically, a
mechanism exists to opt out of specific sets without modifying the
extension that provides them.

To disable a set, add its declared `name` (from `config.yaml`) to
`$GLOBALS['TYPO3_CONF_VARS']['EXTENSIONS']['form']['disabledSets']`
in `ext_localconf.php` or `config/system/settings.php`:

**EXT:my_extension/ext_localconf.php**

```php
// Disable a third-party form set that conflicts with the site configuration:
$GLOBALS['TYPO3_CONF_VARS']['EXTENSIONS']['form']['disabledSets'][]
    = 'some-vendor/conflicting-set';
```

> [!NOTE]
> Disabling the core set `typo3/form-base` will break form rendering
> entirely. Only disable it if you provide a full replacement set with
> equivalent configuration.

The matching is done against the `name` field in `config.yaml`,
**not** against the directory name, so renaming the set directory does not
break an existing disable list.

### EXT:form base set {#ext-form-base-set}

The TYPO3 Form Framework ships its own base set at
`EXT:form/Configuration/Form/Base/` (`typo3/form-base`, priority 10).
All validators, form elements, finishers, and shared rendering configuration
are defined in `EXT:form/Configuration/Form/Base/config.yaml`.

### Site set settings for template paths {#site-set-settings-for-template-paths}

The site set `typo3/form` provides four settings to override Fluid template
paths and translation files.

-   **form.templates.templateRootPath**

    -   *Type:* string
    -   *Default:* (empty)

    Override the default Fluid template path for form element rendering.

-   **form.templates.partialRootPath**

    -   *Type:* string
    -   *Default:* (empty)

    Override the default Fluid partial path for form element rendering.

-   **form.templates.layoutRootPath**

    -   *Type:* string
    -   *Default:* (empty)

    Override the default Fluid layout path for form element rendering.

-   **form.translation.translationFile**

    -   *Type:* string
    -   *Default:* (empty)

    Add an additional XLF translation file for form element labels.

Override the template paths in the site configuration:

**config/sites/my-site/settings.yaml**

```yaml
form.templates.templateRootPath: EXT:my_sitepackage/Resources/Private/Templates/Form/Frontend/
form.templates.partialRootPath: EXT:my_sitepackage/Resources/Private/Partials/Form/Frontend/
form.templates.layoutRootPath: EXT:my_sitepackage/Resources/Private/Layouts/Form/Frontend/
form.translation.translationFile: EXT:my_sitepackage/Resources/Private/Language/Form/locallang.xlf
```

## Impact {#impact}

Extensions that have a `config.yaml` in
`Configuration/Form/<SetName>/` will have their configuration
automatically loaded without any additional registration.

Integrators who include the `typo3/form` site set can additionally override
form template paths, partial paths, layout paths and translation files through
site settings — without touching YAML prototype configuration or TypoScript
`yamlSettingsOverrides`.