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.
Updated by Georg Ringer 6 months ago
- Status changed from New to Closed
closing issue as duplicate of #103558
Updated by Georg Ringer 6 months ago
- Is duplicate of Task #103558: Add warning to site module in case set dependencies are broken added
Actions