• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

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