I also need more information on your site by sharing the debug info. If you don’t know how to share the debug info, please follow this article https://wpml.org/faq/provide-debug-information-faster-support/
Your next reply is enabled to share the debug info.
I tried for numerous hours now. Did Backups retried the migration and so on. The migration always works fine. But as soon as I start importing products again like i did before with polylang (i use the same files from the last import with polylang again). The behaviour starts getting weird. Sometimes it works but most of the time the terms get duplicated.
If you clean up the data afterwards (Troubleshooting) everything is fine for the moment. But as soon as I start the import again. It doubles again. So it has to have something todo with the importing process.
What would be the recommended way to do first import after the migration? Use the old wp-all-import, or create a new one and match the items?
Please restore your site to the point before migrating data from Polylang to WPML and I would like to request temporary access (wp-admin and FTP) to your site to take a better look at the issue. It would be better to a testing site where the issue is replicated. Your next reply is set to private to share the info.
❌ IMPORTANT: Please backup your database and website before proceeding ❌
You can use this plugin to create the backup: https://wordpress.org/plugins/duplicator/
✙ I would need your permission to de-activate and re-activate Plugins and the Theme and to change configurations on the site if needed. This is also a reason the backup is critical.
Also, please share the import file with a few products and attributes then let me know steps to import data to your site. I will try to replicate and investigate the issue.
So i figured out what the issue was. Due to some broken imports or similar, there where several variations where the _sku value was unset. As I have to use the sku value (I know you reccomend against in the tutorial, but its the only common constant) for the linking of the product and for the translation linkings as well i think that resulted in the mistakes.
I solve that issue by adding a cleanup function on an importer hook, which deletes non linked variations that block the sku generation. Maybe it would make sense to add a troubleshooting option, which deletes variations that have no value set in the translation linking field?
I don't see the issue with duplicate variations on the sandbox site in the second language but if you set the SKU as the Unique Identifier value to import products/variations for multilanguage, you should set the same value for one product/variation across languages.
If a variation is missing this value in the import file in the second language, it will work properly in the frontend. But it will not be treated as the translation of the variation in the original language and you will not be able to change the variation info in the second language or sync it with the variation in the original language even running the troubleshooting option.
If you create a custom function to delete the variation that does not have the SKU value, that's a good idea. And running the troubleshooting sync in WooCommerce > WooCommerce Multilingual & Multicurrency > Settings > Troubleshooting > Sync products variations, will fix this issue.
We use cookies to optimize our website and services. Your consent allows us to process data such as browsing behavior. Not consenting may affect some features.
Functional
Always active
Required for our website to operate and communicate correctly.
Preferences
The technical storage or access is necessary for the legitimate purpose of storing preferences that are not requested by the subscriber or user.
Statistics
We use these to analyze the statistics of our site. Collected information is completely anonymous.The technical storage or access that is used exclusively for anonymous statistical purposes. Without a subpoena, voluntary compliance on the part of your Internet Service Provider, or additional records from a third party, information stored or retrieved for this purpose alone cannot usually be used to identify you.
Marketing
These cookies track your browsing to provide ads relevant to you.
