Created by: Matt Wilcox (mattw@viewcreative.co.uk) 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.
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.