Feature #88330

Optional YAML imports

Added by Markus Pircher over 2 years ago. Updated almost 2 years ago.

Status:
Closed
Priority:
Must have
Assignee:
-
Category:
System/Bootstrap/Configuration
Target version:
-
Start date:
2019-05-10
Due date:
% Done:

0%

Estimated time:
PHP Version:
Tags:
Complexity:
Sprint Focus:

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

Related issues

Related to TYPO3 Core - Bug #88993: Siteconfig import or symlink breaks TYPO3 if the sourcepath is an deactivated extensionClosedJosef Glatz2019-08-21

Actions

Also available in: Atom PDF