You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is a great program (idea) but needs some cleaning on its available function set.
First thing I notice is the function like import to --blog_id=5, this is not functioning, and data goes into id #1 by default.
The MU-Migration needs more mysql options to be able to use commands like --set-gtid-purged=OFF or the import fails on servers that don't use root as the main user.
On failed import, there is the unpacked zip folder. So why not give a secondary option to edit the sql file, make fixes, and then redo the import without the zip file and with the directory, for example: wp mu-migration import all ./mu-migration1624807939 etc...
Additionally the function --new_url= is not functioning. It is using the original url in the sql file which is not correct! That would be the old url. It places the old url into the main multisite url url.
And, I'm not getting any error messages. There seems to be a need for some error messages with all these errors happening. Right?
Operating system is freebsd, if you care.
The text was updated successfully, but these errors were encountered:
This is a great program (idea) but needs some cleaning on its available function set.
First thing I notice is the function like import to --blog_id=5, this is not functioning, and data goes into id #1 by default.
The MU-Migration needs more mysql options to be able to use commands like --set-gtid-purged=OFF or the import fails on servers that don't use root as the main user.
On failed import, there is the unpacked zip folder. So why not give a secondary option to edit the sql file, make fixes, and then redo the import without the zip file and with the directory, for example: wp mu-migration import all ./mu-migration1624807939 etc...
Additionally the function --new_url= is not functioning. It is using the original url in the sql file which is not correct! That would be the old url. It places the old url into the main multisite url url.
And, I'm not getting any error messages. There seems to be a need for some error messages with all these errors happening. Right?
Operating system is freebsd, if you care.
The text was updated successfully, but these errors were encountered: