11

We just released WPML 2.3.2. This new version is all about simplifying the things that you already did with WPML and ironing out issues that you reported in the past two weeks.

First, a quick announcement. WPML 2.3.1 was out last night. It had faulty interaction with several other plugins, causing crashes. We identified the cause of these crashes and they’re fixed in WPML 2.3.2.

Now, let’s get to the fun stuff. What’s new in WPML 2.3.2!

  • Real-time custom fields sync
  • Real-time category and taxonomy update
  • Translation for author fields
  • Smarter Admin language switcher
  • Simplified theme localization options
  • Full Support for all getText calls
  • Synchronization for publish date
  • Easy to resign translators

I wrote about all these in the Beta announcement. Head over there to read the full details of every change.

New in WPML – XLIFF interface

This release of WPML also includes a new module. It’s part of the Multilingual CMS package and is called WPML XLIFF.

XLIFF interface is great if you want to send translation jobs to professional translators, who have their own translation tools. This will allow your translators to use their existing translation software and work on your content offline.

When WPML sends the translators the new-job notification emails, they will also receive a ZIP file with everything to translate. They can translate with their software and then upload in one batch to WordPress.

If you’re working with freelance translators or with a translation service, tell them about the new XLIFF interface. I’m sure they’ll be thrilled by these news.

Read more about it in the page about translating with your CAT tools.

Getting WPML 2.3.2

As always, you can get new releases of WPML either from your Plugins Admin page, or manually by logging in to WPML.org and going to the Downloads section.

Comments, ideas, suggestions?

11 Responses to “WPML 2.3.2 – Better Usability and a Smoother Ride”

  1. Truly outstanding work you guys are doing.

    I am now able to offer my clients fully multilingual sites, and with your intelligent and well developed plugin the whole process is easy and intuitive.

    In my opinion this takes WordPress development to a new level.

  2. In case of changing default language (Japanese), Page attribute except English don’t work by updating WPML 2.3.x.
    WPML 2.2.2.1 is not problem.

    • Can you please start a thread about this in our forum and describe exactly what you’re doing?

      List the steps that you’re doing, so that we can reproduce them. If you can include a short clip, it would help greatly.

  3. Hi,
    I’m just wondering which is the best procedure to update wpml and it’s component on a WP multisite network where the plugin is not activated network wide but site-per-site (not on all the subsite)….
    what’s your opinion?
    thank you!

    • The safest way would be to deactivate WPML on all sites, update the plugin files manually (download from wpml.org) and activate again.

      It’s OK to skip the deactivation, but if visitors hit your site while you’re upgrading, unexpected things can happen.

      • Hi Amir, thank you.

        Just one more question…
        While updating manually, is it better to delete the old folder and upload the new ones or it’s OK to overwrite?

        Thank you!

        • Yes, it’s better to delete the entire folder with the old content. This will ensure that you’re getting all new files and no old file is locked behind.

          For that, you really need to disable the plugin first and enable it after uploading.

    • We haven’t tested it. We’re eager to work together with the folks from AppThemes, but we’re not getting replies from them. If you can remind them that we’re like to test WPML with their code, it might help.