This issue is related to #15, but goes further:
Striving for the goal to have an auditable goal, it does not come handy that admins can delete archiving runs in the GUI.
I would like to propose to think about one of these enhancements or a combination of them:
- The deletion of archives is not just controlled by the capability, there is also a kill switch in the plugin settings which is set to false by default. The kill switch setting can then also be enforced in config.php.
- The GUI offers a deletion button based on the capability, but to really delete an archive, you need to enter a secret password which is set in another $CFG setting.
This issue is related to #15, but goes further:
Striving for the goal to have an auditable goal, it does not come handy that admins can delete archiving runs in the GUI.
I would like to propose to think about one of these enhancements or a combination of them: