[Waiting for user feedback] Plugin Compatibility Issue with PHP 8.3

Hi there,

Were you able to review my colleague's response regarding these PHP warnings?

https://wpml.org/forums/topic/warnings-after-updating-to-php-8-2/#post-14489421

When I review them they do not look related to WPML, I'd advise testing in a minimal environment to see which plugin or theme is not triggering these.

Note that WordPress itself is only in beta compatibility for PHP 8.3 and many plugins tend to follow the compatibility schedule of WordPress.

Thank you for updating me!

I have created a sandbox for us to further investigate.

Please access the sandbox and upload your theme.

hidden link

As your theme is custom, please do note that it has not been tested by our team as an officially supported theme would and that our support is limited when it comes to custom themes.

Our team has run tests with PHP 8.3 and this warning has not been seen before when using a standard WordPress theme such as twenty25 for example.

I understand, no problem!

Is there a possibility to create a staging site from your side with just the theme and WPML activated? Possibly on the same server so the PHP versions are the same.

As we are not aware of any known issues with PHP 8.3 and the warnings mentioned here with just WPML it is highly likely they might be coming from a combination of a custom theme + WPML, this method will allow us to confirm this.

Thank you for updating me!

Unfortunately, we do not have an option for us to arrange a call.

I could possibly re assign your ticket to somebody closer to your timezone as I am located in the Pacific Standard Time (PST) zone.

Also, it's important to note that at this point we need to further investigate this issue, which we cannot do without access to either the live site or a staging site.

Is either one of these options available?

As a workaround since these are warnings and do not pose threat to your site and the way it operates you can you can safely remove these warnings by doing the following

Go in your wp-config.php file and look for define(‘WP_DEBUG’, true);.

Change it to:

define('WP_DEBUG', false);

In case access to the site is possible, i will enable the private field reply.

Thank you for the screencast.

Please try the following steps:

1. Test in a minimal environment.

Deactivate all 3rd party plugins and leave only the WPML plugins activated, along with a standard WP theme such as Twenty25.

Does the warning still show?

2. Change the PHP Version to another one available such as 8.2 for example

Let me know your results

3. Go in your wp-config.php file and look for define(‘WP_DEBUG’, true);.

Change it to:

define('WP_DEBUG', false);

Does this help remove the warnings?

To remove the warnings please add this in the wp-config.php and replace the previously added code.

NOTE: Do not add define('WP_DEBUG', false); and define('WP_DEBUG_DISPLAY', false); twice as that will trigger an error.

ini_set('display_errors','Off');
ini_set('error_reporting', E_ALL );
define('WP_DEBUG', false);
define('WP_DEBUG_DISPLAY', false);

Another option is to try this workaround provided by our team:
https://wpml.org/forums/topic/deprecated-rtrim-passing-null-to-parameter-1-string-php-8-1-2/#post-13670953

Our developers are aware of this warning and a fix will be introduced in a future version of WPML. At the moment it's most likely going to be included in WPML 4.7 but I cannot provide a specific timeline for this release at the moment.