Hi @rleach,
Thanks for reaching out. We’re aware of one cause of this error, a third party plugin conflict, with a plugin that uses the Google Charts library on all wp-admin URLs. If you’re using RegistrationMagic you’ll find out more on this here. Updating the RegistrationMagic plugin will resolve this, with a recent release having a fix in place for this.
If you’re not using RegistrationMagic please share your Site Health information so I can check your active plugins, and provide you with some troubleshooting suggestions.
Many thanks for sharing your Site Health information. From reviewing this it doesn’t look like you have the same RegistrationMagic plugin active. May I ask you if the same occurs if you temporarily deactivate the following plugins:
- WP Dating
- WPDating Elementor Add-on
I ask as we’ve encountered the same error recently, from a user who had the same plugins active. If so, I’ll then provide some troubleshooting suggestions to rule out possible third party plugin and theme related conflicts.
@rleach Just following up with you to check whether the same issue remains on your site? If so please follow the steps below:
- 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”
- View your Site Kit dashboard once more
Let me know if you have any questions with the above.
Thread Starter
rleach
(@rleach)
Thanks. That solved the issue. Appreciate your help.
Glad to hear it @rleach, many thanks for the update.
Note that if in Health Check & Troubleshooting mode, this disabled all other plugins from running. For that reason you may encounter the error once more, outside of troubleshooting mode. For that reason, should the issue arise once more, you can pinpoint the exact plugin causing the issue by following the troubleshooting steps added to the Site Kit plugin website.
If you are able to pinpoint the exact plugin causing the conflict I can perform more testing on this.