Epic #103034
Updated by Benni Mack 3 months ago
We should have a new and unified Settings API.
For Content, we have TCA and FormEngine / DataHandler, but for settings, this is all inconsistent and not unified:
* Extension Configuration API ("cryptic syntax")
* TypoScript Constants API ("cryptic syntax")
* Site Settings API (no visual API yet)
* User Settings API (custom API, could be moved into a TCA.be_users.settings custom field)
* "System-wide" settings / global settings (Install tool via DefaultConfiguration.yaml), not extendible
Settings API means the definition of a setting, by various kinds to be configurable, and stored depending on the actual level.
The location where it is persisted is not scope of this epic currently, however the definition, the validation, the usage and the UI is part of it.
We need a new API which superseds at least the first three parts in order to move forward.
For Site Settings, it is a must-have to include site setting presets from extensions and to override them.
As a future step: Dashboard Widgets need to be able to use Settings as well.