-
Notifications
You must be signed in to change notification settings - Fork 39
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Migration tool stuck on Step7 #43
Comments
@sdeering If you first create an order and go back into this it should work. I had the same issue, it would hang with no orders, as soon as I put in an order it worked. |
@mmazzantini |
Our old migration script here at Github requires a fresh Magento 2 instance, hence it will cause conflict if you've added data in Magento 2 instance before migrating. And it was not updated for recent Magento 2 release, including the latest Magento 2.2.2 which also adds up to the possible unexpected issues during the migration. We're biased when referring you to our Pro version, but it would definitely save you pretty much time. PS. You might want to take a look at this Magento 2 FAQs that walks you through most common issues our users run across when using our Pro version so far. Hope that helps. Regards, |
Thank you for your reply. Its helpful to follow other steps to migrate. |
@vasudevsundar |
After Migration, i can't able to add/ edit product in admin (Magento2.0.0) Showing below error ; Uncaught TypeError: DateTime::__construct() expects parameter 1 to be string, |
As we explained earlier, our script here at Github was outdated. This leads to unexpected issues during the migration. Due to our limited resources, we can provide bug fixes and maintenance update to our Pro version only. That's why we referred you to this newer version. Regards, |
After Migration, i can't able to add/ edit product in admin (Magento2.0.0) Showing below error ; _Uncaught TypeError: DateTime::_construct() expects parameter 1 to be string, Issue Solved by removing some attribute set in Product Attribute |
The text was updated successfully, but these errors were encountered: