Add HHVM support

The version of GD provided with Plesk PHP packages does not have support for webp enabled by default. Almost all browsers now support this format.
https://developers.google.com/speed/webp/

Argon2 is a new feature of PHP 7.2 as stated here: http://php.net/releases/7_2_0.php. It won the password hashing competition and is the recommended hashing algorithm.

It must be enabled my re-compiling PHP 7.2 with `--with-password-argon2`.

As an alternative to edit PHP-FPM settings per Service Plan, it would be helpful to provide the possibility to setup PHP-FPM settings on the same place as global PHP.ini settings are available

For example, in Tools & Settings > PHP Settings > 7.x > Extensions > Edit PHP.ini and Edit PHP-FPM

Add mcrypt module to Plesk PHP 7.2 and newer.
For previous PHP versions it's included out of the box.

Mcrypt 1.0.2 natively supports PHP 7.2+ (https://pecl.php.net/package/mcrypt/1.0.2)

It's, for example, required by Prestashop 1.7.x, which is quite popular among Plesk users.

We should be able to choose the default PHP version and handler to be assigned to new created domains/subscriptions/webspaces ; without using Service plan or Event Manager.
Thanks

When using the alternative PHP version supplied, it would be great if additional to OPCACHE we would have APCU which can be used for apps like WordPress or Drupal to get higher performance by caching data in the ram.

As PHP is used with PHP-FPM, this is a great deal for us.

It would be nice to have separate php-fpm error logs for each domain instead of logging everything in /var/log/plesk-php7x-fpm/.

It would be nice to be able to use the various Plesk PHP versions to run our webmail services. Especially PHP 7.1

It would be great if the already existing "Applications" view would recognize the PHP version that is used within that application path. That way Composer could check the correct PHP version for dependencies and simplify the general use of Composer.

It's time to add mod_php7.0 and maybe some autoinstaller for most liked modules like ioncubeloader and apcu etc...

Add the support for Gmagick PHP extension for Windows out of the box

At the moment, disable_functions do not work per domain in Plesk for Windows because disable_functions can be specified only in php.ini, not in .user.ini.
Plesk utilizes .user.ini for custom PHP directives only.

Please, implement support for custom disable_functions (and other functions that cannot be specified in.user.ini) on per domain basis in Plesk for Windows.

Thank you.

We've had a similar suggestion before with insufficient information: https://plesk.uservoice.com/forums/184549-feature-suggestions/suggestions/34209229-add-php-handlers-restriction-per-service-plan

The idea is to be able to limit the number of available PHP handlers for selection at domain PHP settings.

This may be done at Service Plan X > Permissions.

Example: customer will be able to select only FPM server by Nginx.

This will allow the ability for more precise configuration.

Based on the support request.

Blackfire (https://blackfire.io) is a PHP performance management & monitoring solution - currently to install with Plesk requires adding specific PHP directives for each domain, and setting up with different PHP versions as well. Would be nice if this could all be integrated in front-end to enable it per domain simply.

Sybase module requires PHP recompilation, which is not possible in case of Plesk PHP: http://php.net/manual/en/sybase.installation.php
The only viable alternative is to install OS-provided PHP, however, it is usually severely outdated.

When a PHP version is disabled, the subscription that already had that PHP version selected can still use that version while no other is selected. Even in the PHP settings in Plesk is possible see the old version, PHP info still working and displaying the disabled PHP version as well.

Its required a feature to avoid that

I found the similar KB here
https://support.plesk.com/hc/en-us/articles/213954385-Not-possible-to-set-allow-url-fopen-parameter-in-Plesk-12-5
but "allow_uri_include" this time. I think this directive is not good to enable globally, so I tried to set it by .user.ini base but the parameter stayed unchanged.