This is most probably a bug, therefore, next time it is reported, please, fill a third line so it can be properly investigated.
Symptoms
-
WordPress Toolkit Smart Update fails with one of the following error messages:
PLESK_ERROR: Smart Update was unable to correctly clone your website for further analysis. Please try again later.
PLESK_ERROR: Unable to perform Smart Update on this website. Smart Update has detected that your .htaccess file is customized in a way that could prevent the creation of a properly functioning website clone. Please check and adjust .htaccess file customizations, then try running Smart Update again.
-
The domain has Rewrite rules in one of the following locations:
-
On an
.htaccessfile in the main public website folder -
Domains > example.com > Apache & Nginx Settings > Additional Apache directives
-
Domains > example.com > Apache & Nginx Settings > Additional nginx directives
-
Cause
Some rewrite rules can conflict with the WordPress Toolkit Smart Update verifications due to Smart Update cannot verify that the content has been updated successfully.
Resolution
Apply the following:
Click on a section to expand
-
Make sure there aren't conflictive Rewrite rules placed in the following locations:
-
On an
.htaccessfile in the main public website folder -
Domains > example.com > Apache & Nginx Settings > Additional Apache directives
-
Domains > example.com > Apache & Nginx Settings > Additional nginx directives
-
-
Run the WordPress Toolkit Smart Update
-
Once the WP instance has been updated successfully, consider enabling again the Rewrite rules that were disabled
Warning: This initial check is an essential part of Smart Update functionality and disabling it might affect Smart Update results
- Install Panel.ini Editor extension
-
Go to Extensions > My Extensions > Panel.ini Editor > Open > Editor tab > Place the following configuration and click Save to apply the changes:
CONFIG_TEXT: [ext-wp-toolkit]
smartUpdateInitialCheckEnabled = false
Comments
4 comments
It's true that Additional nginx directives prevent cloning of WordPress sites and thus the functionality of Smart Update. We are currently running Smart Update in a trial.
Do you offer an other solution, workaround to make WordPress Smart Update working with Nginx directives enabled? We use the Nginx directives for HTTP Security headers and to block XMLRPC. So it's not an option to disable the directives during an update. Or do you have an script that will disable it temporary, run Smart Update and enable it?
Looking forward!
There really should be an option to get around this. I cannot disable rewrite rules on a production website (which I guess is the point of smart update, that it actually clones the website, so I don't have to do it manually.)
Please look into a fix for this. This feature is one of the most important features in WP Toolkit - and it should work with something as common as rewrites (Apache or NGINX... but in my case NGINX).
There are NO rewrite rules in place and we still get this error.
We removed all the rewrite rules that aren't required by Wordpress, and removed the nginx rules, but we still have the same issue with the first error message.
Please expand this help page, or make the messages clearer.
Please sign in to leave a comment.