Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature request: Settings Refactor #578

Closed
3 tasks done
skrolikowski opened this issue Jun 18, 2020 · 0 comments · Fixed by fusioncms/cms#90
Closed
3 tasks done

Feature request: Settings Refactor #578

skrolikowski opened this issue Jun 18, 2020 · 0 comments · Fixed by fusioncms/cms#90
Assignees
Milestone

Comments

@skrolikowski
Copy link
Contributor

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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants