• The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

Input Enhancing visibility of protection status in WordPress Toolkit

Maarten

Golden Pleskian
Plesk Guru
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 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:
 
Last edited:
Back
Top