Skip to content
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 process breaks double byte characters #18

Closed
HirokazuNishi opened this issue Dec 10, 2015 · 2 comments
Closed

Migration process breaks double byte characters #18

HirokazuNishi opened this issue Dec 10, 2015 · 2 comments

Comments

@HirokazuNishi
Copy link

Please see attached 2 images. One is M1, and the other is M2.
I created one product on M1 with double byte characters, and executed migration process.
After it completed, I checked product data on M2. Its attributes data with double byte characters are broken.

Can't this tool use for double byte characters?
Of course I can use double byte characters for products or any other data on M2 via cli or admin panel.

m1 product
m2 product

@dgoyachev
Copy link

Have same issue - russian letters breaks while importing 1.9.2.1 -> 2.0.0

@HirokazuNishi
Copy link
Author

I made PR #28.
It was caused by missing option parameters for mysql connection.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants