With the holidays behind us, we kicked off the new year with a major WPML release. Now, we present a 3.9.2 version which fixes important issues, adds a few new features, and improves overall stability.

Why it is important to update to this version

WPML 3.9.0 version introduced many important features and changed other ones. In the past few weeks we have been gathering all your feedback and bug reports, which brings us to this release.

By updating to the 3.9.2 version you will get all these fixes and improvements. This way, you avoid running into the same issues and spend your time creating unnecessary support tickets.

What’s new and fixed

Let’s go over the most important changes and fixes for this release. See the last section of this page for a complete changelog.

WPML Core 3.9.2

  • You can now unlock the translation mode for custom fields even if they are set by wpml-config.xml.
  • In Translation Editor, we fixed the button for copying content of custom fields.
  • We resolved errors produced when having an empty wpml-config.xml file.

WPML String Translation 2.7.2

  • We fixed an issue with missing page builder fields when creating a new translation of pre-existing posts.
  • We added the possibility to scan the must-use (MU) plugins for texts (strings).
  • For Elementor compatibility, we fixed an issue with saving the post body correctly and made Elementor form’s select fields translatable.

WPML Translation Management 2.5.1

  • We fixed an issue with missing page builder fields when creating a new translation of pre-existing posts.
  • We implemented a WPML_ENVIRONMENT constant which blocks the fetching of translations. This is a very helpful feature for your test and staging sites, because you want translation to be fetched on your live, production site.
  • We fixed various issues regarding emails sent to translators.
  • We fixed an issue with Gravity Forms and the links not being adjusted.

WPML Sticky Links 1.4.3

  • Resolved a fatal error related to an AbsoluteLinks class

 

Updating to WPML 3.9.2

As always, you will receive this update for WPML plugins automatically to all registered sites. You can download and install manually from your WPML account. Please be sure to update all of WPML’s components.

Finally, remember that it’s always a good idea to backup the database before updating anything in your sites.

Full changelog

WPML Core 3.9.2

Features

  • Allow the translation mode for custom fields to be unlocked when they are set by wpml-config.xml
  • Fixed an issue where “Copy content from” button was not copying custom fields.
  • Added two actions that allow synchronizing of custom fields.

Fixes

  • Implemented multiple security fixes.
  • Fixed a typo in the query parser causing infinite redirection with specific configurations.
  • Fixed an error where the menu has a language switcher with no items.
  • Resolved an exception with pagination resulting in compatibility issue with WP-PageNavi plugin.
  • Fixed a fatal error related to WPML_LS_Templates::are_template_paths_valid class.
  • Adjusted the color picker style in the language switcher’s admin page.
  • Improved the post selection when the slug is shared between multiple posts.
  • Resolved errors produced when having an empty wpml-config.xml file.
  • Fixed a “Fatal error: Uncaught TypeError: Argument 1 passed to WPML_End_User_Page_Identify::__construct()”
  • Improved the sanitize_title filter for some specific locales.
  • Fixed an issue with wrong redirection when a 404 page is accessed with an arbitrary argument.
  • Fixed an issue with pluggable functions when using different domain per language.
  • Resolved an exception with wrong redirection occurring on attachment pages when they have the same slug.
  • Fixed the URL in WP SEO snippet preview when using the “Different languages in directories” option.

WPML String Translation 2.7.2

Features

  • Implemented the scanning of strings for Must-use (MU) plugins.

Fixes

  • Implemented multiple security fixes.
  • Fixed an issue where page builder fields were missing when creating a new translation of pre-existing posts.
  • Fixed escaping of contexts when exporting .po files.
  • Fixed an issue when saving Elementor page translation, to save the post body correctly.
  • Made Elementor form select fields translatable.

WPML Translation Management 2.5.1

Features

  • Implemented a new “WPML_ENVIRONMENT” constant for partially locking communication to Translation Proxy when it is set to “test”.
  • Included a list of registered shortcodes in the exported XLIFF file.

Fixes

  • Implemented multiple security fixes.
  • Fixed an issue with the “Open in translation editor” button on the dialog of the post edit screen.
  • Fixed an issue with email strings being sent to translators in mixed languages.
  • Fixed wording in the notice that appears after the activation of ICanLocalize.
  • Fixed an issue with Gravity Forms where links were not adjusted.
  • Fixed the wrong encoding in emails sent to translators.

WPML Sticky Links 1.4.3

Fixes

  • Resolved a fatal error related to the AbsoluteLinks class.
  • Implemented multiple security fixes.

8 Responses to “WPML 3.9.2 with Important Fixes and Better Overall Stability”

  1. Glad to hear, thank you.

    I’ve found another bugs.

    When the option “Translatable – use translation if available or fallback to default language” is enabled, the comments which were published in English for example, it still counts the number of comments in other languages even if the Synchronization of comments is disabled and surely there is no comments in other languages.

    On the other hand, I am using “YITH Advanced Reviews” and It still shows the comments (Reviews) themselves on product pages in other languages.
    and “YITH Product Compare” won’t add any products correctly in other languages though it works correct in the default language.
    Both of these 2 above are of course when fake-duplicated.
    Is it because of the plugin’s compatibility or just a bug of new WPML?
    If it was the issue of the plugins, I should ask the YITH developers.

    Best regards

    • Hello and thank you for your comment!

      Regarding your first point. Comments are usually assigned to a post. If you use the “Translatable – use translation if available or fallback to default language” mode – then they are assigned to the available language post. This means it should increment the count in that language. I don’t think that there is a way to separate this as otherwise the comments would be orphaned.

      And regarding the YITH issues. It is really hard to guess anything, it would definitely require testing from our side. Would you please be so kind to open a ticket about this issue?

      Thank you!

  2. Thank you for your reply.

    I also got an e-mail directly from your teammate asking about my bug report. But I reply here for not getting confused.

    Well, I can understand that there should be a technical difficulty with the synchronization of comments.
    But on duplicated contents, comments and comment’s counts were displayed separately, and since the game change, it will have to be mixed up…?
    hmm… at this rate, Japanese auditors gonna be obliged to see every comments in English, French, and etc.
    I really hope that there will be some solution somehow.

    About the issues with YITH plugins, the plugins that are installed on my website are not up-to-date actually. since I modified them, I can’t update them to maintain the stability.
    But I don’t think the problem is plugin’s core. If you can afford to cope this issue, I’d love that WPML team contact YITH developers directly. this way, more good communication.

    I am not sure yet if I can continue debugging, seems like there’s still more to work on for me but anyways okay.
    Thank you very much for your kind reply again.

    • Hi, and thank you for the update on the issue. Yes, of course, if tests show that the issue is on the YITH side of things, we will escalate it to their development team directly. Thank you!

    • Hello and thank you for contacting us.
      Could you please open a new ticket in our support forum so that we investigate the problem properly?
      The issue could be caused by various things – including also a corruption of some of your plugin files.
      As a preliminary step, I recommend that you obtain a fresh copy of your plugin files and also perhaps give it a try with another browser or in incognito mode.
      It is possible that some browser extensions or settings can cause slowness in the page – especially if the page is bigger than normal.

    • Hello and thank you for the very nice question.
      We added these two hooks:

      do_action( 'wpml_sync_custom_field', $post_id, $custom_field );

      will sync the value of the specified custom field to all translation. It only does it if the custom field also has to be set to Copy mode.


      do_action( 'wpml_sync_all_custom_fields', $post_id );

      will sync all custom fields that are set to Copy mode to all translation of the given post ID.

      Our documentation team is working on adding this information on our list of hooks and soon it will be there.