Skip Navigation

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.

This topic contains 8 replies, has 2 voices.

Last updated by Yvette 4 years, 9 months ago.

Assisted by: Yvette.

Author Posts
June 14, 2019 at 11:37 am #4020987

stianM

We have a site using Woocommerce and WPML with a bunch of products that only exists in the default language (the products are created by an integration to a remote ERP system). When I need to update the descriptions for the default language, I create an import that updates the products using the SKU to map my CSV rows to the existing products – no problem.

Now I want to create a different import for a secondary language. If the product is not translated, I want the translation to be created.

I've read the tutorial here: https://wpml.org/documentation/related-projects/wpml-all-import-plugin-website-import-with-wpml/
This approach seems to assume that the products in the default language are imported using WP All Import, because I'm forced to map the products using the "Unique Identifier". The products that already exist in the default language don't have a "Unique Identifier" because they aren't created by WP All Import. It would be nice if I could map the secondary language import using another custom field, like the _sku.

So I'm wondering how I can import the secondary language when the products already exist in the default language, and are not originally imported using WP All Import.

June 14, 2019 at 3:33 pm #4022741

Yvette
Supporter

Languages: English (English ) Spanish (Español )

Timezone: Europe/Paris (GMT+01:00)

Hello

This scenario is not supported by WPML All Import. As you suggested, the plugin requires a previous import to "connect" to in order to update our own translation tables with a translation "grouping" for the products involved.

As a type of "workaround"....could it be possible to use WP All Export to create an export file that you then re-import to create the required previous "import"?

Another thought is to use an XLIFF interface to translate the existing products through Translation Management. e.g. create a translation job for the product, then import the translation using XLIFF file interface.

More here: https://wpml.org/documentation/translating-your-contents/using-desktop-cat-tools/configuring-xliff-file-options/

I wait for your feedback on these suggestions

June 19, 2019 at 6:34 am #4048397

stianM

Thank you for your reply.

Regarding your first workaround: I already created an import for the default language where I updated the content field for all products. Because I used "Import data from this file into existing items" (I was matching items based on SKU) I didn't get to set any "unique identifier".

This means I do have an export I can connect the secondary language import to, but the products still don't have a "unique identifier" that I can use to connect the rows.

Was your suggestion to delete all products and then re-import them in order to set a unique identifier, or do you have another way to do this? I would preferably like to use WPML All Import for both languages so we don't have to teach our client to use two different tools to update products.

June 19, 2019 at 9:55 am #4050431

Yvette
Supporter

Languages: English (English ) Spanish (Español )

Timezone: Europe/Paris (GMT+01:00)

Hello

You wrote: "..This means I do have an export I can connect the secondary language import to, but the products still don't have a "unique identifier" that I can use to connect the rows..."

Do you mean you cannot use the SKU again to link the 2nd language import?
e.g. the first "update" import cannot be referenced/linked to?

June 19, 2019 at 10:41 am #4050795

stianM

The first "update" import can be referenced, and I can select the SKU again. But the problem is (I think) that the SKU is not used as the unique identifier in the first import, because the first import is only used to update existing products – not create them.

June 19, 2019 at 12:17 pm #4051389

Yvette
Supporter

Languages: English (English ) Spanish (Español )

Timezone: Europe/Paris (GMT+01:00)

Aha - let me ask the developer for some feedback.

June 19, 2019 at 1:04 pm #4051757

Yvette
Supporter

Languages: English (English ) Spanish (Español )

Timezone: Europe/Paris (GMT+01:00)

So I can confirm that your options are as follows:

1 - export original products, add connection to translated and import again
2 - perform import only in secondary language and then, on translated product edit screen, choose option "this is translation of..." but this will take a lot of time

I hope this resolves your question.

June 19, 2019 at 1:22 pm #4051797

stianM

Just to clarify – by 1, do you mean export them, delete them in Woo and then re-import them? Seems like a lot of trouble just to translate some texts.

June 20, 2019 at 11:09 am #4059275

Yvette
Supporter

Languages: English (English ) Spanish (Español )

Timezone: Europe/Paris (GMT+01:00)

I´m checking this for you and will update with an answer - you can also just try doing one product as a test to get a quicker answer.

This ticket is now closed. If you're a WPML client and need related help, please open a new support ticket.