Project

General

Profile

Actions

Bug #105792

open

Empty settings.yaml should not cause error

Added by Lina Wolf about 1 month ago.

Status:
New
Priority:
Should have
Assignee:
-
Category:
Site Handling, Site Sets & Routing
Target version:
-
Start date:
2024-12-09
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
13
PHP Version:
8.2
Tags:
Complexity:
Is Regression:
Sprint Focus:

Description

If you first hat settings and then removed them for some reason you might end up with an empty settings.yaml file

Also site package builders might want to create the file with a comment so that integrators know where to put there settings.

Currently an empty settings.yaml file however causes error:

This site depends on invalid site sets
Site set 'xxx/site-package' is disabled due to invalid settings

And makes the set disappear from the selector in the site configuration editor

No data to display

Actions

Also available in: Atom PDF