#109412Auto-discovery of EXT:form YAML configurations
Description
YAML configuration files for the TYPO3 Form Framework are currently registered manually via TypoScript in ext_localconf.php or setup.typoscript, requiring separate registrations for frontend and backend. This is error-prone, uses TypoScript as a mere file path transport (an abuse of the mechanism).
The proposal is to replace this with a convention-based directory auto-discovery, modelled after the Site Sets pattern.
*Proposed Solution*
Introduce auto-discovery of form YAML configuration files from the directory EXT:*/Configuration/Form/ across all active extensions.
EXT:my_extension/
Configuration/
Form/
MyFormSet/ ← arbitrary sub-directory name
config.yaml ← required: set metadata
setup.yaml ← optional: form config (FE + BE)
An extension may ship multiple sets in separate sub-directories.
config.yaml — Set Metadata
# Unique identifier following vendor/name convention
name: my-vendor/my-form-set
# Human-readable label for diagnostic output
label: 'My Custom Form Set'
# Merge priority: lower = loaded first (acts as base).
# EXT:form core set uses priority 10. Extension sets default to 100.
priority: 200
*Merge Order*
Files are sorted by ascending priority. Each file is merged on top of the previous one using array_replace_recursive, identical to the former TypoScript-based behaviour.
*Disable Mechanism*
Because all sets from all active extensions are loaded automatically, a global opt-out is available:
$GLOBALS['TYPO3_CONF_VARS']['EXTENSIONS']['form']['disabledSets'][]
= 'some-vendor/conflicting-set';
Matching is done against the name field in config.yaml, not the directory name.
Reviews 5
- main 94292[TASK] Remove stale docblock ext:form ConfigurationManager
- main 93410[FEATURE] Introduce auto-discovery for EXT:form YAML configurations
- main 93684[DOCS] Clarify yamlSettingsOverrides support in form auto-discovery changelog
- main 93685[TASK] Add site set settings for EXT:form template paths
- main 93482[DOCS] Readd removed anchors to form yaml documentation
Related issues 3
History 517
-
Gerrit Code Review pushed patch set 1 for main to change 93410 status
NewUnder Review <span data-processor="relativetime" data-value="2026-03-27T20:49:01+00:00" > 03/27/26, 20:49 </span> -
Gerrit Code Review pushed patch set 2 for main to change 93410 <span data-processor="relativetime" data-value="2026-03-27T20:51:37+00:00" > 03/27/26, 20:51 </span>
-
Gerrit Code Review pushed patch set 3 for main to change 93410 <span data-processor="relativetime" data-value="2026-03-27T20:52:13+00:00" > 03/27/26, 20:52 </span>
-
Gerrit Code Review pushed patch set 4 for main to change 93410 <span data-processor="relativetime" data-value="2026-03-29T14:34:59+00:00" > 03/29/26, 14:34 </span>
-
Gerrit Code Review pushed patch set 5 for main to change 93410 <span data-processor="relativetime" data-value="2026-03-29T16:10:18+00:00" > 03/29/26, 16:10 </span>
-
Gerrit Code Review pushed patch set 6 for main to change 93410 <span data-processor="relativetime" data-value="2026-03-29T16:28:37+00:00" > 03/29/26, 16:28 </span>
-
Gerrit Code Review pushed patch set 7 for main to change 93410 <span data-processor="relativetime" data-value="2026-03-30T19:52:56+00:00" > 03/30/26, 19:52 </span>
-
Gerrit Code Review pushed patch set 8 for main to change 93410 <span data-processor="relativetime" data-value="2026-03-30T19:54:47+00:00" > 03/30/26, 19:54 </span>
-
Gerrit Code Review pushed patch set 9 for main to change 93410 <span data-processor="relativetime" data-value="2026-03-30T19:55:05+00:00" > 03/30/26, 19:55 </span>
-
Gerrit Code Review pushed patch set 10 for main to change 93410 <span data-processor="relativetime" data-value="2026-03-31T05:31:33+00:00" > 03/31/26, 05:31 </span>
-
Gerrit Code Review pushed patch set 11 for main to change 93410 <span data-processor="relativetime" data-value="2026-03-31T05:49:33+00:00" > 03/31/26, 05:49 </span>
-
Gerrit Code Review pushed patch set 12 for main to change 93410 <span data-processor="relativetime" data-value="2026-03-31T06:47:49+00:00" > 03/31/26, 06:47 </span>
-
Josua Vogel commented and changed status
Under ReviewResolved done0 %100 % <span data-processor="relativetime" data-value="2026-03-31T07:10:10+00:00" > 03/31/26, 07:10 </span> -
Benni Mack changed status
ResolvedClosed <span data-processor="relativetime" data-value="2026-03-31T08:09:56+00:00" > 03/31/26, 08:09 </span> -
Benjamin Franzke changed Related to #109432 <span data-processor="relativetime" data-value="2026-03-31T09:07:35+00:00" > 03/31/26, 09:07 </span>
-
Josua Vogel changed Related to #89460 <span data-processor="relativetime" data-value="2026-04-21T13:14:46+00:00" > 04/21/26, 13:14 </span>
-
Christian Kuhn changed Related to #109978 <span data-processor="relativetime" data-value="2026-06-03T10:50:22+00:00" > 06/03/26, 10:50 </span>
Applied in changeset commit:0fa5858df7e772b454edef769d0da131e376501e.