Implementation of the setting to enable secure deletion of pages #1752
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
This is pretty cool! Good idea |
|
Yes, I got the idea after I accidentally lost some data, as the button was the same color as cancel and there was no turning back this was a solution that solved |
|
Another thing that could be done is to have a specific permission to create, edit and delete pages in admin, so that would create another layer of security. |
|
There are already separate permissions for different page actions built into the upcoming Flex pages. :) |
mahagr
approved these changes
Sep 17, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
To avoid accidental deletion, I implemented a secure deletion system in which the user has to type the word DELETE into a text field for the confirm deletion button to be enabled. By default this plugin setting is disabled.