Modify Wordpress integrity checker for security optimisations
So if I create a new Wordpress installation and then I make certain minor security adjustments that are highly recommended in cybersecurity forums, then I will get errors that it is broken through Plesk. I will then forever more be warned that it is broken in Plesk (not in Wordpress) on account of absence of those files, which (as I say) is a deliberate choice I made).
Ideally this would be modified in the install process (e.g. question: "Would you like to remove the readme and license files after installation?" (then explain why it is important to in a hover box), but that might be harder, and the original option might just be quicker/easier/leave the risk to the user to address. Here's an article on this matter (just the first one that I found, easy to understand, demonstrates the whole issue), just to give you clarity on what I mean:
https://wordpress.2bearstudio.com/wordpress-security-tip-delete-readme-after-installation/
Alternatively, would it be possible to offer the chance to 'hide' or 'accept' certain deliberate modifications that are made, like this, as it is pretty annoying to have the constant notification that it is 'broken' when, to my mind, removing inherent vulnerabilities makes it 'not fixed'.
There are other things like this, but not sure that they are so regularly used (for instance, I got through themes and remove their display information if someone wants to read the theme names, version numbers, designers, etc.) and much more critical things that I'll put under a different category.
Jonathan Jewell
shared this idea
Thank you for your idea! We will consider this functionality in upcoming releases if it will be popular.
Everyone, please continue voting for this feature if you consider it important.
-- PD