There has been a critical error on this website. Please check your site admin em

Thanks for reaching out @startechmarketing. So we can determine more on this please share the following:

1. Your Site Health information. You can use this form to share privately if preferred.??
2. Has this only started to occur recently, such as after updating to the latest version of Site Kit?
3. Do you see any loss of functionality within Site Kit, or is this just a message you receive via email from WordPress

Let me know if you have any questions with the above.

I don’t know what caused it, yes it is a new bug, but today dashboard loaded and I am disconnected. Then when I connect, i get the error

I created an error log for you:
[02-Aug-2023 12:39:11 UTC] PHP Deprecated: stripos(): Passing null to parameter #1 ($haystack) of type string is deprecated in …wp-content/plugins/google-site-kit/includes/Core/REST_API/REST_Routes.php on line 69

11 …wp-content/plugins/google-site-kit/includes/Core/Assets/Script_Data.php(51): call_user_func(Object(Closure), ‘googlesitekit-b…’) 12 [internal function]: Google\Site_Kit\Core\Assets\Script_Data->Google\Site_Kit\Core\Assets{closure}(‘googlesitekit-b…’) 13 …wp-content/plugins/google-site-kit/includes/Core/Assets/Asset.php(129): call_user_func(Object(Closure), ‘googlesitekit-b…’) 14 …wp-content/plugins/google-site-kit/includes/Core/Assets/Assets.php(1017): Google\Site_Kit\Core\Assets\Asset->before_print() 15 …wp-content/plugins/google-site-kit/includes/Core/Assets/Assets.php(1026): Google\Site_Kit\Core\Assets\Assets->run_before_print_callbacks(Object(WP_Scripts), Array) 16 …wp-content/plugins/google-site-kit/includes/Core/Assets/Assets.php(1026): Google\Site_Kit\Core\Assets\Assets->run_before_print_callbacks(Object(WP_Scripts), Array) 17 …wp-content/plugins/google-site-kit/includes/Core/Assets/Assets.php(1026): Google\Site_Kit\Core\Assets\Assets->run_before_print_callbacks(Object(WP_Scripts), Array) 18 …wp-content/plugins/google-site-kit/includes/Core/Assets/Assets.php(156): Google\Site_Kit\Core\Assets\Assets->run_before_print_callbacks(Object(WP_Scripts), Array) 19 …wp-includes/class-wp-hook.php(308): Google\Site_Kit\Core\Assets\Assets->Google\Site_Kit\Core\Assets{closure}(”)

8 …wp-content/plugins/google-site-kit/includes/Core/Assets/Assets.php(728): Google\Site_Kit\Core\Assets\Assets->get_product_base_paths() 9 …wp-content/plugins/google-site-kit/includes/Core/Assets/Assets.php(357): Google\Site_Kit\Core\Assets\Assets->get_inline_base_data() 10 [internal function]: Google\Site_Kit\Core\Assets\Assets->Google\Site_Kit\Core\Assets{closure}(‘googlesitekit-b…’) 11 …wp-content/plugins/google-site-kit/includes/Core/Assets/Script_Data.php(51): call_user_func(Object(Closure), ‘googlesitekit-b…’) 12 [internal function]: Google\Site_Kit\Core\Assets\Script_Data->Google\Site_Kit\Core\Assets{closure}(‘googlesitekit-b…’) 13 …wp-content/plugins/google-site-kit/includes/Core/Assets/Asset.php(129): call_user_func(Object(Closure), ‘googlesitekit-b…’) 14 …wp-content/plugins/google-site-kit/includes/Core/Assets/Assets.php(1017): Google\Site_Kit\Core\Assets\Asset->before_print() 15 …wp-content/plugins/google-site-kit/includes/Core/Assets/Assets.php(1026): Google\Site_Kit\Core\Assets\Assets->run_before_print_callbacks(Object(WP_Scripts), Array) 16 …wp-content/plugins/google-site-kit/includes/Core/Assets/Assets.php(1026): Google\Site_Kit\Core\Assets\Assets->run_before_print_callbacks(Object(WP_Scripts), Array) 17 …wp-content/plugins/google-site-kit/includes/Core/Assets/Assets.php(1026): Google\Site_Kit\Core\Assets\Assets->run_before_print_callbacks(Object(WP_Scripts), Array) 18 …wp-content/plugins/google-site-kit/includes/Core/Assets/Assets.php(156): Google\Site_Kit\Core\Assets\Assets->run_before_print_callbacks(Object(WP_Scripts), Array) 19 …wp-includes/class-wp-hook.php(308): Google\Site_Kit\Core\Assets\Assets->Google\Site_Kit\Core\Assets{closure}(”)

Thanks for the update @startechmarketing, appreciate you sharing the additional information. Deprecation notices can occur with the latest version of PHP. There is an open GitHub issue which is currently being worked on regarding this. Once complete you should no longer encounter these errors. You’ll find out more on this below:
https://github.com/google/site-kit-wp/issues/7147

Note also that despite this error, you shouldn’t encounter any loss of functionality with Site Kit. Let me know if this is not the case and we can investigate this further.

Hi thanks for your help I read github I have no clue how to fix it and I uninstalled and reinstalled site kit it crashed the site again.

WPML says this I downgraded, I get less errors and site does not crash

https://wpml.org/errata/site-kit-by-google-uncaught-typeerror-illegal-offset-type-in-isset-or-empty-in/

Thanks for the update @startechmarketing. If you’re a WPML user then we are working on a fix for this. As we didn’t receive your Site Health information I wasn’t able to check your active plugins. You can follow the following GitHub issue for updates on this:
https://github.com/google/site-kit-wp/issues/7389

WPML themselves are also working on a fix for this. We’ll let you know here as soon as we have an update. For the moment, as you’ve already downgraded to Site Kit 1.105.0 your should not encounter any such errors.

Yes we are WPML but even with that plugin deactivated we had the error. WPML new about the error but maybe is related. Ok I wait for update thank you

Correct @startechmarketing, from reviewing the error with the team there will be a fix out both on the Site Kit site and also with WPML. We’ll let you know once a fix is out. Thank you!

Hello thanks, I have updates from Wpml but still crashes and also is a conflict with Rank Math SEO plugin but only the string translation plugin and only backend wp-admin front end has no critical error and no 500 server error

only things that have changed is wordpress and plugin updates please advise the status of your fix thanks

We certainly will inform you once a fix is out @startechmarketing. Thanks also for the additional information.

Just to let you know that we released Site Kit 1.107.0, which has a fix out for this @startechmarketing. Please upgrade to this latest version and your previous version of PHP if you wish, and which point the error should no longer occur.

Let me know if you have any questions on this.

I did, we still get errors, but I don’t know if this casues WPML string translation to fail – we think the conflict is yours, Rankmath and WPML string translation

[21-Aug-2023 07:25:55 UTC] PHP Deprecated: stripos(): Passing null to parameter #1 ($haystack) of type string is deprecated in /home4/…..wp-content/plugins/google-site-kit/includes/Core/REST_API/REST_Routes.php on line 69

Thanks for the update @startechmarketing. This latest PHP warning differs to the WPML related error initially reported. We are working on a fix to this, with more details available below:
https://github.com/google/site-kit-wp/issues/7147

Note that this is only a warning related to the latest version of PHP, which therefore doesn’t impact any Site Kit functionality.