• Please be aware: Kaspersky Anti-Virus has been deprecated
    With the upgrade to Plesk Obsidian 18.0.64, "Kaspersky Anti-Virus for Servers" will be automatically removed from the servers it is installed on. We recommend that you migrate to Sophos Anti-Virus for Servers.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

Forwarded to devs PHP settings reset when the PHP version is changed/saved by customer

B4c4rd1

Regular Pleskian
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:
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:
upload_2018-12-13_11-44-51.png

after save:
upload_2018-12-13_11-45-9.png
ACTUAL RESULT:
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
 
@IgorG,

have you an Update?

We already have some customers complaining about it. We are reluctant to check every single server if the error has occurred.

Thanks!
 
@IgorG,

Are you serious? You prefer a system that has the status preview? I can not understand that.

In the case of a bug that causes a high level of support you do not want to call an ETA? We have multiple Plesk instances and are currently busy just to prevent the bug...
 
I understand your concern about the problem. But the situation is that the problem fix for 17.8 is very dependent on the fix for 17.9. For version 17.9, the fix will be released within a few days, and then it will be ported to 17.8. Note, that bug has a critical status, so it will be processed in the corresponding priority.
 
@IgorG,

We can confirm that the bug was fixed!

Plesk Onyx 17.8.11 Update 39
  • Subscription's PHP settings are no longer expected to default values after the PHP handler version was changed. (PPPM-9817)
Thanks to the entire Plesk team!
 
Back
Top