adelval

WooCommerce Multilingual 2.0, compatible with Woocommerce 2.0.x has been released.
blogpost: https://wpml.org/2013/03/woocommerce-multilingual-2-0-released/
get it: https://www.ads-software.com/extend/plugins/woocommerce-multilingual/

@rapidz
Do you also have the latest version of Woocommerce Multilingual (2.0) ?
The issue about manual conversion of prices did sometimes arise with previous versions, but should be fixed by now. Tested with Woocommerce 2.0.4. (And you don’t even need to unlink the duplicate)

Hi,

Sorry for the late reply.

I answer here only to the first issue you raised, about manual pricing. Basically, the problem is that no fields are saved from translated products unless they are marked as “translate”. For this to work, you need to do three things:

1) In WPML->Translation Management->Multilingual Content Setup, look for the section “Custom fields translation”. There, tick “translate” for the fields you want to translate (e.g. all those containing the substring “price”).

2) In WPML->Woocommerce Multilingual, enable multicurrency and select the manual option (Ok, I know you got this right, I put it here just for reference and other readers’ benefit)

3) In each product page, you must do the same thing as in Step 1, such as mark _price, _regular_price and _sale_price as “translate”.

It’s clear that the process could be made simpler for users, so I’m reporting back to our development team.

Please let me know if this works for you. In my test site it did.

I answer in this thread so that issues about localization are not spread out over many threads. The calendar is localized fine for me in Spanish. Most error messages are as well. But things like “You have specified an appointment request without a date” are not. I tried changing the provided contact-json-spanish.php but it had no effect. (On the other hand, I’d like to know where other error messages are located, since though I do get them in Spanish, a “grep -R” for any given Spanish message in the plugin directory finds none of the other error messages).

Thanks, it works as expected now.

I have the same issue, with the latest versions of the plugin (3.2) and wordpress (3.4.2), and the Force SSL option checked. In fact, the redirects occur in two cases: if I try to access an SSL page with http, or if I try to access a non-SSL page with https (in all other situations it works fine).

Specifically for “https://example.com/my-NON-ssl-page” I get two 301 redirects, first to “https://example.com/index.php” and then to “https://example.com” (the latter I wouldn’t expect of wordpress, but it seems that’s what it does if you try to access index.php from the address bar as well).

In other direction is worse. For “https://example.com/my-ssl-page” I get 301 redirects to “https://example.com/index.php” then to “https://example.com/” then “https://example.com/index.php” and finally to “https://example.com/”

Not sure when this began to happen, I discovered it recently by some diagnostic messages in webmaster tools.

Thanks for your help