WP Toolkit feature to detect plugin and theme conflicts
Please implement a function in the WP Toolkit that would detect plugin or theme conflicts. For example, cloning a website with WP Toolkit sometimes fails due to a plugin or theme that is interfering with the WP-CLI commands execution. Usually, running the same WP-CLI command with the --skip-plugins and/or --skip-themes flag allows the command to be executed successfully.
Currently, the WP Toolkit doesn't provide enough information why the cloning fails. It would be useful if there's a functional, which would provide more information on what particular plugin or theme is causing the issue.
Plesk Tech Support
shared this idea
Thank you for the update. We can certainly attempt to improve the error/warning reporting during cloning processes. We will consider this functionality in upcoming releases if it becomes popular.
Everyone, please continue voting for this feature if you consider it important.
-- SH
-
Thomas commented
As the initiator, I would first like to thank you for your feedback.
Yes, I am aware that this is certainly not easy to implement and that due to the large number of plugins and themes, the tool often malfunctions.
It is not about recognizing all incompatibilities between any plugins and themes, but about detailed information why a process (for example the cloning process) could not be carried out.
End users cannot do much with errors such as “Unexpected token ‘;’”.
It would certainly be possible to create a database in which compatibility problems could be stored and queried.
For another example, the toolkit times out because the database check takes too long due to a table, further information would be useful.
Best regards
Thomas -
Adrian commented
I am well aware that this involves a more complex mechanism, but it could likely be effectively addressed with machine learning and a corresponding database. However, it would be a significant help if the error message could indicate something like, "There was an error during cloning: $ErrorMessage." This way, end users can recognize that the process was interrupted by Plugin XYZ. Deactivating the plugin and attempting the cloning process again can certainly be handled by the customer themselves.
The feature is basically too good to do without - at least as a warning as to which plugin caused the crash.
In any case, thank you very much for taking a look at my suggestion. -
Marcus Krämer commented
We need this!
-
That would be a awesome feature with a lot of benefit.
-
Patrizia Marano commented
Yes please.