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

Delete flag in configuration #593

Closed
bdot opened this issue Sep 11, 2017 · 1 comment
Closed

Delete flag in configuration #593

bdot opened this issue Sep 11, 2017 · 1 comment

Comments

@bdot
Copy link

bdot commented Sep 11, 2017

- Do you want to request a feature or report a bug?

Feature request

- What is the current behavior?

Currently an user can delete any file that's available via CMS. If you have important files like settings.json and home.md, you may want to restrict deletion action to minimise the chaos.

- What is the expected behavior?

Ideally a delete on/off flag in config.yml at file/section level.

@verythorough
Copy link
Contributor

Was just coming here to file this! I think this field would make a great partner to the create field.

rpullinger added a commit to rpullinger/netlify-cms that referenced this issue Oct 17, 2017
Adds a `delete` flag to collections in `config.yml`. Defaults to
false. This is mostly for use with files to restrict users from
deleting settings files etc that available via the CMS.
Benaiah pushed a commit that referenced this issue Oct 30, 2017
Adds a `delete` flag to collections in `config.yml`; fixes
#593. Defaults to false. This is mostly for use with files to restrict
users from deleting settings files etc that available via the CMS.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants