23

We just released another (and hopefully) final dev version of WPML 3.2.3. This version has passed our QA and is considered safe for development and production sites. WPML 3.2.3 comes with a long list of improvements, as well as complete compatibility with WordPress 4.3.

WordPress 4.3 updates

Like other WordPress releases, WordPress 4.3 comes with a number of enhancements and code cleanups. This means that some functions that used to exist before 4.3 are now deprecated (should no longer be used). WPML 3.2.3 includes the required changes and uses replacement functions instead of the deprecated ones.

If you are building WordPress sites right now, you should do your development on the dev version of WordPress 4.3. This way, when 4.3 is released, you don’t need to do any last-minute changes to your work. WPML 3.2.3 makes this possible. So, we recommend that you switch your development sites to WordPress 4.3 (dev) and WPML 3.2.3 (this RC).

Other improvements in WPML 3.2.3

Besides the important changes to support WordPress 4.3, this release of WPML comes with a number of important fixes and improvements.

WPML Core

Fixes

  • Fixed missing parentheses in mobile switcher
  • Changing admin language on one site (multisite) does not sets admin language on all sites anymore
  • When ‘Language as Parameter’ is used, wp_link_pages() pagination produce now a properly formed URL
  • Fixed WPML breaking XML-RPC calls
  • Fixed wrong order of languages when using icl_get_languages with orderby=name
  • Fixed redirection issues when the same slug is used in translations with hierarchical post types
  • Fixed page template being unchangeable in translated content, after deactivating the “Synchronize page template” setting
  • Fixed “This is a translation of” being empty when creating a new translation
  • Fixed “This is a translation of” so it’s enabled correctly
  • Removed errors when deactivating WPML for a subsite in multisite install
  • Fixed an issue preventing subsites in a subdirectory multisite setup from completing the last setup step
  • Removed creation of duplicated ‘update_wpml_config_index’ cron job
  • Fixed domain name mapping when a domain name in one language includes the domain name from another language.
  • Fixed problem with Greek characters in taxonomy names causing problems with taxonomy translations editor
  • Fixed language switcher not filtering out empty date archive translations
  • Fixed issues resolving hierarchical page URLs when parent and child use the same page-slug
  • Fixed issue where urls pointing at hidden language posts were redirected incorrectly when using the languages as parameters setting.
  • Fixed ‘wpml_active_languages’ filter so it returns languages with correct data.

Improvements

  • Improved caching of posts, taxonomy translation data, and strings
  • Improved performances
  • Wildcard entries for admin string settings now work for sub-keys on all levels in addition to top-level keys
  • Improved menus synchronization (by a factor of 100)

WPML Translation Management

Fixes

  • Translation Editor shows existing translated content, if there was a previous translation
  • Translation Editor won’t changes language pairs for translators anymore
  • Titles for packages and posts won’t get mixed up in the translation jobs table anymore
  • Users set as translators can translate content again, using the translation editor, even if there is not a translation job created for that content

WPML String Translation

Fixes

  • Fixed a problem with slug translation showing translated slug for English on Multilingual Content Setup when Admin language is other than English
  • Fixed slug translation so it works with the default permalink structure.
  • Fixed caching problem with admin texts which caused some admin texts to not update correctly.
  • Removed PHP Fatal error: Specified key was too long; max key length is 1000 bytes caused by gettext_context_md5
  • Fixed string scanning issues
  • Fixed slug translations so that they are not used when they are disabled
  • Fixed Auto register strings for translation
  • Fixed admin texts so the settings are loaded from the default language and not the administrator’s language
  • Fixed fatal error when an old version of WPML is active

New

  • Support multi-line strings when importing and exporting po files
  • Support gettext contexts in string translation
  • Updated dependency check module

WPML Gravity Forms Multilingual

Improvements

  • It’s now possible to translate all “choices” options (labels and values) of fields with this property

Download and update

Since this is still not a production release, it will not be automatically delivered to your WordPress sites. To get this release candidate, log in to your WPML account and click on Downloads. Scroll to the bottom. If you have a CMS account, get the CMS_Beta_Package and unzip it. It will include ZIP files of all of WPML’s components. If you have a Blog account, download the Blog beta.

Please backup the site before upgrading. Be sure to update all WPML components that you are using.

When is the official release?

This version of WPML has passed all our testing and is ready for a public release. We are hoping to get some feedback on how this update works for you, especially on WordPress 4.3 sites. We will wait for this feedback until the beginning of next week and then hit the Publish button.

Feedback?

We’d love to know how this update works on your sites. If you need technical help, please create threads in our technical support forum. If these are related to this update, you can also leave a comment here with the link to the thread, and a brief description. For anything else that’s less technical, leave your comments here and we’ll reply.

23 Responses to “WPML 3.2.3 Release Candidate with WordPress 4.3 Support”

  1. I have just install this 3.2.3 Release Candidate on my site and the issue I had with using a different domain per language is now fixed… It was returning a 500 Internal Server Error….

    Thank you

    Greg

  2. Is there a list somewhere of deprecated functions?

    Can you please clarify:
    From now on deprecated functions should no longer be used. What about earlier sites coded with now deprecated functions?

    Thanks,
    Piet

  3. Hi there –

    ‘Fraid to be the one asking the stupid question but… am I supposed to manually replace the files/folders?

    Using the plugin uploader I get an error message telling me the sitepress-etc.-etc. folder already exists, and the install failed.

    Did I miss something?

    Thanks!
    🙂
    Best,
    Jesper W.

    • We just released WPML 3.2.3 (official version). Now it comes through the normal update process, so you don’t need to do any manual editing. The updated versions should appear in the WordPress dashboard in 12 hours (WordPress update caching). Then, you should just click on the Update buttons and you’re all set.

      Before any major updates, we recommend doing backups.

      • on the same subject:

        – does this update comes up to the dashboard before upgrading to wp 4.3? haven’t done it yet and wpml updates have stopped on version 3.1.9.7

        – and we should start by updating wp to 4.3 and only after that wpml plugins?

        tks

        • Hi Herminio,

          Automatic updates in 3.1.9.7 are disabled in purpose.

          You can update manually:
          – download all the plugins you are using
          – unzip them
          – deactivate them on your site
          – replace the plugins in your server with the unzipped ones
          – reactivate them (no data should get lost, but it’s always a good practice to make a backup before these actions)

          After you update, you will get the back automatic updates.

          Please, if you are using ICanLocalize to translate content, do not update: we are finishing and polishing a migration plugin which will allow ICL users to update WPML.

  4. We have updated wordpress from 4.2 to 4.3 and wpml to latest version. Including all wpml plugins like string translation and others. Our main language for the web was spanish and second language english (translate).

    After update all strings translation are in spanish (before english) but still main language is spanish. I only have the option to translate to spanish not english.

    Before there was an option on string translation page to choose the language of the strings. We can’t found it now.

    Any solution???

    • Do you remember what version of WPML you updated from?

      Older versions had a GUI for setting the source language of strings, but this GUI did nothing. We removed it now because it was really misleading.

      We are working on a major update that will allow you to choose the source language for strings, per context. This way, you can keep the WordPress core, plugins and the theme as ‘English’, but set the source language of texts that you enter in the WP Admin to your site’s default language.

      This should make it a lot simpler to translate sites that don’t have English, or that use a default language other than English.

      We are working on it right now. It’s a big change, so this will take a few weeks to complete and clean. I’ll write about it in our blog and newsletter as soon as there’s a test version ready.

  5. SLUG PROBLEM DETECT WITH WPML (last version) and WORDPRESS 4.3

    /blog/
    /es/blog/
    /de/blog

    WONT WORK PROPERLY. REDIRECT PROBLEMS. DO NOT UPDATE!