• 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.

custom php.ini files

W

wking

Guest
Ok here is the situation, we have a customer that is attemptingto use a custom php.ini file on their account. The php.ini file is in the httpdocs folder where it should be. When checking the php settings using phpinfo.php the user settings and the server default settings match regardless of any entry in the customers php.ini file. I have verified that front page extensions are not installed and have removed the asp.net support as well as removed the dedicated application pool. No change I make to the custoemrs account seems to make any change in the info returned by the phpinfo.php script.
 
Back
Top