• Resolved jansudek

    (@jansudek)


    Hello, my page shown some E_DEPRECATED warnings, can you fix it to not shown ?

    E_DEPRECATED htmlspecialchars(): Passing null to parameter #1 ($string) of type string is deprecated in file /wp-content/plugins/google-site-kit/includes/Core/Authentication/Clients/OAuth_Client.php on line 403
    
    E_DEPRECATED strtotime(): Passing null to parameter #1 ($datetime) of type string is deprecated in file /wp-content/plugins/google-site-kit/includes/Modules/Analytics_4/Report.php on line 112
    E_DEPRECATED htmlspecialchars(): Passing null to parameter #1 ($string) of type string is deprecated in file /wp-content/plugins/google-site-kit/includes/Core/Authentication/Setup.php on line 234

    Site Kit by Google v1.124.0
    PHP 8.1

Viewing 8 replies - 1 through 8 (of 8 total)
  • Plugin Support James Osborne

    (@jamesosborne)

    Thanks for reaching out @jansudek. The deprecation notices you’re encountering don’t impact any Site Kit functionality and are related to some of the dependency libraries used by Site Kit, as opposed to coming from the plugin itself. They can be disregarded for the time being, as we are updating these libraries shortly, at which stage they should no longer occur.

    You can find more details on where we reported this over?on the Google Client Library GitHub repository, where they confirmed this has since been addressed.

    In relation to your query about not displaying these, I suspect you have a setting in your wp-config file or maybe from a third party plugin to ensure errors are printed. While you can’t disable these from within Site Kit, have you reviewed your wp-config file? You can also disable the display of errors by adding a configuration as per this guide.

    Thread Starter jansudek

    (@jansudek)

    thanks for reply, but this is not that problem google/apiclient-services “Dynamic property declarations in PHP 8.2” .. this is another E_DEPRECATED errors in PHP 8.1 .. thanks for fix it..

    Plugin Support Adam Dunnage

    (@adamdunnage)

    @jansudek I just wanted to check in here and follow up with you to see if you were able to hide these from displaying? Did following the guide that James shared with you work in this instance?

    Can I just also check that you are not seeing any noticeable impact on the Site Kit plugin and how it performs for you?

    Thread Starter jansudek

    (@jansudek)

    thanks for your care .. so its only in debug.log , errors are hidden .. but hidden errors is not fixed errors .. it is only deprecated errors which not impact to sitekit working ..

    so thanks to delegate someone to fix that PHP deprecated notices and fix that errors ..

    Plugin Support James Osborne

    (@jamesosborne)

    Thanks for the update @jansudek. I’ll check this with the team and report back to you here. You are correct that the deprecation notices you highlighted are not specific to third party dependencies, however, I will need to check this further.

    I’ll report back to you once I have more information on this.

    Plugin Support James Osborne

    (@jamesosborne)

    Just to keep you updated on this @jansudek, we created the following GitHub issue based on your findings:
    https://github.com/google/site-kit-wp/issues/8589

    Many thanks for raising this here in the forums. Feel free to subscribe to that issue for updates.

    Plugin Support James Osborne

    (@jamesosborne)

    @jansudek Thanks for your patience on this while we perform some checks. As I’ve been unable to encounter these same deprecation notices so far, can you share the following:

    1. Do you encounter these notices consistently, each time you the Site Kit dashboard?
    2. Your Site Health information. You can use this form to share privately if preferred.?This will allow us to check your Google Analytics settings, with the warnings likely coming from a GA4 configuration.

    Once we have the above we may be able to determine more on this and ensure they no longer occur. Let me know if you have any questions with the above.

    Plugin Support James Osborne

    (@jamesosborne)

    Just to let you know that we have a fix out in Site Kit for this issue, with more details added to this GitHub issue. Thank you for bringing this to our attention.

Viewing 8 replies - 1 through 8 (of 8 total)
  • You must be logged in to reply to this topic.