Thanks for reaching out. As we’re currently looking into other reports of this can you share your Site Health information and we investigate this further? You can use this form to share privately if preferred.
After sharing please perform the following checks, to see if the same error appears when other plugins are temporarily deactivated.
- Login to your site from a Chrome browser incognito window
- Install and activate the Health Check & Troubleshooting plugin.
- Navigate to “Plugins > Health Check & Troubleshooting > Troubleshoot”.
- From the same screen click on the “Available Plugins” tab at the top right and then click on the “Enable” option next to “Site Kit by Google”
- Check for the same error when visiting your Site Kit dashboard once more
Let me know how you get on with the above.
Hi @jamesosborne,
I followed all the steps you mentioned. Thank you very much for sharing all the steps with clarity and simplicity.
So, in the incognito window, there is no error.
But when I got back to my site on the normal window, I again encountered the same error.
Cannot read properties of undefined (reading 'load')
in Script
in GoogleChartLoader
in ContextProvider
in Chart
in div
in GoogleChart
in div
in Cell
in div
in Row
in div
in Grid
in Stats
in div
in div
in Widget
in WithWidgetSlug(Widget)
in ModuleOverviewWidget
in WidgetRenderer
in div
in Cell
in WidgetCellWrapper
in div
in Row
in div
in div
in Grid
in WidgetAreaRenderer
in div
in WidgetContextRenderer
in ModuleApp
in GoogleSitekitModule
in RestoreSnapshots
in ErrorHandler
in Root
Please help.
Regards,
Dhara
This is super useful. Many thanks for sharing. As we’re still investigating this and based on your checks can you provide the following information:
- When you mentioned this error does appear from a regular browser session (and not incognito) is this when in troubleshooting mode as per the above?
- Can you share your Site Health information so we can inspect your current WordPress environment? You can use this form to share privately if preferred.
As we’re presently investigating this the above information – should you be able to provide it, would be of great use. Hopefully we can then determine the cause, which based on your findings indicates a possible third party plugin conflict.
Hi James,
Will you pls guide me on how to check and send the site health information?
@gujjumitro Not a problem, you can navigate to “Tools > Site Health > info” from within your wp-admin dashboard and then press the “Copy site info to clipboard” button.
After doing so you can paste the results into a response here or use our form to share privately if preferred. You’ll also find a screenshot showing the steps involved when using our form.
I have submitted the site health via the form. Please check.
Excellent, thank you! While I check your details and share this with the team who are currently looking into this can you share whether this error appears consistently?
If so can you share the following:
- At what point you see this error (ie. Each time you visit the primary Site Kit dashboard window)
- Do you you encounter this when checking from a Chrome browser incognito window?
Hi James,
I encounter this problem :
Each time I visit the primary Site Kit dashboard window and check the data for the latest 7 days.
Yes I encounter this when checking from a Chrome browser incognito window.
Thank you for your prompt response. I hope all these questions and answers result in a permanent solution.
Appreciate you sharing your findings, very useful indeed! I’ll add this to the related GitHub issue, from which we’re investigating reports of this error.
While we’ll keep you updated with any progress on this if you could also share the below this may help us determine more on this:
- When you mention this occurs using the 7 day reporting period can you share whether you encounter this when switching reporting periods?
- Can you share your current hosting provider?
If you’d like to share your experience in the form of a video recording using a service such as Loom or RecordIt I can bring this to the attention of our engineers. Really appreciate your help on this as we try to determine the cause, with other users also impacted.
@gujjumitro Just to let you know that Site Kit version 1.46.0 has been released, with a solution in place for this error which you reported. Can you update to this latest version and confirm that you no longer encounter this when visiting your Site Kit dashboard?
