This is the technical support forum for WPML - the multilingual WordPress plugin.
Everyone can read, but only WPML clients can post here. WPML team is replying on the forum 6 days per week, 22 hours per day.
No supporters are available to work today on this forum. Feel free to create tickets and we will handle it as soon as we are online. Thank you for your understanding.
our corporate website uses WordPress with WooCommerce to show our product range (about 1.000 products). We have multiple Languages, so we added WPML to handle this. We use WP All Import Pro with WooCommerce Import Add-On Pro and WPML All Import to import the product data from our PIM-Software into WooCommerce.
On a different website of ours, where we only have one language, this works great. But the multi-language site gives us some trouble.
We created separate imports for all four business areas, one for German and one for English each.
We started with the German import which creates all the attributes and populates them with German terms.
In the next step, we created an English import where we set the Language to English and selected the corresponding German import in the All Import WPML Settings. For the attributes, we used the same Names and Values as in the German import. The plan was to later translate these with WPML. For the initial import, this all works great. Problems arise when we try to update the products.
To update products, we edited the templates of the initial imports and changed the files before running them again. At this step we encountered a problem:
The import doesn't recognize that the attributes were already created, are populated with terms and translated. It creates a new attribute with the same name and a slightly different slug. The result is that the translation in WPML isn't working anymore, and it shows German product data in the English version.
Example:
See the screenshot attached. The correct attribute is Öffnungsart with the slug oeffnungsart that has a translated term. The update import created a second attribute called Öffnungsart (slug: offnungsart) that overwrites the correct attribute.
Can you explain to us how this happens and how we can prevent this?
We are very interested in finding a solution to our goal of importing our products in multiple languages into WooCommerce and would be open to contract a developer to achieve it.
Welcome to the WPML support forum. My name is Nicolas and I will be happy to help you today.
Could you please clarify a point:
- The issue happens on both languages? Or only when you update the English import?
1. I'm asking because when importing products in the secondary language it's really import to translate FIRST all taxonomies and attributes before importing the products.
2. Yes you can translate them with the same value as German, that's not an issue
3. Also, in order to import translated taxonomies you will have to follow the same logic as importing products:
- Create an unique identifier
- Import German categories
- Import English categories, connected to the German import and linked by the same unique identifier
That way WPML can link the German and English categories together (You can verify that by going to ""WooCommerce > WooCommerce Multilingual > Categories" and see if German categories have translations).
4. Once all Categories are translated, you can then import the English products with an unique identifier that links them to the German products.
If so, could you please provide me with a temporary admin access (wp-admin and FTP) – preferably to a test site where the issue has been replicated – so I can further investigate. I will activate a private field for your next answer where you can provide that information safely (this field is only visible by you and the support team). Don't share your own admin account, create a new one that you will delete when we finish troubleshooting.
IMPORTANT: Before we proceed, please backup your site and database.
Nico
The topic ‘[Closed] WP All import issue with taxonomies’ is closed to new replies.
