You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Currently the fields that make up the Settings interfaces use regular input fields. This allowed a standardized way of configuring settings. We'd like to investigate a more streamlined way of creating customizable settings using our existing Fieldtypes.
Describe the solution you'd like
Refactor how settings are saved using Fieldtypes.
Setting fields should be imported and treated as if they are a Fieldset.
Fields for settings will be stored in a separate table.
Setting values will be stored in a separate table, each value in it's own column with associated data type.
Feature request checklist
This is a single feature (i.e. not a re-write of the entire CMS)
The title starts with "Feature request: " and is followed by a clear feature name (Ex: Feature request: add konami code to control panel)
Is your feature request related to a problem? Please describe.
Currently the fields that make up the Settings interfaces use regular input fields. This allowed a standardized way of configuring settings. We'd like to investigate a more streamlined way of creating customizable settings using our existing Fieldtypes.
Describe the solution you'd like
Refactor how settings are saved using Fieldtypes.
Feature request checklist
Feature request: add konami code to control panel
)The text was updated successfully, but these errors were encountered: