Feature #88330

Optional YAML imports

Added by Markus Pircher 5 months ago. Updated 30 days ago.

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

0%

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 extension Under Review 2019-08-21

History

#1 Updated by Riccardo De Contardi 30 days ago

  • Category set to System/Bootstrap/Configuration

#2 Updated by Riccardo De Contardi 30 days ago

  • Related to Bug #88993: Siteconfig import or symlink breaks TYPO3 if the sourcepath is an deactivated extension added

Also available in: Atom PDF