#89460Form module does not recognize form setups in other than 1st root-page
Description
This bug took me ages to figure out, because no error is thrown!
If you have 2 or more site-roots (for 2 or more different websites in one T3 instance), the backend form-module lists only forms defined in the first root-page. All definitions in the 2nd or following site-roots are ignored.
Example setup:
MyT3Instance - FirstSiteRoot (UID 1) - SubPage1 - SubPage2 - ... - SecondSiteRoot (UID 9) - SubPage1 - SubPage2 - ...
Inside the template of FirstSiteRoot I include the bootstrap_package, which comes with a custom form-setup.
module.tx_form.settings.yamlConfigurations.110 = EXT:bootstrap_package/Configuration/Form/Setup.yaml
Inside the template of SecondSiteRoot I include the bootstrap_package, AND have also a custom form-setup in user_mysecondsiteextension.
module.tx_form.settings.yamlConfigurations.300 = EXT:user_mysecondsiteextension/Configuration/Form/MyCustomSetup.yaml
If you select the form-module now, you’ll see ONLY the “Contact Form” defined by bootstrap_package (EXT:bootstrap_package/Resources/Private/Forms/Contact.form.yaml),
because it seems the form-module recognizes ONLY form setups from the first occurring page-root in the sitetree.
If you now move up the SecondSiteRoot BEFORE the FirstSiteRoot, the form-module lists both forms (the bootstrap_package one and EXT:user_mysecondsiteextension/Resources/Private/Form/mycustom.form.yaml)
Expected behaviour:
The form-module should look into ALL root-pages and list all forms which it finds.
Reviews 0
No change resolves or names this issue in its commit message, and no comment links one.
Related issues 2
History 11
-
Susanne Moog changed Sprint Focus Remote Sprint <span data-processor="relativetime" data-value="2019-11-17T18:24:44+00:00" > 11/17/19, 18:24 </span>
-
Mathias Brodala changed Related to #89731 <span data-processor="relativetime" data-value="2019-11-21T19:05:28+00:00" > 11/21/19, 19:05 </span>
-
Riccardo De Contardi changed parent task #89731 <span data-processor="relativetime" data-value="2019-11-21T21:00:52+00:00" > 11/21/19, 21:00 </span>
-
Mathias Brodala changed Sprint Focus
Remote Sprint<span data-processor="relativetime" data-value="2019-11-22T17:04:23+00:00" > 11/22/19, 17:04 </span> -
Björn Jacob changed Sprint Focus Remote Sprint <span data-processor="relativetime" data-value="2020-04-13T11:34:12+00:00" > 04/13/20, 11:34 </span>
-
Mathias Brodala changed Related to #87816 <span data-processor="relativetime" data-value="2020-10-26T14:57:52+00:00" > 10/26/20, 14:57 </span>
-
Björn Jacob commented and changed TYPO3 Version
911 <span data-processor="relativetime" data-value="2021-08-06T11:36:11+00:00" > 08/06/21, 11:36 </span> -
Björn Jacob changed target version Sprint Focus
Remote Sprint<span data-processor="relativetime" data-value="2021-08-06T11:36:23+00:00" > 08/06/21, 11:36 </span> -
Josua Vogel commented <span data-processor="relativetime" data-value="2026-04-21T13:14:05+00:00" > 04/21/26, 13:14 </span>
This bug report is no longer valid for the current TYPO3 main branch and v14.3.
This problem was rooted in the TypoScript-based YAML registration mechanism, which was inherently per-site. Since the backend Form module had no specific site context, it would only evaluate the TypoScript of one root page, causing forms registered via other site roots to be invisible.
In TYPO3 v14.2+, the configuration loading has been fundamentally redesigned:
Auto-discovery replaces TypoScript registration: Form YAML files are now automatically discovered from EXT:my_extension/Configuration/Form/<setname>/config.yaml across all active extensions. This mechanism is global and not bound to individual site roots.<br>TypoScript registration is deprecated: plugin.tx_form.settings.yamlConfigurations and module.tx_form.settings.yamlConfigurations trigger a deprecation warning since v14.2 and will be removed in v15.0.</setname>The FormManagerController loads configuration globally: It calls FormYamlCollector->getPaths() which returns all auto-discovered YAML paths regardless of site context.
Since the underlying architecture that caused this bug (per-site TypoScript-based YAML registration) has been replaced by a global auto-discovery mechanism, the issue can no longer occur. All extensions providing a Configuration/Form/<setname>/config.yaml will have their forms listed in the backend module, independent of site root assignment or page tree ordering.</setname>
Recommendation : Close as resolved.
-
Josua Vogel changed Related to #109412 <span data-processor="relativetime" data-value="2026-04-21T13:14:46+00:00" > 04/21/26, 13:14 </span>
-
Garvin Hicking commented and changed status
NewClosed <span data-processor="relativetime" data-value="2026-04-21T14:54:45+00:00" > 04/21/26, 14:54 </span>Closing as suggested, let me know if anyone feels differently
We will work on this (having a page tree etc.) in v12.