Error on debug pages

  • Resolved blackdeth73

    (@blackdeth73)


    3 years, 1 month ago

    Warning: Undefined array key "search-console" in /bitnami/wordpress/wp-content/plugins/google-site-kit/includes/Core/Util/Debug_Data.php on line 406

Warning: Trying to access array offset on value of type null in /bitnami/wordpress/wp-content/plugins/google-site-kit/includes/Core/Util/Debug_Data.php on line 406

Warning: Undefined array key "search-console" in /bitnami/wordpress/wp-content/plugins/google-site-kit/includes/Core/Util/Debug_Data.php on line 414

Warning: Trying to access array offset on value of type null in /bitnami/wordpress/wp-content/plugins/google-site-kit/includes/Core/Util/Debug_Data.php on line 414

Warning: Undefined array key "adsense" in /bitnami/wordpress/wp-content/plugins/google-site-kit/includes/Core/Util/Debug_Data.php on line 406

Warning: Trying to access array offset on value of type null in /bitnami/wordpress/wp-content/plugins/google-site-kit/includes/Core/Util/Debug_Data.php on line 406

Warning: Undefined array key "adsense" in /bitnami/wordpress/wp-content/plugins/google-site-kit/includes/Core/Util/Debug_Data.php on line 414

Warning: Trying to access array offset on value of type null in /bitnami/wordpress/wp-content/plugins/google-site-kit/includes/Core/Util/Debug_Data.php on line 414

Warning: Undefined array key "analytics" in /bitnami/wordpress/wp-content/plugins/google-site-kit/includes/Core/Util/Debug_Data.php on line 406

Warning: Trying to access array offset on value of type null in /bitnami/wordpress/wp-content/plugins/google-site-kit/includes/Core/Util/Debug_Data.php on line 406

Warning: Undefined array key "analytics" in /bitnami/wordpress/wp-content/plugins/google-site-kit/includes/Core/Util/Debug_Data.php on line 414

Warning: Trying to access array offset on value of type null in /bitnami/wordpress/wp-content/plugins/google-site-kit/includes/Core/Util/Debug_Data.php on line 414

    An error is displayed on the Admin > Site Health screen.

    The page I need help with: [log in to see the link]

Viewing 15 replies - 1 through 15 (of 16 total)
1 2
  • Plugin Support Adam Dunnage

    (@adamdunnage)

    3 years, 1 month ago

    @blackdeth73 thanks for getting in touch. To help you with this, could you share some more information:

    1. Your Site Health information. You can use this form to share privately if preferred. Please also include your hosting provider here
    2. Does this have any impact on how Site Kit is working for you?
    3. Do you see any console errors alongside this?
    4. Do you see any other warnings or errors when checking your Site Health status (Tools > Site Health > Status)? Such errors may include REST endpoint

    Any screenshots or recordings you can provide are also welcome. Let me know if you have any questions.

    Thread Starter blackdeth73

    (@blackdeth73)

    3 years, 1 month ago

    @adamdunnage

    Hello, thanks for the answer.
    The form has been submitted. Please confirm.

    Plugin Support James Osborne

    (@jamesosborne)

    3 years, 1 month ago

    Many thanks for the update @blackdeth73. While I suspect the issue you’re encountering is similar to that described on this related GitHub issue, in order to confirm this can you share whether this happened only after the latest plugin update, and whether you’ve been experiencing any errors on your wp-admin dashboard other than within the Site Health information page?

    Note that we also have a mini plugin which you can test if you wish, which is based on the above GitHub issue. To do so, please download and install the plugin as a standard WordPress plugin (using the upload method – Plugins > Install > Upload Plugin > Activate). After you install and activate this mini plugin it would be great if you could confirm that you no longer encounter the same when checking your Site Health information tab. 

    Let me know how you get on, or ask if you have any questions with the above mini plugin.

    Thread Starter blackdeth73

    (@blackdeth73)

    3 years, 1 month ago

    @jamesosborne

    PHP Multibyte String Polyfills After activating the plugin, the following error message is displayed.

    Fatal error: Uncaught ValueError: version_compare(): Argument #3 ($operator) must be a valid comparison operator in /bitnami/wordpress/wp-content/plugins/wp-mbstring-polyfill-master/wp-mbstring-polyfill.php:12 Stack trace: #0 /bitnami/wordpress/wp-content/plugins/wp-mbstring-polyfill-master/wp-mbstring-polyfill.php(12): version_compare() #1 /opt/bitnami/wordpress/wp-admin/includes/plugin.php(2314): include_once(‘…’) #2 /opt/bitnami/wordpress/wp-admin/plugins.php(192): plugin_sandbox_scrape() #3 {main} thrown in /bitnami/wordpress/wp-content/plugins/wp-mbstring-polyfill-master/wp-mbstring-polyfill.php on line 12

    Plugin Support James Osborne

    (@jamesosborne)

    3 years, 1 month ago

    Thanks for the update @blackdeth73, and sorry to hear you encountered errors upon install. Rather than using the plugin, do you have the ability to modify your PHP modules? If so, you can enable mbstring. After doing so, you should no longer encounter the errors previously reported, before installing the mini plugin.

    Let me know how you get on with the above.

    Thread Starter blackdeth73

    (@blackdeth73)

    3 years, 1 month ago

    @jamesosborne

    Thank you for answer. Could you please tell me how to enable mbstring? Hosting is using Lightsail.

    Plugin Support Adam Dunnage

    (@adamdunnage)

    3 years, 1 month ago

    @blackdeth73 I would recommend checking this with your hosting provider who should be able to guide you on this.

    Thread Starter blackdeth73

    (@blackdeth73)

    3 years, 1 month ago

    @adamdunnage

    It installs mbstring, but the error remains.

    Plugin Support Adam Dunnage

    (@adamdunnage)

    3 years, 1 month ago

    @blackdeth73 If both options you have tried above do not work the only other workaround at this time would be to revert back to the previous version of Site Kit 1.92.0.

    There is a fix for this which will be in the next release which will arrive next week so until then feel free to revert back to 1.92.0 until 1.94.0 is released with the fix.

    Plugin Support Adam Dunnage

    (@adamdunnage)

    3 years, 1 month ago

    @blackdeth73 Version 1.94.0 of Site Kit is now available which contains a fix for this issue. Please update to the latest version and let us know if you experience any further problems.

    Thread Starter blackdeth73

    (@blackdeth73)

    3 years, 1 month ago

    @adamdunnage

    error is the same. The error hasn’t gone away. The plugin version is 1.94.0.

    Plugin Support James Osborne

    (@jamesosborne)

    3 years, 1 month ago

    Thanks for the update @blackdeth73. As these are warnings and not errors that are output I wonder are they related to PHP8, which is still in Beta support with WordPress core.

    To troubleshoot this further, can you temporarily switch to PHP 7.4 and check for the same warnings?

    Thread Starter blackdeth73

    (@blackdeth73)

    3 years, 1 month ago

    @jamesosborne

    The error message is the same as the first time. Wasn’t this an mbstring problem from the beginning? If it is a php version problem, please solve it when it is updated.

    Plugin Support James Osborne

    (@jamesosborne)

    3 years, 1 month ago

    Thanks for the update @blackdeth73. I had suspected that you were encountered was related to a missing mbstring module, as per this GitHub issue, given it occurs from your wp-admin menu and started around the time of Site Kit 1.93.0. As this doesn’t seem to be the case I’ll need to check this with the team.

    I’ll report back to you here once I have an update from discussing this. Thank you!

    Plugin Support James Osborne

    (@jamesosborne)

    3 years, 1 month ago

    Thanks for your patience on this @blackdeth73. Based on your findings, we’ve been able to reproduce this and we’ve created the following GitHub issue:
    https://github.com/google/site-kit-wp/issues/6597

    We’ll work on this to ensure you encounter no further warnings. Note that these are warnings and they shouldn’t impact any Site Kit functionality. We’ll keep you updated on this once we have a fix in place. Thanks for reporting.

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

The topic ‘Error on debug pages’ is closed to new replies.