• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • 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.

suggestion

S

slacker22

Guest
There should be more conditional logic in the code that checks for potential problems. It seems the software tries to do things even if they arent possible, ( Like write to a directory it cant ). Even the database connection isnt checked... If mysql is down you just get the standard php error... I needed to increase the max number of connections of mysql so that i could login to plesk. It just bombed with a php error. Professional software shouldnt bomb out.. In software this complex you should have more error checking and provide the user with more helpful options. I mean how hard would it be to say "Sorry the configuration of your server is incorrect because of the following reasons". Or "The operation could not be completed because.. Please do this to resolve the issue".

All of this is fine if you writing free software. But if you are going to charge for it you need to make it more user friendly. Ive used php software that costs 50 bucks that has better error checking then this.
 
Back
Top