- Plesk Onyx for Linux
- Plesk Obsidian for Linux
- Unable to update WordPress core files and plugins via Smart Update feature at Plesk > WordPress > example.com > Updates > Available > Update with Smart Update. The following error is shown:
PLESK_ERROR: Smart Update test run could not be performed due to errors. Address the errors and try running Smart Update again.
Smart Update was unable to correctly clone your website for further analysis. Please try again later.
- During the WordPress updating process with Smart Update, the cloned instance creates a
wpt-fallback-sitemap.xmlfile, as can be seen in the Plesk panel log
/var/log/plesk/panel.logwith debug enabled:
CONFIG_TEXT: DEBUG Starting: filemng fhceadmin exec /var/www/vhosts/example.com/httpdocs/.wp-toolkit_K timeout 60 /opt/plesk/php/7.0/bin/php -d safe_mode=off -d display_errors=off -d opcache.enable_cli=off -d open_basedir= -d error_reporting=341 -d max_execution_time=60 -c /var/www/vhosts/system/example.com/etc/php.ini /usr/local/psa/admin/plib/modules/wp-toolkit/vendor/wp-cli/wp-cli/php/boot-fs.php --path=/var/www/vhosts/example.com/httpdocs/.wp-toolkit_K --no-color sitemap generate wpt-fallback-sitemap.xml, stdin:
sitemap.xml files that are generated for the main website and for the cloned one differ from each other.
This is a WordPress Toolkit extension bug #EXTWPTOOLK-3611, which is planned to be fixed in one of the future updates.
As a workaround, manually create a
smart-update-sitemap.xml and upload it to the instance's Document Root directory:
Go to XML-Sitemaps.com website;
Enter the website URL (for i.e: https://example.com) to create a sitemap for the instance:
Click Download your XML Sitemap File Download:
When downloaded, rename the file from
- Log in to Plesk;
Go to Domains > example.com > File Manager > httpdocs > Upload the
Note: The default Document Root is httpdocs. This can be confirmed at Plesk > Domains > example.com > Hosting Settings > Document Root. In case a custom one is used, upload the file accordingly.