• 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.ini is empty

BRAHM

Basic Pleskian
TITLE:
PHP.ini is empty
PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE:
CentOS Linux 7.6.1810 (Core)‬
Product Plesk Onyx
Versão 17.8.11 update #41
PROBLEM DESCRIPTION:
I have included a custom configuration in php.ini file and saved it trough plesk.

Now, when I open php.ini config it is empty as follow:


2019-02-22_1101.png
STEPS TO REPRODUCE:
Tools and Setings
PHP configs
edit php parameters
save.

when I get back to php settings it is empty.​
ACTUAL RESULT:
2019-02-22_1101.png
EXPECTED RESULT:
2019-02-22_1103.png
ANY ADDITIONAL INFORMATION:
YOUR EXPECTATIONS FROM PLESK SERVICE TEAM:
Help with sorting out
 
From developer:

Not reproduced. Additional information is required, perhaps investigation on the customer's server.
As an additional investigation step, check if php.ini is present under /opt/plesk/php/7.x/etc/and contains data.
 
I have tried to apply the settings to php.ini and it worked now. I can not understand how it failed before.
 
Last edited:
I have tried to apply the settings to php.ini and it worked now. I can not understand how it failed before.
Most probably it was some kind of browser issue - cookies, cache, etc.
 
Back
Top