ข้ามการนำทาง
9

WooCommerce team released an update yesterday to WooCommerce 2.2. This update adds great stuff and also requires some small changes in our WooCommerce Multilingual. I’m writing to ask your help and tell us about any other issues that you are running into, so that we can iron out everything early next week.

At the moment, we know that there may be conflicts with slug translations.

From WCML devs:

If the user (that’s you) has not entered explicit values for product category base, product tag base or product attribute base (see screenshot below) the urls for product categories/tags/attributes would not be translated correctly.

This happens because we are using the WooCommerce translations in the mo files to translate in this case and in WooCommerce 2.2 these mo files are not included any longer.

The quick workaround for existing users on this is to go to the permalinks options page, enter the explicit values and then go to the string translation page and translate them manually.

How to get slug translation working in WooCommerce 2.2 (temporary workaround)
How to get slug translation working in WooCommerce 2.2 (temporary workaround)

We already have a workaround for it, but we need more time for testing before we release an update.

Need Help with Any Other Compatibility Problem with WooCommerce 2.2?

Right now, there are quite a lot of ‘moving parts’ related to WooCommerce and WordPress. WordPress 4.0 is out, we recently updated WPML, WooCommerce just got updated and many extensions are following. To quickly resolve issues, we need to narrow things down.

Before you report problems, try to disable as many WooCommerce extensions as possible. This will eliminate issues coming from other places.

To report problems:

  1. Go to WPML support forum and create a new thread. Select ‘Help me solve a problem’.
  2. Enter the debug information from WPML. This FAQ shows how to do it. Getting this debug info saves you and us a lot of time and gets us in the right direction quickly.
  3. Include “WooCommerce 2.2” in the thread title (and also the actual description of your problem).
  4. Also leave a comment here with the link to that thread.

Our plan is to debug and resolve everything during next week. Then, we’ll run full QA for WPML, WordPress 4.0, WooCommerce 2.2.x and WooCommerce Multilingual. You should expect a finished version the following week.