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

Additional Directives - PHP Extension

Ian Cunningham

New Pleskian
I'm running PP 11.0.9 on Windows 2008 R2 and I've tried to add a PHP extension to the additional directives box of the PHP settings page (domain), however this has no effect on PHP. If I add the extension manually to PHP.ini then it works fine, but adding it to the "additional directives" box does nothing - I've confirmed this on 3 different servers, it does the same on all of them.

I did some searching and it looks like others have this problem too:

http://stackoverflow.com/questions/12741931/loading-php-extensions-using-plesk

Is this a bug?
 
Sorry for the slow reply, I have just revisited this issue.

According to the documentation it isn't possible to load an extension via the additional directives box, as the link to the PHP.net docs says it's only available by editing php.ini.

However, the description for the additional directives box says:

Use the same syntax as you use for php.ini. For example, if you want to automatically load the mSQL extension, add the line: extension=msql.so.

So that implies that it is indeed possible?
 
Back
Top