Facebook
TwitterRecently, Plesk added a vulnerability status feature to the WordPress Toolkit, which is a great step forward. However, both the vulnerability status and the protection status are currently accessed through the same link, making it harder to quickly find the protection details.
It would benefit users, especially those less familiar with these features, if Plesk were to separate these into two distinct links. This way, the protection status would be more visible and easier to access, helping users stay informed about the security of their WordPress installations without extra steps. Clearer access to these statuses could also address the concern about the perceived gaps in protection, such as with xmlrpc.php, making Plesk's security offerings feel more complete and transparent.
I've created a corresponding UserVoice request:
It would benefit users, especially those less familiar with these features, if Plesk were to separate these into two distinct links. This way, the protection status would be more visible and easier to access, helping users stay informed about the security of their WordPress installations without extra steps. Clearer access to these statuses could also address the concern about the perceived gaps in protection, such as with xmlrpc.php, making Plesk's security offerings feel more complete and transparent.
I've created a corresponding UserVoice request:
Enhancing visibility of protection status in WordPress Toolkit
Recently, Plesk added a vulnerability status feature to the WordPress Toolkit, which is a great step forward. However, both the vulnerability status and the protection status are currently accessed through the same link, making it harder to quickly find the protection details. It would benefit...
plesk.uservoice.com
Last edited:
