- Plesk Onyx for Linux
Note: This article has the reference to the issues with the fixes available:
"A WordPress site could not be cloned if proc_open was disabled in PHP settings of the source or destination domain."
- WordPress Toolkit 2.0.2 31 March 2017
"Manually removing a WordPress database without using Plesk could result in inability to install or clone WordPress instances."
Cannot create a clone, the following error is received:
Cloning Failed, database does not exist
The cloned instances are created but are shown with a warning:
Unable to read WordPress configuration file
The following error can be found in
ERR  '/usr/local/psa/admin/bin/filemng' 'db_user' 'exec' '/var/www/vhosts/example.com' '/usr/local/psa/admin/plib/modules/wp-toolkit/vendor/wp-cli/wp-cli/bin/wp' '--path=/var/www/vhosts/example.com/test.example.com' 'config-settings' 'get' '--params=DB_NAME,DB_USER,DB_HOST,DOMAIN_CURRENT_SITE,PATH_CURRENT_SITE,MULTISITE,SUBDOMAIN_INSTALL,WP_AUTO_UPDATE_CORE,WP_DEBUG,WP_DEBUG_LOG,WP_DEBUG_DISPLAY,SCRIPT_DEBUG,SAVEQUERIES,WP_AUTO_UPDATE_CORE' '--format=json' failed with code 81.
Plesk database is inconsistent, as the command
plesk repair db -n
Inconsistency in the table 'db_users' for the column db_id: No rows
Plesk database is not consistent.
This is WordPress Toolkit bug with ID #EXTWPTOOLK-471 that will be fixed in one of the updates.
As a workaround:
1. Remove all broken cloned instances
2. Fix the database inconsistencies:
# plesk repair db