PHP 8.4 Deprecated Warnings

Resolved

(@ispreview)

I’ve just started testing PHP 8.4 and came across a few deprecated warnings that need to be tackled:

Deprecated: YoastSEO_Vendor\Symfony\Component\DependencyInjection\Container::__construct(): Implicitly marking parameter $parameterBag as nullable is deprecated, the explicit nullable type must be used instead in /wp-content/plugins/wordpress-seo/vendor_prefixed/symfony/dependency-injection/Container.php on line 60

Deprecated: YoastSEO_Vendor\League\OAuth2\Client\Provider\AbstractProvider::authorize(): Implicitly marking parameter $redirectHandler as nullable is deprecated, the explicit nullable type must be used instead in /wp-content/plugins/wordpress-seo/vendor_prefixed/league/oauth2-client/src/Provider/AbstractProvider.php on line 416

Deprecated: YoastSEO_Vendor\GuzzleHttp\Client::getConfig(): Implicitly marking parameter $option as nullable is deprecated, the explicit nullable type must be used instead in /wp-content/plugins/wordpress-seo/vendor_prefixed/guzzlehttp/guzzle/src/Client.php on line 181

Deprecated: YoastSEO_Vendor\GuzzleHttp\ClientInterface::getConfig(): Implicitly marking parameter $option as nullable is deprecated, the explicit nullable type must be used instead in /wp-content/plugins/wordpress-seo/vendor_prefixed/guzzlehttp/guzzle/src/ClientInterface.php on line 77

Viewing 4 replies - 1 through 4 (of 4 total)

Plugin Support Maybellyne
(@maybellyne)

1 year, 1 month ago

Hello @ispreview,

Thanks for reaching out, but deprecations are NOT errors and should NOT be treated as such. Deprecations don’t break any WordPress functionality and are not errors, so you can ignore them. You can ensure that DEBUG_DISPLAY is turned off.

Furthermore, WordPress 6.7 is still in beta support for PHP 8.4. Our development team will fix deprecated messages for PHP 8.4 when WordPress is fully compatible with it. Here’s the detailed table on WordPress-supported PHP versions mentioning the stable, exemptions, and beta support.

Thread Starter ispreview
(@ispreview)

1 year, 1 month ago

I didn’t say they were errors, I said they were “warnings”. But what they do is fill up your error logs and slightly slow down each PHP process, which makes it harder to spot the real errors. Looking forward to when they get cleaned up.
Thread Starter ispreview
(@ispreview)

9 months, 3 weeks ago
I’m not a PHP coder, but I got so tired of waiting for you to fix the most basic stuff that I’ve learnt and done it myself:
```
/wp-content/plugins/wordpress-seo/vendor_prefixed/symfony/dependency-injection/Container.php on line 60

Change:

    public function __construct(\YoastSEO_Vendor\Symfony\Component\DependencyInjection\ParameterBag\ParameterBagInterface $parameterBag = null)

To This:

    public function __construct(?\YoastSEO_Vendor\Symfony\Component\DependencyInjection\ParameterBag\ParameterBagInterface $parameterBag = null)


/wp-content/plugins/wordpress-seo/vendor_prefixed/league/oauth2-client/src/Provider/AbstractProvider.php on line 416

Change:

    public function authorize(array $options = [], callable $redirectHandler = null)

To:

    public function authorize(array $options = [], callable|null $redirectHandler = null)

/wp-content/plugins/wordpress-seo/vendor_prefixed/guzzlehttp/guzzle/src/Client.php on line 181

Change:

    public function getConfig(string $option = null)

To:

    public function getConfig(?string $option = null)


/wp-content/plugins/wordpress-seo/vendor_prefixed/guzzlehttp/guzzle/src/ClientInterface.php on line 77

Change:

    public function getConfig(string $option = null);

To This:

    public function getConfig(?string $option = null);
```
casl
(@casl)

9 months, 2 weeks ago

Hi, host configurated on last update Php 8.3 brings no more deprecated warning.

Viewing 4 replies - 1 through 4 (of 4 total)

The topic ‘PHP 8.4 Deprecated Warnings’ is closed to new replies.