#105976Error shown when depend on a site settings definition which has only readonly settings
Description
When using the following scenario:
A site package site set depends on another site set which defines a settings.definition.yaml file. In this settings.definition.file there are two settings, both are readonly. Additionally, the site package site set defines also a settings.definition.yaml file which also only readonly settings:
EXT:site
dependencies:
- my-vendor/some-ext
settings.definitions.yaml:
settings:
site.some_setting:
label: "Some setting"
type: "string"
readonly: "true"
default: "Some value"
EXT:some_ext
settings.definitions.yaml:
settings:
some_set.some_setting:
label: "Some setting"
type: "string"
readonly: "true"
default: "Some value"
This results in the following error in the backend (Site Management > Settings):
This site depends on invalid site sets Site set 'my-vendor/site' is disabled: Missing dependency 'my-vendor/some-ext'
I would expect that the settings of some-ext are displayed correctly (as readonly) – apart from that the error message is misleading. This also happens when only one setting is defined as readonly and the others are writable.
If I remove the settings.definitions.yaml from some_ext, everything works, the readonly settings are correctly displayed readonly.
Background: I would like to use the settings definitions as a central place to define values (like with TypoScript constants previously), but they must not be overridden via the GUI.
Reviews 0
No change resolves or names this issue in its commit message, and no comment links one.
History 3
-
Chris Müller changed description <span data-processor="relativetime" data-value="2025-01-22T07:40:47+00:00" > 01/22/25, 07:40 </span>
-
Chris Müller changed description <span data-processor="relativetime" data-value="2025-01-22T08:08:54+00:00" > 01/22/25, 08:08 </span>
-
Oliver Bartsch commented and changed status
NewClosed <span data-processor="relativetime" data-value="2026-11-16T16:43:20+00:00" > 11/16/26, 16:43 </span>
Hey,
I went through this, and the readonly flag itself is not the problem. “Missing dependency ‘my-vendor/some-ext’” means the some-ext set could not be loaded at all, so it never reached the registry. Readonly does not affect loading. A dependency set with
readonly: trueworks fine and is shown read-only in the editor.In the example you posted, the settings use
readonly: "true". The quotes make this a string. The definition expects a real boolean, so the whole settings.definitions.yaml of that set is rejected, and the set depending on it is reported as having a missing dependency. Please use the unquoted YAML boolean:settings: some_set.some_setting: label: 'Some setting' type: string readonly: true default: 'Some value'(Please also check the indentation: in the snippet,
label,typeetc. are on the same level as the setting key.)You are right that the message was hard to trace back. This was improved with “[TASK] Refine site set error handling” (#105793, #105792, in main and 13.4). Since then, every invalid set and its exact reason (e.g. “Invalid type: readonly”) is listed in the Site Management overview and by
vendor/bin/typo3 site:sets:list. If you still see the problem with a recent 13.4 release andreadonly: true, please post the output ofsite:sets:listand I’ll reopen.For now, I’m closing this, since it comes down to configuration and the error reporting has already been improved.
Cheers, Oli