Feature #88330
closed
Optional YAML imports
0%
Description
Currently an exception is thrown if a YAML file is not found.
In some cases it may be that a YAML file is not available, or only available if a extension installed.
As example if the new Site configuration with the routeEnhancers.
An extension could have its own default route configuration. but if the extension is not installed and the site configuration has a import for this extension, the exception broke the entire TYPO3 installation.
My suggestion would be to optionally make imports optional, like:
imports:
-
resource: "EXT:my_ext/Configuration/Routes/Default.yaml"
optional: 1
Updated by Riccardo De Contardi over 4 years ago
- Category set to System/Bootstrap/Configuration
Updated by Riccardo De Contardi over 4 years ago
- Related to Bug #88993: Siteconfig import or symlink breaks TYPO3 if the sourcepath is an deactivated extension added
Updated by Gerrit Code Review over 4 years ago
- Status changed from New to Under Review
Patch set 1 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/62617
Updated by Kevin Ditscheid over 4 years ago
- Priority changed from Should have to Must have
I added an option to ignore errors in the YAML import, see the applied patch
Updated by Daniel Goerz about 4 years ago
- Status changed from Under Review to Closed
Will be solved with #88993, please continue over there.