• Resolved clhalsell

    (@clhalsell)


    All pages, when I try to use SiteKit, give me this error. It has worked fine for months so I’m not sure what changed.

    a is null
    
        in GoogleChart
        in div
        in Cell
        in div
        in ForwardRef
        in div
        in ForwardRef
        in SearchConsoleStats
        in div
        in div
        in Widget
        in WithWidgetSlug(Widget)
        in SearchFunnelWidget
        in WidgetRenderer
        in div
        in Cell
        in WidgetCellWrapper
        in div
        in ForwardRef
        in div
        in div
        in ForwardRef
        in WidgetAreaRenderer
        in div
        in WidgetContextRenderer
        in DashboardMainApp
        in DashboardEntryPoint
        in RestoreSnapshots
        in ErrorHandler
        in StrictMode
        in Root

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

Viewing 10 replies - 1 through 10 (of 10 total)
  • Plugin Support James Osborne

    (@jamesosborne)

    Hi @clhalsell,

    Thanks for reaching out. We’re aware there there may be some third party plugins that can cause conflicts with the Site Kit dashboard, since Site Kit 1.79.0. With that please share your Site Health information and we can check your current WordPress environment. You can use this form to share privately if preferred.

    After sharing I can check the same plugins which you have active, before checking this with the team, and providing you with some troubleshooting suggestions.

    Looking forward to hearing from you.

    Plugin Support James Osborne

    (@jamesosborne)

    Hi there @clhalsell,

    We’ve received a Site Health information response referencing this support topic. Assuming this was from you, can you follow the steps below, which can help rule out third party plugin conflicts? While you’re doing so I’ll also set up a WordPress environment similar to your own to try and recreate the same error:

    1. Login to your site from a Chrome browser incognito window
    2. Install and activate the Health Check & Troubleshooting plugin.
    3. Navigate to “Plugins > Health Check & Troubleshooting > Troubleshoot”.
    4. 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”
    5. View your Site Kit dashboard once more

    Let me know if the same error appears while in troubleshooting mode, or inform me if you have any questions with the above. I’ll also let you know of any status update on a similar environment to your own.

    Plugin Support James Osborne

    (@jamesosborne)

    @clhalsell Note that I’m also seeing a /?v=cd6a9bd2a175 path added to the end of every URL on your site. Are you familiar with this?

    Thread Starter clhalsell

    (@clhalsell)

    I just now submitted my sitehealth report via the form. The info you’re referring to wasn’t me. I’ll be away from service until Monday, but thank you so much for all of your help and your quick response.

    Plugin Support James Osborne

    (@jamesosborne)

    Thanks for the update @clhalsell. From checking your own site details nothing obvious stands out that be resulting in this dashboard error. The next steps are to rule out possible third party plugin conflicts. To do so please follow the steps below – when you’re back on Monday:

    1. Login to your site from a Chrome browser incognito window
    2. Install and activate the Health Check & Troubleshooting plugin.
    3. Navigate to “Plugins > Health Check & Troubleshooting > Troubleshoot”.
    4. 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”
    5. View your Site Kit dashboard once more

    I’ll also perform a check with the plugins and theme you have active in the meantime. Let me know how you get on.

    Thread Starter clhalsell

    (@clhalsell)

    Ok, I did all of that and the SiteKit dashboard looks fine while it’s in troubleshooting mode. What does that mean?

    Plugin Support James Osborne

    (@jamesosborne)

    Many thanks for the follow up @clhalsell, great to hear that! We were just discussing this case today.

    What does that mean?

    If the issue no longer appears while in troubleshooting mode this indicates a third party or theme related conflict. To narrow this down, and determine the particular conflict, what you can do is re-enable the other plugins, one by one, while remaining in troubleshooting mode. I have a summary of the steps below, with more details on the plugin website:

    1. Navigate to “Plugins > Health Check & Troubleshooting > Troubleshoot”. .
    2. Confirm once more that the error doesn’t appear by visiting your Site Kit dashboard (maybe from a different tab)
    3. From back in your Health Check plugin click on the “Available Plugins” tab at the top right enable your other plugins one by one, while rechecking your Site Kit dashboard each time. You’ll need to refresh/reload the Site Kit dashboard after enabled each plugin.
    4. As soon as the error appears please inform me of the plugin you just activated. If at no stages does the error appear activate your current Mai Achieve while in troubleshooting mode, before checking your Site Kit dashboard once more

    Let me know how you get on with the above check, or ask if you have any questions!

    Note that I also have an environment set up similar to your own, although without the commercial theme and plugins you have active. With the other plugins I haven’t been able to recreate the same, so I do suspect something with your themes or theme related plugins.

    Thread Starter clhalsell

    (@clhalsell)

    Ok, the error came back when I enabled Mai Icons.

    Thread Starter clhalsell

    (@clhalsell)

    Well, now it looks like it’s working. I must have missed an update or something?

    Plugin Support James Osborne

    (@jamesosborne)

    Many thanks for the update @clhalsell, great to hear that you were able to determine the cause, with the error re-appearing when you enabled the Mai Icons plugin, which is related to your theme.

    Well, now it looks like it’s working. I must have missed an update or something?

    If the error no longer appears now, even with the Mai Icons active, you could be correct. From re-reviewing your Site Health information it does look like you initially missed the Site Kit 1.80.0 update, good spot! We did make changes to the plugin since 1.79.0 based no user reports of possible conflicts, which I suspect you were impacted by.

    If you run into any further errors or warnings be sure to reach out. Thank you!

Viewing 10 replies - 1 through 10 (of 10 total)
  • The topic ‘SiteKit Encountered Error’ is closed to new replies.