- Plesk for Linux
Custom WordPress instance settings that are specified on a WordPress admin page at
http://example.com/wp-admin are reset or rewritten.
It may have the following symptoms:
Custom Site Title and Site Language preferences are manually set in WordPress admin page http://example.com/wp-admin > Settings > General:
When Preferred domain is changed in Plesk > example.com > Hosting Settings, then:
Custom WordPress settings are rewritten and substituted (replaced) with WordPress Toolkit default settings Site name and Interface Language specified in Plesk > Domains > example.com > Applications > Manage My Applications > My CMS > Change Setting.
The following email is sent to the WordPress administrator mailbox:
CONFIG_TEXT: Subject: [My CMS] Notice of Password Change
This notice confirms that your password was changed on WordPress Instance Name.
If you did not change your password, please contact the Site Administrator at firstname.lastname@example.org
Customizations are reset to default after syncing the subscription with its service plan after changing Hosting Parameters for a service plan via Plesk > Service Plans > Hosting Plans > Default > Hosting Parameters > Update & Sync.
The following record can be found in
/var/log/plesk/panel.logwith enabled debug:
CONFIG_TEXT: [util_exec] [0e4e8322fd503b8bf81fa8a644efbb4b-0] Starting: sappmng --run-application-script --script-file-name=configure --script-name=configure --script-language=php --user-name=test --php-cli=/usr/bin/php5 --php-ini=/var/www/vhosts/system/example.com/etc/php.ini --application-full-name=file:////opt/psa/var/apspackages/b0cee9e4-9620-463a-b74f-82321438096d/cache
There may be other symptoms when customization defined on a WordPress admin page are reset on Plesk.
This is a Plesk extension bug EXTWPTOOLK-1245 that will be fixed in future product updates.
This bug is typical for Plesk 12.x only as in Plesk 12.x WordPress Toolkit is used as APS application.
The bug can also be reproduced in Plesk Onyx if the Wordpress instance is installed via a catalog of applications (APS) instead of WordPress Toolkit Extension.
For Plesk 12.x:
Upgrade to the latest supported Plesk version and install WordPress instances using WordPress Toolkit which is improved and works as an extension (installed directly from www.wordpress.org), not as APS. In WordPress that works as an extension in Plesk Onyx, the bug is not reproduced at all.
As a workaround:
Set custom Site name and Interface Language in WordPress Toolkit directly in Plesk > Domains > example.com > Applications > Manage My Applications > My CMS > Change Settings.
Note: Any customizations defined on a WordPress admin page are not supported by WordPress Toolkit in Plesk 12.x.
For Plesk Onyx: