• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

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