Summary:
Introduce a functionality to log files identified for deletion during Defender scans before deleting them, accessible via the WPMUDEV dashboard.
Description:
During the process of cleaning a site with Defender, it’s possible to inadvertently delete essential files, potentially rendering the site inoperable. To mitigate the risk of such critical errors and enhance user awareness, I propose the implementation of a logging feature. This feature would automatically create a log of all files flagged for deletion by Defender prior to the actual deletion process.
Key Feature:
Pre-Deletion Log Creation: Automatically generate a detailed log of files marked for deletion before deleting them.
Accessibility:
The logs should be accessible through the WPMUDEV dashboard, rather than being stored locally. This would ensure that users can review deletion logs from any location and without the need to access their local site environment, which might be compromised or unreachable.
Use Case:
In a scenario where a user (like myself) inadvertently selects and deletes essential files, leading to site dysfunction, this feature would allow them to identify exactly which files were deleted. This can significantly aid in recovery processes, whether by manual restoration or through support services.
Benefits:
Enhances safety and oversight during the cleanup process.
Helps prevent accidental deletion of critical files.
Provides a reliable recovery reference point in cases where deletions impact site functionality.
This feature would not only add an extra layer of security but also provide peace of mind to users managing their website security through Defender and WPMUDEV.
