update php and error with Site Kit

Thanks for reaching out @eliot1988.

Based on the screenshots you provided, these depreciation notices are appearing when using the admin toolbar, meaning they are only visible for admins.

Note also that such depreciate notices are normal and expected, given WordPress support for PHP8 is still in a beta stage. You’ll find out more on this below:
https://make.www.ads-software.com/core/handbook/references/php-compatibility-and-wordpress-versions/

Note also that while depreciation warning may appear to stem from Site Kit, it’s likely that many such notices are coming from how Site Kit interacts with WordPress core. Once WordPress fully supports PHP8* you should no longer encounter these depreciation notices. We do regular testing with PHP8 and all Site Kit functionality should work as expected. If you find anything unusual with regards Site Kit behavior, other than depreciation warnings, let me know and I’d be happy to investigate this further.

thank you very much!

If I do this? there should be no errors as you can see in the image, maybe the errors will go away?

https://ibb.co/NVSPZmh

No probelem @eliot1988.

The below is enough to ensure PHP errors are not output on the front end of your site.
ini_set('display_errors','Off');

Error displaying is usually disabled by default. From reviewing the screenshot you provided earlier the error may be appearing within a tagDivCSSAnalyzier admin toolbar feature. It’s possible that depreciation notices may appear within this, but you can reach out to tagDiv for support on this.

You can also test visiting your site as non logged in user to ensure you don’t see any PHP errors output.

Let me know if you have any further questions on this.

ok! thank you very much!!

No problem at all. Be sure to reach out if you have any further questions.

when I disable the site kit plugin and install the latest version of php I don’t get any errors.. So it has to do with this plugin… What can I do in this case?

@eliot1988 As mentioned above, Site Kit uses many of WordPress core hooks and actions. As PHP8* remains in Beta support at WordPress level at this time (Compatibility list), depreciation warnings and notice are expected.

While you can safely ignore these warnings, be aware that these don’t have any impact on plugin functionality. As long as you’re not outputting PHP warnings on the front end of your site no visitors will be able to view these warnings.

thanks!!

No problem. Have a great weekend.

@jamesosborne I would like to follow up on this.

Obviously we can hide deprecation notices, but those of us working in dev environments are likely to keep error reporting on to catch anything we need to be aware of as we continue adapting to the latest versions of PHP, and deprecation notices cause a signal-to-noise ratio problem in dev environments. Further, some plugin developers are one-person teams who may not be formally testing newer versions of PHP, and bringing deprecations to their attention before they start actually breaking sites in newer PHP versions is good for the ecosystem as a whole.

Re: WordPress core support – the “beta” designation for WordPress core support will indefinitely exist for PHP 8.0 and greater given how the core team has defined their “beta” support – in that they’ve said that WordPress core is fully compatible, but they can’t vouch for plugins. So they’ve called it “beta” support. WordPress 6.2, in particular, resolved all outstanding PHP 8.1 deprecation notices in core with the update to Requests 2.0.

Would love to see deprecation notices resolved in this plugin, or at least the issue tracked in the GitHub issue tracker and not closed as “Complete” when it isn’t really.

@eclev91 Many thanks for the input and further insights and information regarding WordPress Core’s “Beta” status. I’ll bring this up with the team once more. I’m aware there are regular checks with the latest version of PHP and the plugin, but I will report back to you here with any updates.

@eclev91 I’m just following up with you let you know that I checked with the team regarding the deprecation notice in this support topic. That specific notice should not longer appear with recent changes to the plugin.

If you’re running into this or any other deprecation notice, please share this by opening a support topic and we can investigate any individual errors. We do have regular testing with PHP8 and we’re happy to investigate any errors that may arise from your testing. I’ll also put some time aside to check this next week.

Would love to see deprecation notices resolved in this plugin, or at least the issue tracked in?the GitHub issue tracker?and not closed as “Complete” when it isn’t really.

That deprecation notice should no longer appear, however, if you do find otherwise let me know and I’ll check this with the team.