• Introducing WebPros Cloud - a fully managed infrastructure platform purpose-built to simplify the deployment of WebPros products !  WebPros Cloud enables you to easily deliver WebPros solutions — without the complexity of managing the infrastructure.
    Join the pilot program today!
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.
  • 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.

Custom subdomain PHP settings reset when main domain is changed

ThomasR

Basic Pleskian
Hi,

We're using Plesk 11.5 for Linux with multiple PHP versions on several servers. On certain conditions we are experiencing issues with PHP settings (PHP version and/or custom PHP settings) for a subdomain when the server executes an action on the main domain. Two examples:

1. The main domain uses PHP 5.4, the subdomain uses PHP 5.6 (both as FastCGI). When we add a new PHP handler for PHP 5.6 and replace the old with the new one (using /usr/local/psa/bin/php_handler --replace -old-id fastcgi-5.6.14 -new-id fastcgi-5.6.15), then all subdomains are reset to PHP 5.4.

2. Both main domain and subdomain uses PHP 5.6 (which is not the default PHP version on the server). The main domain uses default PHP settings, the subdomain has some custom PHP settings set by Plesk's web interface. When setting a general configuration (e.g. changing the hard quota limit under "FTP Access" or adding a domain alias), the custom PHP settings for the subdomain are reset to the default values which are used by the main domain.

It looks like both issues are triggered by a syncing action, although the subscription is locked.

Does anyone have had the same problems? Does there is permanent solution for it? I've no idea if the same problem occurs in Plesk 12.x as well.
 
Back
Top