Feature #1167
Updated by Alexander Watzinger over 4 years ago
Because of the growing number of site and user settings, settings a complete overhaul of the mechanics is are needed. Aims are much more generalized functions to ease additions and usage in code but also a better user interface presentation. Done: New web.settings database table: * id * name * value * category (new) - used in user interface * type (new) - e.g. string, boolean, int, double, url - used for presentation and validation * default (new) - shown in user interface and to mark non-default settings * profile_override (new) - to mark settings that can be overridden in the user profile To discuss: * Retrieve order from form objects (don't hard-code it How to present boolean fields, checkbox or dropdown * Layout: show values on settings overview like in views) profile?