Released on:

Features

  • Fixed issue when assigning language information to posts created through inner post insertion.

Fixes

  • Fix compatibility issues with WP Super Cache.
  • Resolved fatal error with Toolset Views in the front-end happening with WPML 4.0.6.
  • Fixed an issue which sometimes prevents translation of Avada’s global items.
  • Relevant check performed to avoid notice.
  • Fixed fatal error when WP Bakery custom grid item is not a valid numeric ID.
  • Resolved Compatibility issue with Avada’s global items when updating them from a standard page.
  • Added support to translate global templates conditions in Elementor.
  • Fixed a fatal error when a term has the same slug in different languages and term ID is different than taxonomy term ID.
  • Added missing quick-link for Media translation settings in the Settings page.
  • Fixed an issue preventing the translation to be saved for WP versions < 4.7.0.
  • Handled possible communication errors between WPML and ATE.
  • Notices are suppressed by relevant checks.
  • Fixed by finding page with exact slug and setting it as best match.
  • Fixed the WPML setup notice which was displayed for non-administrators.

Download and Update

You can get this release directly to the WordPress admin or download and install manually. To receive automatic updates, you need to register WPML on your site. Then, visit the Plugins or Updates admin pages. To download manually, visit your wpml.org account and go to Downloads. Follow the installation and upgrade instructions for complete details.

When you update WPML, be sure to update together all the components that you are using. Don’t use a mixture of new and older versions.

Feedback? Need Help?

We love feedback. To make a suggestion, ask a question or give an idea, leave your comment here. If you need technical support and help troubleshooting problems, please use our technical support forum.

3 Responses to “4.0.7”

  1. Since the new update the edit pages from the back-end have issues to be opened, it arrives in a “page_not_found”. Before I discovered this, I deactivated all plugins, and by activating the WPML plugin, it occurs. Looks like the links changed, or something. Can this please be resolved?

    • What you’re describing shouldn’t happen and it’s not happening to other sites running WPML. There might be something missing or wrong in your DB. We can help you find and fix it. Could you please report this in our support forum, so that one of our supporters can help you?

    • I have the same thing. Even when all plugins except WPML are disabled, the site still gets a page not found. Did you found a solution?

Leave a Reply

Please leave here comments about this page only.
For technical support and feature suggestions, head to our forum. We are waiting there!

You can use these tags:
<a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>