Skip Navigation
8

WordPress 6.6 moves away from PHP 7, embracing the faster and more efficient PHP 8+. This release of WPML ensures full compatibility with the latest WordPress and PHP versions.

WordPress 6.6 Changes Support for PHP Versions

WordPress 6.6, scheduled for release on July 16, brings numerous enhancements to the Block Editor, plus a host of other improvements. 

Notably, it changes the recommended PHP version to 7.4 or later, dropping support for PHP 7.0 and 7.1.

WPML 4.6.12 adds support for PHP 8.3 and enhances the overall experience with PHP 8.x.

Get Ready for Better Than Human Translations!

We’re excited to introduce two major upcoming features, which will work together to deliver automatic translation that’s often better than human translation:

  • WPML AI is our new translation engine. It uses LLM technology to deliver contextual and native translation.
  • Maiya will make sure that WPML understands precisely what your text means and that we translate it correctly.
Maiya will help you produce better than human translations

How to Update

As usual, we’re releasing WPML 4.6.12 and String Translation 3.2.13 gradually. As this is not a critical update, we recommend waiting until the updates reach your site. 

If you prefer to update immediately, go to PluginsAdd New, click the Commercial tab, and hit the Check for updates button.

Missing the WPML update in your WordPress admin? Learn more about our gradual rollout process.

Share Your Thoughts

With WordPress updates, PHP support changes, and exciting new WPML features on the horizon, we’d love to hear your feedback in the comments below!

8 Responses to “WPML 4.6.12 – Full Compatibility with WordPress 6.6 and PHP 8.3”

  1. We’re still getting “Deprecated: rtrim(): Passing null to parameter #1 ($string) of type string is deprecated” since PHP 8.1 when WPML is active, as reported more than one year ago: https://wpml.org/forums/topic/deprecated-rtrim-passing-null-to-parameter-1-string-php-8-1/

    And again:
    https://wpml.org/forums/topic/rtrim-passing-null-to-parameter-1-string-of-type-string-is-deprecated/

    And again:
    https://wpml.org/forums/topic/rtrim-passing-null-to-parameter-1-string-of-type-string-is-deprecated-2/

    • Hi Marco,
      Thanks for getting in touch. I passed your message on to our development team, who have informed me that this issue did not appear in our automated tests. In the tickets that you previously opened, it seems that our team was unable to reproduce your issue. However, we would really like to get to the bottom of this – it may be due to a different setup, or it may be something our automated tests missed. Could you please open a Support ticket again, so that a qualified team member can assist you?

    • Hi there,

      Thanks for getting in touch. Can you please try doing the following:
      1. Go to Plugins → Add New Plugin.
      2. Switch to the Commercial tab and click Check for updates.

      If you still don’t see the updates after following the steps above, please open a ticket in our Support forum.

  2. Hi. We are running WPML 4.6.13. If I upgrade PHP to v8.2, on every page, the first element after the body tag is offset by exactly 50px in the Spanish translation. This doesn’t happen with the original English. What could be causing that?

    • Hi, Eric! In general, updating the PHP version shouldn’t impact a site’s front-end display but there are certain cases where it could happen. Without looking at the site more closely, it’s impossible to tell what causes this but I would expect it to be related to the theme or some other plugin rather than WPML. The best would be to report this in our support forum and let our supporters take a look.

Leave a Reply

Please stay on topic and be respectful to others. If you need help with issues not related to this post, use our Support Forum to start a chat or submit a ticket.

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>