decarvalhoaa

After you created a Product Attribute under Admin > Products > Attributes, click on the button “Translate Attributes Labels”. This will open the Polylang’s Strings Translation page where you can translate your just created product attribute.

Now, you need to create and translate the product attributes terms. Go to Admin > Products > Attributes and click on the name of the product attribute. This will open a page where yoiu can create the attributre terms. For example: if your attribute is Colour, your terms are blue, green, red,etc. You can use the normal Polylang functionality to translate the terms.

Now ahead to Admin > Products > Add Product and create your product. Click on Attributes and from the dropdown box choose your attribute, in my example colour. Click the Add button and in the input field write the terms you have created before, or simply select all terms by clicking the button Select All.

If you are creating a Variable Product, don’t forget to select Variable Product in the dropdown box so that the option “Use as variation” is shown.

Can you tell us what versions of WC and Polylang you have installed? Please indicate whether your Polylang version is the Pro version or otherwise.

Have you tried, disabling and activating the Woo-Poly plugin?

For variable product, the price is set for each variation. Below the dropbox where you select Variable Product, click on the tab Variations. When you expand all the variations you will find the fields – including regular and sales price – for that variation of the product.

If you don’t have a tab called Variations, you have not yet created an attribute – coulor in you case, and/or have not set (yet another checkbox) to “Used for variations” in the Attributes tab.

Sorry if this explanaition is not easy to follow, but WooCommerce Variable Products is difficult to explain.

When you create the variable product on the default language, is the price kept for all the variations after you save / update?

• This reply was modified 8 years ago by decarvalhoaa.

Have you created the variable product first in the default language? and only then create the translations?

And confirm that in the Plugin settings (Admin > Settings > WooPoly > Metas List) all the metas you want to sync are ticked.

Try first solving the other issue your reported. If it is related to the URL modification setting that may as well be causing issue with the emails. If that is not the case, please let me know what are the emails that are not being translated. There are a few emails that are not supported yet but I’m trying to find the time to implement that.

Changing lang files will not help you.

Please check your Polylang settings. If you have URL modifications configured to The language is set from content this may be the issue.

The Plugin, as indicated in the description doesn’t support this config.

What you need to know about this plugin
The plugin needs PHP5.3 or above
This plugin is developed in sync with Polylang and WooCommerce latest version
The plugin support variable products , but using them will disallow you to change the default language , because of the way the plugin implements this support. So you have to make sure to choose the default language before you start adding new variable products.
Polylang URL modifications method The language is set from content is not supported yet

Thanks for the head-up @anphira

In you particular case, the “Ingredients” is the name of the attribute that you already translated to “Ingredi?nten”.

The entire list of ingredients is 1 term. You need to translate this 1 term to all your site languages. You missed to do step number 3 in the instructions above provided by @mguderle to achieve that.

• This reply was modified 8 years, 1 month ago by decarvalhoaa.

Can you share the wordpress permalinks settings and Polylang URL modification Settings?

This feature is not implemented in the plugin. However, you are welcome to suggest the implementation here https://github.com/hyyan/woo-poly-integration/issues

@tiagorestivo – I don’t you make a Push Request for that in github https://github.com/hyyan/woo-poly-integration/ ?

@rmgl – lets start with gathering some info:
– what languages have you configured in Polylang and what are the Default?
– Have you translated the strings in the Polylang strings translations table?
– have you check if you have the WooCommerce language files for your all languages?

I have implemented the following fix: When a new translation of a variable product is created, the variation descriptions are copied over to the translation (as before). However, now is possible to edit/change the variation description. The description will not be overwritten when you Save/Update your product.

I have tested in my staging environment. Can I ask you to install the plugin and help testing it? The plugin can be found here https://github.com/hyyan/woo-poly-integration/archive/variation_description.zip
Please don’t install this in a production environment. Only use it in your test environment.

If I get positive feedback from you guy and after further testing, I wiill push a request to Hyyan to add this to the next release.

By the way, this version has several other fixes:

– Fixed PHP notice due to Polylang deprecated functions
– Fixed WordPress database error in reports page
– Fixed missing argument warning in order detailspage and emails
– Fixed strpos() empty needle warning for empty endpoints
– Fixed removing email instructions from 3rd party payment gateways
– Fixed not detecting whether polylang pro is active
– Fixed PHP notice in Reports when products don’t have translations
– Fix variation description couldnt be translated
– Fix variable product default attributes not synced

Thanks for helping identifying the gap. I will work on the implementation for the emails Cancelled Order, Failed Order, Order On-hold and Order Notification for the next release. release date of the new release is however subject to @hyyan availability and timelines.

Your are right regarding the Cancelled Order. I just checked the code and the translation for this email type is not implemented. I have not implemented because this email is typically intended for the shop managers etc. Therefore is sent in the default admin language.

Sorry for mislead you. What I wrote is nonetheless valid for the other emails except admin emails.

• This reply was modified 8 years, 1 month ago by decarvalhoaa.