#103034Unified Settings API
Description
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.
Reviews 3
- main 85750[BUGFIX] Ensure proper loading order of EXT:seo and EXT:dashboard
- 12.4 85768[BUGFIX] Ensure proper loading order of EXT:seo and EXT:dashboard
- main 83696[TASK] Use site sets in EXT:styleguide
Fix this issue
Start the commit message of your patch with this. Add what the patch does, and the versions it goes to in "Releases:". The changes above were merged or abandoned: read them before you start. How to create a patch
- Commit message
-
[TASK] Unified Settings API Resolves: #103034 Releases: main
Subtasks 16
- Epic #103630Site sets: Composable (sub)set's of site configuration, shippable in extensions
- Bug #103732Styleguide FE tree generator ignores option 'with site settings'
- Task #104794Site Settings Editor
- Task #104831Allow translations of site settings labels and description
- Task #104840Auto-register set labels from labels.xlf
- Bug #106894Site settings do not support storage of subkeys, if the dot-seprated setting exists as a key.
- Task #106953Add page type to settings
- Feature #107035Introduce System Settings API
- Feature #107036Support per-instance settings for Dashboard Widgets
- Task #107037Setting types need to be parameterizable
- Bug #107038Custom settings types are not loaded in settings editor
- Task #107039Add settings type helpers that ease integration of repeating element patterns
- Task #107040Streamline array vs object handling in settings type values
- Bug #107091Settings input fields lose focus on value change via keyboard
- Task #107132Add url type to settings
- Bug #107169settings api: enum not working for int types, only type string