Title: Deprecated warnings on PHP 8.4
Last modified: May 3, 2025

---

# Deprecated warnings on PHP 8.4

 *  [Chris](https://wordpress.org/support/users/christof15/)
 * (@christof15)
 * [11 months, 2 weeks ago](https://wordpress.org/support/topic/deprecated-warnings-on-php-8-4/)
 * **Deprecated**: Google\Site_Kit\Core\Authentication\Clients\Google_Site_Kit_Client::
   authorize(): Implicitly marking parameter $http as nullable is deprecated, the
   explicit nullable type must be used instead in **/home/user1/web/example.nl/public_html/
   wp-content/plugins/google-site-kit/includes/Core/Authentication/Clients/Google_Site_Kit_Client.
   php** on line **99**
 * **Deprecated**: Google\Site_Kit\Core\Authentication\Clients\Google_Site_Kit_Client::
   fetchAuthToken(): Implicitly marking parameter $http_handler as nullable is deprecated,
   the explicit nullable type must be used instead in **/home/****user1**/web/**
   example**.nl/public_html/wp-content/plugins/google-site-kit/includes/Core/Authentication/
   Clients/Google_Site_Kit_Client.php on line **260**

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

 *  Plugin Support [James Osborne](https://wordpress.org/support/users/jamesosborne/)
 * (@jamesosborne)
 * [11 months, 2 weeks ago](https://wordpress.org/support/topic/deprecated-warnings-on-php-8-4/#post-18450061)
 * Thanks for reaching out [@christof15](https://wordpress.org/support/users/christof15/),
   and highlighting this warning.
 * It’s not uncommon to encounter such deprecation warnings if using PHP 8.4, however,
   these don’t impact any standard Site Kit functionality. Many such warnings may
   even be coming from WordPress core, despite appearing to be Site Kit specific.
   You’ll see that PHP 8.4 remains in beta support from reviewing the below official
   WordPress.org guide:
   [https://make.wordpress.org/core/handbook/references/php-compatibility-and-wordpress-versions/](https://make.wordpress.org/core/handbook/references/php-compatibility-and-wordpress-versions/)
 * While we do review the plugin to ensure compatibility with the latest versions,
   we also have some external libraries in use that can also trigger such warnings
   if these libraries don’t explicitly provide full support for PHP 8.4, and we 
   also must consider support for older PHP versions, many of which users have active.
 *  I also went ahead and created a GitHub issue for the team to review based on
   your topic:
   [https://github.com/google/site-kit-wp/issues/10719](https://github.com/google/site-kit-wp/issues/10719)
 * I’ll make the team aware of this. In the meantime, if you find any unusual behavior,
   or something not working as expected based on PHP8.4, do let me know. Thank you.
 *  Plugin Support [James Osborne](https://wordpress.org/support/users/jamesosborne/)
 * (@jamesosborne)
 * [11 months, 1 week ago](https://wordpress.org/support/topic/deprecated-warnings-on-php-8-4/#post-18463027)
 * Just to let you know that we are making changes to the plugin to ensure this 
   deprecation error no longer exists. Many thanks for reporting this.
 * I’ll keep you updates once this update is live. Thank you.

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

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

 * ![](https://ps.w.org/google-site-kit/assets/icon-256x256.png?rev=3141863)
 * [Site Kit by Google - Analytics, Search Console, AdSense, Speed](https://wordpress.org/plugins/google-site-kit/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/google-site-kit/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/google-site-kit/)
 * [Active Topics](https://wordpress.org/support/plugin/google-site-kit/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/google-site-kit/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/google-site-kit/reviews/)

 * 2 replies
 * 2 participants
 * Last reply from: [James Osborne](https://wordpress.org/support/users/jamesosborne/)
 * Last activity: [11 months, 1 week ago](https://wordpress.org/support/topic/deprecated-warnings-on-php-8-4/#post-18463027)
 * Status: not resolved