Thomas
My feedback
3 results found
-
19 votes
Thank you for your input. We will consider this functionality in upcoming releases if it is popular. Everyone, please continue voting for this feature if you consider it important.
—
IG -
13 votes
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
An error occurred while saving the comment -
22 votes
Thank you for your input. We will consider this functionality in upcoming releases if it is popular. Everyone, please continue voting for this feature if you consider it important.
—
IG
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