Question: When deleting the DE product, shouldn't the system automatically delete the EN version - as it's linked to the DE version ? Or is this standard in WPML that you manually have to delete all translated/wpml linked version(s) of a product ?
To enable this, you need to go to WPML -> Settings -> Synchronization of posts and pages. There are two checkboxes for this feature.
Regarding the category count for EN, that was indeed a typo, apologies for the confusion. It’s the opposite—the count went from 4 to 8.
- 2nd (en) import imported EN categories into the DE category list (I believe its because you are in DE mode when importing)
Yes, this is somewhat expected because we need to store that information somewhere as part of the import/export process, since WooCommerce’s import routine doesn’t support multilingual content.
- the WPML Import/Export action moved the EN product correctly, but categories were moved/mixed incorrectly
I’ll discuss it with our development team and keep you updated.
This issue appears to be related to a known bug that requires development adjustments. In this case, the parent category seems to be incorrectly assigned to the other language, causing the child category to also appear there while still being counted in the original language.
Currently, the best approach seems to involve manual database modifications. This would involve first correcting the parent category's language, then re-linking the parent and child categories to their original counterparts to ensure everything functions correctly.
It would actually be nice/better if no category information were part of an import file with translations, as woocommerce and WPML should already know the assigned categories (taken from the original language). What happens if a translated product is assigned to a different set of categories ? wouldn't that make 'a mess' in the db ?
At this time, I can’t provide an exact timeframe for a solution. The issue is already in our backlog, but our developers are currently focused on the upcoming 4.8 release. I’ll keep you updated here as soon as there’s any news. I've also shared your feedback with our developers to explore potential improvements.
unfortunately, I can't provide an update on this at the moment. The resolution depends on the ongoing development of the Import Add-On, and I don’t have a timeline for when it will be resolved.
I ran two new imports (using the built-in csv importer) and the 2nd import showed an error which I haven't seen before. The first import showed "Import complete! 1 product imported. 2 variations imported", the 2nd showed "Import complete! 3 products were skipped." and the log for each product/variant showed "A product with this SKU already exists." During the 2nd import I didn't select "Existing products that match by ID or SKU will be updated. Products that do not exist will be skipped".
The products in 2nd import csv file (which contains the translations) contain the identical SKU's as the product in the first file/import.
Could this be related to 'new/adjusted code' in the built in import tool ?
Not that we are aware of. However, what you describe doesn’t seem to be an error. That said, we don’t have enough information to provide a definitive answer without clear steps to reproduce the issue.
If you need further assistance, please create a separate ticket for this matter and keep this ticket focused on the category hierarchy issue.
In the csv files with translations, which you also have tested, we have assigned SKU numbers on all products/variations. Now the import of these files fails - so now I can't get to the point where we see the errors with categories.
