WooCommerce 2.6

Yes, after creating the global attribute you can create the values, however unless a language is set it is not possible to translate the values unless a language is set on the global attribute. Since there is no field on the form to set the source language this has to be done by using the global polylang tool to set items with no language to the default language, after which the global attribute translation works fine.

However the more serious issue is on the product attributes: all attributes and variations are lost on translation, with or without the wooCommerce Polylang integration.
Regarding the point about product variations created before the plugin is installed, on translating these I appeared to also lose detail from the source product.

I was using the dev branch woo-poly-integration-development.zip mentioned on these threads, and I created and copied several site versions to test and was testing translation from English to Spanish and Chinese. All product attributes appeared to be lost on translation except Regular Price of a Simple product.
If there’s some setting I missed, I can easily test it out…

reported versions are:

WordPress 4.5.3,
Polylang by Frédéric Demarle – 1.9.3
Lingotek Translation by Lingotek and Frédéric Demarle – 1.2.1
Hyyan WooCommerce Polylang Integration by Hyyan Abo Fakher – 1.0.0
WooCommerce by WooThemes – 2.6.2

nono price is also lost on translation along with the other attributes, I had added it back manually..

@kamarena – your issue #2 is solved in my last development commit

2. The plug in allows you to add to the cart and buy the same product of the same variation in different language. At the end of the purchase the stock of that variation will show a negative number (even if you selected “not allowed back orders”)

@jonathan – Let’s start then with the must serious issue first.

However the more serious issue is on the product attributes: all attributes and variations are lost on translation, with or without the wooCommerce Polylang integration.
Regarding the point about product variations created before the plugin is installed, on translating these I appeared to also lose detail from the source product.

This should not be happening and I can’t reproduce it. When you create a translation does the url looks like

<install-dir>/wp-admin/post-new.php?post_type=product&from_post=1843&new_lang=de

Before you press “Publish” is the Language set and Title of the source product you are translation shown? Can you take a screenshot of that screen as it opens?

Regarding the other issue, try this steps please:

1. Under Products -> Attributes create a new attribute. Just give it a name, leave everything else as it is and press “Add Attribute”

The new attribute should appear on the right hand side table.

2. Press “Translate Attribute Labels”. You will be redirected to the page Settings -> Languages -> Strings Translations. Look for your new attribute and translated for the other languages you have on your site.

3. Go back to Products -> Attributes and click on the attribute name on the table on the right hand side.

You should see now a form on the left hand side to enter new attri. values. a) Do you see the Language dropdown at the bottom of the form?
On the right you should see a table. b) Do you see columns with flags for all the languages in you site? The table should be empty at this point. Can you take a screenshot and share it here?

@decarvalhoaa you’re doing a great job!

1) Product translation creation
Ok I’ll deactivate Lingotek and try again with your method, as I have been creating from the product list by selecting the upload to Lingotek, Request translations etc or automatically create the default translations in Pending Review status.

Test 4.1 – Ok – if I do the translation myself by turning off Lingotek and hitting the plus from the product screen, the attributes are carried over including the correctly translated global attribute value, good job.

Test 4.2 – create translation by hitting plus on Product Listing – also OK

I tested this with variation product as well, all fine (apart from the inconvenience of not having the default translations).

So it looks like when the translation is created by Lingotek it has bypassed the WooCommerce Polylang Integration

Attribute creation also works perfectly if lingotek is turned off.

I made a new commit today on my Dev branch where the default attributes synchronization is fixed.

Is Lingotek a free service? Is a plugin?

reactivating Lingotek plugin, and setting Translation > Manage > Content Type
Products – Disabled
also works fine.

In any case Lingotek is quite disappointing and not very popular so can probably be safely ignored…

@decarvalhoaa, Lingotek is a free plugin that works with Polylang, by the same authors, the Polylang blue plus and tick symbols get changed to orange when Lingotek is engaged.

The idea is to provide default machine translation and option to engage professional translators.
Unfortunately it is quite clunky:
1. if you aren’t logged into WordPress as the adminstrator user who created the Lingotek account you get blank windows whenever you click into edit-in-lingotek
2. you can’t actually put your own team into your Lingotek group for managing or partially managing your own translations or otherwise offer translation services
3. the Manual workflow has too many steps: ‘Upload to Lingotek’, update lingotek status, ‘Request Translations’, update translation status, download translations, Dis-associate translations [this last step very important otherwise users get a blank screen on editing the translations due to point 1] is excessive just to get a default translation machine translation.

I assumed that Lingotek was a standard option for running with Polylang from the same authors but I see it wp reports only 9,000+ downloads for Lingotek and 100,000 for Polylang so clearly not.

Thx for the explanation.

Thanks decarvalhoaa!

I’ll be testing the latest release!