Home›Support›English Support›[Fixed in next Release] PHP 8.4 Implicitly marking parameter ... as nullable is deprecated, the explicit nullable type must ...
[Fixed in next Release] PHP 8.4 Implicitly marking parameter ... as nullable is deprecated, the explicit nullable type must ...
This is the technical support forum for WPML - the multilingual WordPress plugin.
Everyone can read, but only WPML clients can post here. WPML team is replying on the forum 6 days per week, 22 hours per day.
Our second-tier supporter has let me know that our developers are already working on WPML compatibility with PHP 8.4. Among other things, those deprecation notices will also be handled. It will be included in future versions of WPML. We'll keep you updated when the version with the fix is released. Unfurtunatly I can't provide an ETA for when it will be released.
PHP 8.3 is already deprecated (= no more active support, only security updates) since end of 2025 see hidden link but you still have PHP deprecation notices in PHP 8.4, which was released 1.5 years ago and reaches end of life in 9 months...
Thanks for pointing out the state of Supported PHP Versions as they appear on the PHP official website. We are operating within the WordPress ecosystem, and PHP 8.4 is still in beta support. You can see it here https://make.wordpress.org/core/handbook/references/php-compatibility-and-wordpress-versions/. Please also see the attached screenshot. In any case, I can see from our tracking of this case that the support for PHP 8.4 will be included in the next WPML version 4.9.3. This should be released soon. I'll keep you updated here.
@itamar
Please stop using this logic as it is not correct. WordPress does not mention PHP 8.4 & 8.5 beta support because it has issues. It does so because it is not sure plugin makers comply with all standards yet. This is their official statement:
Due to the acknowledgement that WordPress is rarely used in isolation (without any theme or plugins), support is labelled as “beta support” until at least 10% of all WordPress sites are running that version or later, as this indicates good compatibility across the wider ecosystem of plugins and themes.
So it is on you guys to get ahead of it. I also reported it and it is difficult to bugfix with all the wpml notices cluttering everything.
I do not want to push you guys as I know you are working on it but I want you to stop using this excuse.