25

We’re happy to release WPML 3.1.6, further improving data caching, performances, and security.

Most of the changes in this release are under the hood and won’t be immediately noticed, unless you faced performances issues.

We also added several hooks for themes and plugin developers, to reduce the number of lines of code, removing previously needed logic to check if functions or plugins existed.

WPML core

  • Time of first activation of WPML plugin reduced to about 5% of previous results
  • WPML now resolves site URL and paths to plugins directories in better way, respecting different server and WordPress settings
  • Improved caching of WPML function’s results, especially for WordPress in multi site mode
  • We added new screen to WPML > Support with debug informations, this will be helpful when WPML users will need our help at forum
  • Enhanced compatibility with WP SEO plugin and NextGen Gallery plugin
    Fixed possible SQL injections
  • Fixed language switcher on custom post type archive pages
  • Support for translate_object_id filter – this can be used in themes instead of the icl_object_id function
  • Fixed widget previews
  • Function url_to_postid() is now filtered by WPML plugin to return correct post ID.
  • Constants ICL_DONT_LOAD_LANGUAGE_SELECTOR_CSS + ICL_DONT_LOAD_LANGUAGES_JS are respected now when JS and CSS files are loaded
  • Several additional bug fixes

WPML CMS NAV

  • Fixed possible SQL injections
  • Minor syntax fixes

WPML MEDIA

  • Improved compatibility with plugins, which filters lists of attachments

WPML STICKY LINKS

  • Fixed sticky links handling in widgets
  • Fixed possible SQL injections

WPML STRING TRANSLATION

  • String Translation module respects now that strings can be stored in arrays with hash index equal to zero
  • Improved translation caching
  • Improved translation of blog name in multisite mode

WPML TRANSLATION ANALYTICS

  • Fixed possible SQL injections
  • WPML TRANSLATION MANAGEMENT and WPML XLIFF
  • Support for different formats of new lines in XLIFF files; this improves compatibility with different translation software

Download and upgrade

If you are using our Installer plugin, you will receive this update automatically to your WordPress admin. You can always download manually from your WPML account.

Again, this is a pretty major upgrade, with almost every file in WPML edited. We backed up our database before this release and you should too.

Credits

WPML 3.1.6 is the result of very hard work from the entire team. Want to meet them?

Konrad

Konrad was in charge of WPML 3.1.6, fixing bugs, improving performance and taking care of biz.

Andrea

Andrea is WPML’s lead developer. In parallel to this maintenance release, Andrea is leading the next major version of WPML.

Paweł

Paweł is now working on extending WPML’s interfaces to translation services. Most on this very soon.

Next for WPML

WPML 3.2 is in the pipe, getting ready for QA. It’s a major update to the Translation Management and String Translation modules.

Ideas? Suggestions? Leave your comments and we’ll get back to you.

25 Responses to “WPML 3.1.6 – Stability Update”

  1. Site down after upgrade !

    Warning: Unknown: failed to open stream: No such file or directory in Unknown on line 0

    Fatal error: Unknown: Failed opening required ‘/kunden/homepages/6/d453959470/htdocs/gastronomeparisien/wp-content/plugins/sitepress-multilingual-cms/res/css/gzip.php’ (include_path=’.:/usr/lib/php5.4′) in Unknown on line 0

    • Hello Alex.

      I’m sorry you’re facing such kind of issue.

      We will contact you shortly in order to help you troubleshooting the issue.

  2. On a new installation of latest WP and latest WPML, bbpress is installed but the link does not appear on menu. If WPML is deactivated then it shows up.
    Please sort this

  3. I can´t update the plugin,
    It doesn´t work from the wp repository, neither I see how can update from here
    Thanks

  4. Hi, I just did update the WPML wordpress plugin, and it cause some problem in Divi theme, of Elegant theme. I can’t write the text in text section. Please can you help me.

    • Hi Marco,

      would you please so kind to create a thread in our support forum?

      After you do that, a member of our support team will provide you all the help you need.

      Thanks.

        • Hi Michael,

          I didn’t understand there vulnerability was such critical, sorry.

          I’m about to send you an private email, so you can explain what you have found.

          Thanks!

          • No, I was just giving my opinion on the matter. I don’t know of any vulnerabilities, please ask Sysadmin who posted this comment. Thanks.

            • I’m sorry Michael. Got a bit confused 🙂

              Thanks for pointing out anyway: I’m in touch with Sysadmin now.

              Regards

  5. Hi, I have problems with Views after updating String translation. I use Toolset and WPML together on 3 websites and they all reacting strange. I downgraded String translations to solve the problem.

    Kind regards, Addy

    • We are also updating Types and CRED, so that all plugins should work together correctly. It’s already fixed in the development versions. Would you like to receive a development version and verify that it’s good for you?

  6. Do you have any idea when wpml 3.2 will be release ? Is it going to be before or after WordPress 4.0 launch.

    Hope you’ll fix the quadruple click when translating a post(checkbox, duplicate, edit, translate independently).

    My clients find it hard to understand compare to qtranslate.

    • Hello Julien,

      We have a lot of things coming in the next version of WPML.
      There is also an improved “Copy content from original” feature: this will get rid of the workflow you have described.

      But yet, there is still some ongoing development, plus following testing, and this requires time.

      We are still discussing if we must release a 3.1.7 intermediate version.
      This would precede WPML 3.2, but it all depends on when we manage to complete our pending development tasks.

      If we find out that we need more time, we may consider to release a beta version.
      Of course, this beta version would still need to go through our QA testing process.