Bug #83605
closed
Form yaml files not found on multi domain site
0%
Description
On a multi domain site I have multiple root pages having it's own template / plugin settings each and it's own path for yaml form definition files. In this case the "Forms" module shows only the forms of one site, unless you specify ALL paths of all domains in 'allowedFileMounts' for each template's plugin settings across all sites.
My setup is a traditional one with the Configuration (TS) in /fileadmin/sitename/templates/Configuration/TsSetup/..., not the new way with extensions for each site template.
Updated by Björn Jacob almost 7 years ago
- Status changed from New to Needs Feedback
- Assignee set to Benno Flory
Hi Benno, we need more information to find out what's going on here :) Which TYPO3 Version are you using (full version number please)? Please also provide us your configuration. How do you register the form configuration for frontend and backend? Thanks.
Updated by Riccardo De Contardi over 6 years ago
- Status changed from Needs Feedback to Closed
- Assignee deleted (
Benno Flory)
No feedback since the last 90 days => closing this issue.
If you think that this is the wrong decision or experience the issue again and have more information about how to reproduce your problem, please reopen it or open a new issue with a reference to this one.
Thank you and best regards
Updated by Dennis Grün about 5 years ago
- TYPO3 Version changed from 8 to 9
- PHP Version changed from 7.0 to 7.2
It's still a thing. Please reopen!
We got TYPO3 9.5.9 LTS running with a multi-domain setup.
In the tree list we have 3 root pages and need to include several forms only for the second root tree.
If TS for the yaml locations is included within the sitepackages static TS for the given tree it won't get detected by the forms module altough the object browser is showing a flawless configuration.
But if you include the TS within the (according to treelist) first of the root pages the forms module detects the configuration without any problems.
So it seems the configuration for yaml location gets read only if given in the first rootpage of a tree or in the ext_typoscript_setup-file way (forms does the default this way).
In conclusion I suggest following behaviour would be nice:
- make clear within the documentation (sorry if I just didn't catch it ;D) that yamlConfigurations has to be configured globally
- alternatively make the forms module dependent on the active page tree context which would benefit multi domain systems because it would be a lot easier to manage the forms for each domain seperately