Skip Navigation
Home » WPML Blog – News and Updates for the WordPress Multilingual Plugin » WPML versions » WooCommerce Multilingual 1.5 Released with Improvements and Fixes

WooCommerce Multilingual 1.5 Released with Improvements and Fixes

WPML versions
23

We’re very happy to release WooCommerce Multilingual 1.5, with support for WooCommerce 1.6.6, improvements and bug fixes.

As you probably know, WooCommerce is already moving to version 2.0.3. We’re working on support for WooCommerce 2.x, but it’s not ready yet.

This version runs with WooCommerce 1.6.6.

What’s New in WooCommerce Multilingual 1.5

  • Fixed setting prices manually in translated products (so that they don’t auto-sync when not requested)
  • You can translate product slugs and shop slug using WPML’s new slug translation
  • You can translate custom attributes
  • Product variations translation and synchronization is much improved
  • Synchronization for product stock in different languages is fixed
  • Improved checks and warnings against incompatible permalink configurations
  • Fix tax-label translation, when using more than one tax label
  • Sends order notification emails in the language used to place the order
  • Cleaned several warnings and updated deprecated code
  • Cleaned-up the XML language configuration file and add missing strings

Download

This release should appear automatically in your Plugins page. You can also download it manually from the project page on WordPress.org.

Download WooCommerce Multilingual

Your help is vital. If you run into anything that doesn’t look right, or you’re stuck without translation support for anything in WooCommerce, let us know. Start a new thread in our technical forum and we’ll help.

WooCommerce 2.x Compatibility Schedule

At this very moment, David and Alvaro are going through WooCommerce 2.0.3 and WPML. We’ll know what’s missing in a couple of days and it will probably take us around a week or two to release a new version of WooCommerce Multilingual, which supports both the 1.x version and the newer 2.x versions.

I’ll write a new post about it when it’s ready for you.

In the meanwhile, if you want to receive a development version for your testing, please add a comment here. We’ll get in touch with you privately and send you beta versions of WooCommerce Multilingual for 2.x.

Enjoy!

How can we make WPML better for you?

Share your thoughts and comments about our plugin, documentation, or videos by booking a Zoom call with Agnes, our Client Advocate. Your feedback matters and helps us improve.

Book a call with Agnes

23 Responses to “WooCommerce Multilingual 1.5 Released with Improvements and Fixes”

  2. Hello, I am running woocommerce 2.03 and need the beta version of multilingual as this is causing major issues with us adding product attributes where they are not translating.
    Please help as this is urgent.

      • Please add me to the beta list as well.
        Honestly, I have to say that I am rather disappointed that wpml is so far behind with WooCommerce compatibility as they have been in beta for months now and the code was open to everyone to test against.

        • Sure thing. Added you. WooCommerce 2 has been a moving target for a long time. We’ve been working with WooCommerce developers in the last several months and have several big commits in the plugin. For that reason, WooCommerce 2 is pretty compatible already with WPML. In case you’ve noticed, the recent releases of WooCommerce don’t require any patches from us. You can use the official version of WooCommerce, WPML and WooCommerce Multilingual.

          Fortunately (due to a lot of hard work by David), this is the situation with WooCommerce 2, from the beginning. We’ve started on updates for WooCommerce Multilingual 2 some time ago and had to wait until things settle completely in order to complete it.

          We’ll have a new release shortly and will send you beta versions before. Thanks for helping to test, it really helps!

          • Thanks Amir
            Yeah, I will beta the plugin for sure. More than half of the huge project I am working on has to do with a multilingual setup of WooCommerce. I’m already so regretting talking the client into a multilingual setup instead of separate websites. It is always one thing after the next with wpml.
            *not a complaint, an observation after weeks of frustrations on this project is all

            • Thanks for the explanation. The last thing we want is for you to regret having chosen WPML for any project. We’ll do our very best to make this work for you, on time.

              • Naw, it has nothing to do with wpml. It just turns out that I thought wpml was much further along than it is and it would be an easy project. I was very wrong and hope I never EVER have to do another multilingual website as long as I live. Your jobs must suck bigtime, so I feel for ya.

  3. Issue, after update warning txt

    Warning: array_unique() [function.array-unique]: The argument should be an array in /home/tlmarket/public_html/wp-content/plugins/sitepress-multilingual-cms/inc/translation-management/translation-management.class.php on line 3173

    Warning: array_unique() [function.array-unique]: The argument should be an array in /home/tlmarket/public_html/wp-content/plugins/sitepress-multilingual-cms/inc/translation-management/translation-management.class.php on line 3173

    Warning: array_unique() [function.array-unique]: The argument should be an array in /home/tlmarket/public_html/wp-content/plugins/sitepress-multilingual-cms/inc/translation-management/translation-management.class.php on line 3173

    May I reinstall the previous version? where can I find it

  5. Hi There, could you add me to the beta list too? I’m also more than willing to help since WPML-WOOC is essential for my projects.

    Thanks in advance!

  7. Hello, I need to start developing an e-commerce with the theme Camy – Clean Responsive Ecommerce WordPress Theme (http://goo.gl/JDIj4) and WooCommerce 2.01. I recommended to use the current version of WooCommerce Multilingual 1.5 or the beta? It’s urgent, sorry, thanks in advance!

    • The current development version looks OK, but we have found a new issue with variations. We are fixing it and will update here as soon as it’s ready.