• Resolved pollarddaniel8

    (@pollarddaniel8)


    after the recent update of site kit I get this error on the dashboard page

    Cannot read properties of undefined (reading 'map') in WidgetAreaRenderer in div in WidgetContextRenderer in DashboardMainApp in DashboardEntryPoint in RestoreSnapshots in ErrorHandler in ThemeProvider in StrictMode in Root

    and this when I try to access the settings page

    An error occurred while running 'mapSelect': Cannot read properties of null (reading 'name')The error may be correlated with this previous error:TypeError: Cannot read properties of null (reading 'name') at Oe (https://creepyshed.co.uk/wp-includes/js/dist/data.min.js?ver=7c62e39de0308c73d50c:2:20069) at select (https://creepyshed.co.uk/wp-includes/js/dist/data.min.js?ver=7c62e39de0308c73d50c:2:21232) at Object.select (https://creepyshed.co.uk/wp-includes/js/dist/data.min.js?ver=7c62e39de0308c73d50c:2:22352) at Module.ct (https://creepyshed.co.uk/wp-includes/js/dist/data.min.js?ver=7c62e39de0308c73d50c:9:4129) at c (https://creepyshed.co.uk/wp-content/plugins/google-site-kit/dist/assets/js/googlesitekit-vendor-c0361f61e19f0ac5e729.js:7:491719) at https://creepyshed.co.uk/wp-content/plugins/google-site-kit/dist/assets/js/googlesitekit-vendor-c0361f61e19f0ac5e729.js:7:492174 at Object.current (https://creepyshed.co.uk/wp-content/plugins/google-site-kit/dist/assets/js/googlesitekit-settings-f5792d29fc29a20b0ba2.js:74:32241) at e (https://creepyshed.co.uk/wp-content/plugins/google-site-kit/dist/assets/js/googlesitekit-vendor-c0361f61e19f0ac5e729.js:7:171945) at https://creepyshed.co.uk/wp-content/plugins/google-site-kit/dist/assets/js/googlesitekit-vendor-c0361f61e19f0ac5e729.js:7:172060 at Ii (https://creepyshed.co.uk/wp-content/plugins/google-site-kit/dist/assets/js/googlesitekit-vendor-c0361f61e19f0ac5e729.js:7:741060)Original stack trace: in Header in div in SettingsActiveModule in div in Layout in SettingsActiveModules in Route in Switch in SettingsModules in div in Cell in div in Row in div in Grid in div in SettingsApp in withRouter(SettingsApp) in Router in HashRouter in RestoreSnapshots in ErrorHandler in ThemeProvider in StrictMode in Root

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

Viewing 14 replies - 16 through 29 (of 29 total)
  • Plugin Support James Osborne

    (@jamesosborne)

    Very interesting, thanks for sharing this @pollarddaniel8. Were you able to check with your .htaccess file refreshed, or with Cloudflare deactivated?

    Rather than ask you to perform some additional checks at this time, we’ll review this further with the team. If you are happy to continue troubleshooting, there are additional checks we can suggested but we can check this with the team first, rather than have you unnecessarily taking up time. I added the checks we already performed to the below GitHub issue from where we can keep track of this:
    https://github.com/google/site-kit-wp/issues/10551

    Feel free to perform some of the additional checks listed there, and do let me know if you happened to perform a check with with your htaccess file refreshed and with Cloudflare deactivated.

    Thread Starter pollarddaniel8

    (@pollarddaniel8)

    I’ve not had time to cloudflare, many thanks for looking in to this.

    i did this at step “As I noticed some additional .htaccess rules, can you visit your permalinks page (Settings > Permalinks) and press the “Save change” button? This will recreate a fresh .htaccess file for you. I ask as rules applied at .htaccess level can impact Site Kit behavior. “

    no change to the problem

    Plugin Support James Osborne

    (@jamesosborne)

    Thanks for the additional insights @pollarddaniel8.

    I’ve not had time to cloudflare, many thanks for looking in to this.

    We don’t suspect it’s related to Cloudflare based on the very useful console errors you providers, but always worth a check.

    i did this at step “As I noticed some additional .htaccess rules, can you visit your permalinks page (Settings > Permalinks) and press the “Save change” button? This will recreate a fresh .htaccess file for you. I ask as rules applied at .htaccess level can impact Site Kit behavior. “

    Thanks for checking this. That’s one more potential cause we can rule out. At this point we do suspect a host related block. Are you able to set up another WordPress site on a newly created subdirectory, from where we can check further?

    Another possibility which, may help us determine the cause, is to do as you did one more with setting up Site Kit, but with only Site Kit active using the Health Check and Troubleshooting, and looking for any changes in your browser console with Google Analytics deactivated. The steps to do so are below:

    1. Login to your live 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. Attempt to set up Site Kit once more (without Google Analytics).
    6. Check for any browser console errors and share here or using the form. Feel free to share a screen recording with your browser console log open if you prefer, as an alternative to screenshots.

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

    Thread Starter pollarddaniel8

    (@pollarddaniel8)

    i did the above, using my phone so no access to the console but, with the plugin enabled the site kit worked as it should, on turning off the trouble shooting plugin the errors returned. I’ll be back at my computer in a bit so I can check properly

    Thread Starter pollarddaniel8

    (@pollarddaniel8)

    In troubleshooting mode I’ve gone though all the plugins the one below is the only one the creates an error when enabled. If I enable all apart from this one all works fine

    Easy Image Collage

    Create beautiful responsive image collages for all your posts and pages

    Version 1.13.6 | By Bootstrapped Ventures | View details

    Plugin Support James Osborne

    (@jamesosborne)

    Nice troubleshooting @pollarddaniel8! Based on this, please do check from your regular browser on desktop when you have time. From reviewing your Site Health information there are some MU plugins active, possible host related, along with MalCare WordPress Security Plugin. There may be some configurations applicable with these plugins that are impacting Site Kit requests.

    If the same error not longer occurs, and Site Kit works as expected once more from your regular browser session on desktop, you can enable each plugin one by one while in troubleshooting mode – checking the Site Kit dashboard each time. This will help narrow down a possible conflicting plugin. Let me know if you’re able to do this, or ask if you have any questions. I’m also going to review the configurations possible with some of your plugins in the meantime. Thank you.

    Plugin Support James Osborne

    (@jamesosborne)

    Update: It looks like you discovered the possible cause. I’m testing this plugin at present and given I don’t encounter the same, can you try to reset the Easy Image Collage Settings, as highlighted below?

    If the same occurs after resetting, you’re probably facing a multi-party plugin conflict. Let me know how it goes, while I’ll continue testing on my side.

    Thread Starter pollarddaniel8

    (@pollarddaniel8)

    i have done the above and still the same result

    Plugin Support James Osborne

    (@jamesosborne)

    Thanks for checking. Just to be certain, please share the following:

    1. When using the Health Check & Troubleshooting plugin, with only Site Kit and Easy Image Collage present, the same errors occur on the Site Kit dashboard?
    2. Do you encounter any errors when not using the Health Check and Troubleshooting plugin, but with the Easy Image Collage plugin temporarily deactivated?

    Thread Starter pollarddaniel8

    (@pollarddaniel8)

    Q When using the Health Check & Troubleshooting plugin, with only Site Kit and Easy Image Collage present, the same errors occur on the Site Kit dashboard?

    A Yes

    Q Do you encounter any errors when not using the Health Check and Troubleshooting plugin, but with the Easy Image Collage plugin temporarily deactivated?

    A no

    Plugin Support James Osborne

    (@jamesosborne)

    Thanks for the additional information @pollarddaniel8. We have been able to confirm the conflict, much in part to your very useful insights. I’ll be providing you with a workaround solution shortly, so you can use both plugins at once. The issue is that some codes related to a library is used by Easy Image Collage (and possibly other plugins). Some code within this library matches what is used by Site Kit.

    Please allow me some time to share a solution here. Note that in the meantime, you can temporarily deactivate East Image Collage if you wish to view the Site Kit dashboard. I’ll follow up with you here shortly. Thanks again!

    Thread Starter pollarddaniel8

    (@pollarddaniel8)

    Glad I could be of help, good luck with your fix

    Plugin Support James Osborne

    (@jamesosborne)

    Thanks for your patience @pollarddaniel8. This error is indeed due to a conflict with the Vafpress Framework, a project which is no longer maintained for many year, in use by Easy Image Collage. While there is little we can do with regards to usage of this framework by other plugins or themes, the workaround below should do the trick:

    1. Download this mini-plugin
    2. Upload and activate the plugin (via the plugin upload method)
    3. Check for the same issue when activating both East Image Collage and Site Kit. You will need to keep this plugin active in the event that the conflict does return (as the framework used by the conflicting plugin may remain in use).

    Do let me know if you have any questions on the above, and it would be great if you could confirm that the above does address the conflict you raised.

    Plugin Support James Osborne

    (@jamesosborne)

    As we didn’t receive a response I’ll mark this as resolved. Feel free to open a new support topic if you continue to encounter issues, or reopen this topic and we’d be happy to assist.

Viewing 14 replies - 16 through 29 (of 29 total)

The topic ‘Error after update’ is closed to new replies.