Autoloader: deprecation notice when using PHP 8.3

[lifeforceinst]

Impacted plugin

Jetpack

Quick summary

After installing latest Ubuntu server 24.04 with PHP 8.3.6 and loading up WordPress 6.5.2 and porting across the database and then loading WooCommerce. If debugging is enabled, the following error message is generated.

strlen(): Passing null to parameter #1 ($string) of type string is deprecated in /var/www/html3/mylf/wp-content/plugins/woocommerce/vendor/jetpack-autoloader/class-path-processor.php on line 132

This indicates that a guard rail should be provided in this function to deal with strlen() being passed a null paramater.

Steps to reproduce

1 Install ubuntu 24.04 wwith PHP 8.3.6 and other necessary applications.
2 Install WordPress 6.5.2.
3 Port across MySQL database.
4 Enable debug in wp-config.php with define('WP_DEBUG', true); and define('WP_DEBUG_LOG', true);
5 Install WooCommerce.
6 As soon as WooCommerce is loaded, the error is displayed on admin console and in error logs.

A clear and concise description of what you expected to happen.

There should be no message about depreciated call.

After reporting to WooCommerce sithub at woocommerce/woocommerce#47001 this was closed saying to report the issue to Jetpack.

What actually happened

WooCommerce: strlen(): Passing null to parameter #1 ($string) of type string is deprecated in /var/www/html/wp-content/plugins/woocommerce/vendor/jetpack-autoloader/class-path-processor.php on line 132

Impact

All

Available workarounds?

No but the platform is still usable

Platform (Simple and/or Atomic)

Self-hosted

Logs or notes

Ubuntu 24.04
Server Info: Apache/2.4.58 (Ubuntu)
PHP Version: 8.3.6
WordPress: 6.5.2
WooCommerce : 8.8.2

[jeherve]

Thanks for the report, we'll take a look at this and update this issue once we make progress on that.

[anomiex]

I was unable to reproduce this following the instructions given. Unless it's specific to Ubuntu 24.04 somehow and won't reproduce on Debian bullseye with PHP 8.3 installed.

Examining the relevant code, the one caller of that private method passes output from wp_normalize_path(), and that function always returns a string. So either I'm missing something, or something is very weird in the reporter's environment.