Actions
Bug #103754
closedSets: Setting an invalid dependency discards the whole configuration
Status:
Closed
Priority:
Should have
Assignee:
-
Category:
-
Target version:
-
Start date:
2024-04-28
Due date:
% Done:
0%
Estimated time:
TYPO3 Version:
13
PHP Version:
Tags:
Complexity:
Is Regression:
Sprint Focus:
Description
When setting an invalid dependency in Configuration/Sets/MySite/config.yaml
like
name: my-vendor/my-site label: MySite dependencies: - some-vendor/unknown
the TypoScript provided by Configuration/Sets/MySite/setup.typoscript
is not available at all (resulting in No page configured for type=0.
).
My expectation would be: a dependency, which cannot be loaded, would not influence the rest of the configuration.
An error is logged, so when looking into the logfile, one can grasp the problem.
Actions