Skip to content

Feature request: Settings Refactor #578

@skrolikowski

Description

@skrolikowski

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)
  • I have searched for existing issues and to the best of my knowledge this is not a duplicate

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions