TITLE:
PHP settings are reset when the PHP version is changed
PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE:Plesk Onyx Version 17.8.11 Update #33
Ubuntu 16.04
PROBLEM DESCRIPTION:Ubuntu 16.04
If the PHP settings have been set via a service plan and have been synced with the customer, these settings can be reset directly by the customer when the customer change/save the PHP version. It will then enable the Plesk default settings for each version of PHP.
STEPS TO REPRODUCE:1. Create a service plan
2. edit the PHP settings. For example: php_memory_limit = 256M
3. Deactivate under the tab permissions: Hosting performance settings management !!!
3. Sync with a customer
4. Login with the synced customer
5. Change the PHP version and save
Before save:

after save:

ACTUAL RESULT:2. edit the PHP settings. For example: php_memory_limit = 256M
3. Deactivate under the tab permissions: Hosting performance settings management !!!
3. Sync with a customer
4. Login with the synced customer
5. Change the PHP version and save
Before save:

after save:

After save, all PHP settings have been set to the default settings!
EXPECTED RESULT:After save, it should keep the php settings from the service plan!
ANY ADDITIONAL INFORMATION:That's a very critical error. It should be fixed as soon as possible.
YOUR EXPECTATIONS FROM PLESK SERVICE TEAM:Confirm bug