Epic #89107
Updated by Susanne Moog over 4 years ago
Site settings should provide a possibility to configure site-wide settings (for example storage PIDs) for use in all contexts. Prerequisites: * Existing site Starting point: Sites module * A site has a new button "edit settings" to reach the site settings module * The site settings module has the same interface as the constant editor / extension configuration (can be refactored to a different syntax at a later point - we want to keep settings in the same format and switch to yaml for constants and site settings in one step, providing a fallback to the legacy syntax; as step one: make reusing of constant editor files/config possible) * The site settings get read and written to a file called "settings.yaml" "settings.typoscript" next to the corresponding sites config.yaml (similar to how constants are saved) * The site settings are readable / accessible via the sites object (and in all cases where that is accessible) * The site settings interface is build from various Settings.typoscript configuration files provided by extensions in Configuration/Site/Settings.typoscript (these contain the interface definitions - see constants for syntax) Further steps: * Make site settings language aware * Add possibility to restrict an extensions site settings to specific sites only (question to be discussed: should we implement a general possibility to load extensions based on the current site?) Additional Info: * Benjamin Kott is working on a revamp of the constant editor configuration format / gui - which can then be used for both site settings and constants