Skip Navigation
Home » WPML Blog – News and Updates for the WordPress Multilingual Plugin » WPML versions » WPML compatibility release for WordPress 4.5

WPML compatibility release for WordPress 4.5

WPML versions
16

We are working to release an update for WPML (and its add-ons plugins) to address some compatibility issues with WordPress 4.5.

WordPress 4.5 brings several changes in its API, changes which need to be addressed and which require holding the development of WPML 3.4 (more about WPML 3.4 in the next posts).

Of course, some bug fixes not related to WordPress 4.5 also slipped in, as they occurred during the development of WPML 3.4.

We are currently under full QA, which usually takes several days, but you can start using our beta version right now. If you do so, please share your feedback or questions in our support forum.

WP 4.5 Fixes

As for WordPress 4.5 compatibility, here’s a list of what we have worked with:

  • WPML Core 3.3.7: fixed compatibility issues with terms editing functionalities
  • WPML Translation Management 2.1.6: replaced use of deprecated function `get_currentuserinfo`
  • WPML String Translation 2.3.7: fixed filtering rewrite rules for WP 4.5 when the rules are cleared

Other relevant changes in WPML 3.3.7

You can find the full changelog.md in each plugin’s folder.

WPML Core 3.3.7

Fixes

  • Fixed some issues with post synchronization (“Copy publishing date” option and post date synchronisation).
  • Fixed several WP SEO compatibility issues with sitemaps generation, missing trailing slashes, taxonomies, and “Adjust IDs for multilingual functionality” being randomly disabled
  • Fixed unexpected browser redirection on root page
  • When the blog page is deleted and then re-translated, it is now possible to set the blog page in Settings > Reading
  • Improved sitepress.js to use var when declaring variables, so as to allow minification and combination of scripts in strict mode
  • Show language switcher if CPT is set to do nothing
  • `wp_get_archives` now works for any custom post type
  • Fixed notices when updating to the latest version with browser redirection activated.

Performances

  • Removed non-translators cache from options.

Features

  • Auto-disconnect duplicates when they are edited and only if there are changes.
  • Increased the accepted length of “Default Locale” and “Tag” in the languages table, so as to allow variations such as “de_DE_formal”
  • Hide system fields when displaying custom fields and terms meta in “Multilingual Content Setup”

Compatibility

  • WP SEO user meta fields are now translatable with WPML String Translation

WPML String Translation 2.3.7

Fixes

  • Fixed issue with theme scanned on each access to WPML > Plugin and theme localization
  • Fixed error when scanning themes/plugins for strings on localhost on Windows
  • Fixed filtering of translation jobs when selecting “From language”

Features

  • Author biographical info is now translatable in string translation

WPML Translation Management 2.1.6

Fixes

  • Fixed issue where translated XLIFFs with ‘0’ (zero) as content were not accepted from Translation Management
  • Fixed `Fatal error: Uncaught exception ‘InvalidArgumentException’ with message ‘Tried to load a string filter for a non-existent language’`
  • Added option to disconnect multiple duplicates (bulk mode) in TM Basket before sending for translation.
  • Fixed issue with incorrect redirections after translation save/update and wrong post/page edit links.
  • Reduce the number of DB queries on listing pages.

Features

  • Hide system fields when displaying custom fields and terms meta
  • Added external-file in XLIFF files, to allow third party services to access the original URL.

WPML Media Translation 2.1.20

Fixes

  • Fixed language filter issue in Media Library section.

CMS NAV 1.4.18

Fixes

  • `$post->ancestors` is a read-only field and should not be set
  • Fixed bug occurring when the “auto-save” action was running, and causing some CMS-NAV loss data during post editing
  • Fixed issue with pages’ order not being respected

Gravity Forms Multilingual 1.3.8

Fixes

  • Fixed issue when a field is removed from a form: the related strings are now removed
  • Previous and next buttons are now fully translatable

16 Responses to “WPML compatibility release for WordPress 4.5”

    • Jan, this version set the hreflang meta to the highest priority as possible.

      However, you will have a new setting in the “WPML > Languages > SEO Options” where you can decide to restore this priority to the default one (which is 10), as it’s used to be few WPML versions ago.

      We will soon publish more details about this feature.

    • I’m constantly looking at Google Webmaster Tools, and I did see about 108 indexed pages but it’s now dropping again!

      When I use Googlebot-simulator on http://www.ac-hydraulic.dk/de is shows a permanent redirect?!

      I’m loosing traffic big time – and need support – please let me know if my thread should re-open, or if we can continue it on this page

      Googlebot-simulator:
      HTTP/1.1 301 Moved Permanently
      Date: Tue, 29 Mar 2016 13:05:58 GMT
      Server: Apache/2.2.29 (Unix) PHP/5.3.10
      X-Powered-By: W3 Total Cache/0.9.4.1
      Set-Cookie: _icl_current_language=de; expires=Wed, 30-Mar-2016 13:05:58 GMT; path=/
      Set-Cookie: _icl_current_language=de; expires=Wed, 30-Mar-2016 13:05:58 GMT; path=/
      Location: http://www.ac-hydraulic.dk/de/
      Cache-Control: max-age=3600
      Expires: Tue, 29 Mar 2016 14:05:58 GMT
      Vary: User-Agent, Accept-Encoding
      Content-Type: text/html; charset=UTF-8
      Content-Length: 0
      Keep-Alive: timeout=5, max=100
      Connection: Keep-Alive

  3. Fast reply, thanks 😉
    It’s true, we use W3 total cache to redirect depending on language. I’m surprised it says 301, maybe I’ll disable it. But we’ve had it for more than a year, and the total annihilation by Google was because of the href lang.

    • The 301 redirect is almost definitely caused by the browser redirect option.
      The fact is that Google introduced JavaScript parsing about a year ago: until then this wasn’t an issue, but now Google understand some JavaScript, including the browser redirection script WPML use to redirect visitors.
      This, in addition to the hreflang issue (which fix is going to be released soon), could have added confusion to the issues you were facing 🙂

      I hope that, with the 3.3.7 release, these SEO issues will be gone for good! 🙂

      • Are there any beta’s out, I can try. My pages have dropped from 950 indexed to less than 100. I’ve just tried to disable the browser redirect, but the error persists.
        Also tried disabling W3 and iThemes Security Pro.

        • Like, should I just wait it out – and hope Google accepts my changes from the support thread, or should I go with 3.3.7-b1.
          My a** is on fire :/

          • There is a beta, but some fixes have been added after the beta has been released.
            You can find the beta by going in you account, and then clicking the “Downloads” link.
            Scrolling down to “CMS Beta Package”, you can download the most recent beta.

            Anyway, are are wrapping up the formal release: if you can wait a bit longer, you can update to WPML 3.3.7 🙂

  5. Qucik question, is the double lines set by WPML or W3?

    Set-Cookie: _icl_current_language=de; expires=Wed, 30-Mar-2016 13:05:58 GMT; path=/
    Set-Cookie: _icl_current_language=de; expires=Wed, 30-Mar-2016 13:05:58 GMT; path=/

    • I see the code has changed when I crawl one of my sites with Googlebot-simulator

      FROM:

      HTTP/1.1 301 Moved Permanently
      Date: Tue, 29 Mar 2016 13:05:58 GMT
      Server: Apache/2.2.29 (Unix) PHP/5.3.10
      X-Powered-By: W3 Total Cache/0.9.4.1
      Set-Cookie: _icl_current_language=de; expires=Wed, 30-Mar-2016 13:05:58 GMT; path=/
      Set-Cookie: _icl_current_language=de; expires=Wed, 30-Mar-2016 13:05:58 GMT; path=/
      Location: http://www.ac-hydraulic.dk/de/
      Cache-Control: max-age=3600
      Expires: Tue, 29 Mar 2016 14:05:58 GMT
      Vary: User-Agent, Accept-Encoding
      Content-Type: text/html; charset=UTF-8
      Content-Length: 0
      Keep-Alive: timeout=5, max=100
      Connection: Keep-Alive

      TO:

      http://www.ac-hydraulic.dk/download/output.txt

      • I’m not sure how to compare these two results, as they are in a completely different format 🙂

        Anyway, could you please create a ticket in the forum: they will be able to assist you better, as in the post comments we don’t have the right means to provide proper support.

        Thanks.