Feature #88330

Optional YAML imports

Added by Markus Pircher over 1 year ago. Updated 8 months ago.

Status:
Closed
Priority:
Must 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 Closed 2019-08-21

History

#1 Updated by Riccardo De Contardi about 1 year ago

  • Category set to System/Bootstrap/Configuration

#2 Updated by Riccardo De Contardi about 1 year ago

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

#3 Updated by Gerrit Code Review 11 months 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

#4 Updated by Kevin Ditscheid 11 months ago

  • Priority changed from Should have to Must have

I added an option to ignore errors in the YAML import, see the applied patch

#5 Updated by Daniel Goerz 8 months ago

  • Status changed from Under Review to Closed

Will be solved with #88993, please continue over there.

Also available in: Atom PDF