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
Created by: Matt Wilcox ([email protected]) on 2015/11/12 11:03:22 +0000
Votes at time of UserVoice import: 9
We’ve just had a client manage to wipe out a few hundred Entries from three of their Craft websites - and while Craft was doing the right thing, and it was user error which was the problem, I think there’s a way to safeguard against this.
They’d had a member of staff leave, and deleted her user account. They appear to have also deleted every single entry that user owned - either because that’s the default action and they didn’t read the dialogue properly, or because they read it and didn’t understand it, and opted to delete rather than re-assign owner.
Should Craft do a database backup before such a potentially catastrophically large data-loss operation, in the same way it does when upgrading itself?
Clients should know better, and their host ought to have been running backups - but they weren’t.
This seems like a somewhat sensible precaution for that type of action.
This discussion was converted from issue #936 on June 22, 2021 06:17.
Heading
Bold
Italic
Quote
Code
Link
Numbered list
Unordered list
Task list
Attach files
Mention
Reference
Menu
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
We’ve just had a client manage to wipe out a few hundred Entries from three of their Craft websites - and while Craft was doing the right thing, and it was user error which was the problem, I think there’s a way to safeguard against this.
They’d had a member of staff leave, and deleted her user account. They appear to have also deleted every single entry that user owned - either because that’s the default action and they didn’t read the dialogue properly, or because they read it and didn’t understand it, and opted to delete rather than re-assign owner.
Should Craft do a database backup before such a potentially catastrophically large data-loss operation, in the same way it does when upgrading itself?
Clients should know better, and their host ought to have been running backups - but they weren’t.
This seems like a somewhat sensible precaution for that type of action.
Beta Was this translation helpful? Give feedback.
All reactions