Stuck on Checking Compatibility

Thanks for reaching out @skredlemon. It sounds like your colleague has already set up the plugin successfully. In relation to any compatibility notice, these can occur in various circumstances, such as if you’re using an ad blocker or if there are issues with your WordPress REST API. So we can determine more on what’s happening in your case, please share the following:

1. Your Site Health information. You can use this form to share privately if preferred.?
2. Did you share a login with your colleague, or do you both have different administrator logins to the site?

Once we have the above we can advise on this further and hopefully ensure Site Kit works as expected for you. Let me know if you have any questions with the above.

Hi @jamesosborne, thank you for the quick response. My colleague set up the plugin using their own admin account, and they have verified it appears to be working fine on their end. I am not using an ad blocker in this browser on purpose. As per the REST API I don’t think there should be an issue with it tbh. The site is under active development. I have shared all the relevant information in the URL you provided. Please let me know once you have had the time to check everything.

Thanks for the update @skredlemon. Given you’re unable to proceed with a “Checking compatibility” notice, please perform the following checks:

1. Check do you encounter the same issue from a Chrome browser incognito window. If so, please share any browser console errors that appear, and any additional message that may appear if any, or whether the issue is only that the “checking compatibility” notice never proceeds.
2. Does the same occur if you temporarily deactivate your cookieyes plugin? I can see this plugin may have been deactivated when sharing your Site Health information, however, I do see a possibly related popup when visiting your site.

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

Thanks for the tips @jamesosborne I followed your instruction to test it from an incognito session, in which case I received no errors in the console – zero – and the compatibility check was completed. I was then allowed to proceed, after which step I was also able to access the settings page from the incognito session and the normal session also. Kindly note that the cookieyes plugin has not been touched in the meantime.

Therefore I believe that the issue – whatever it might have been – has been resolved now. So thank you once more.

Glad to hear it @skredlemon, and thanks for the update. Based on your experience, it may have been a temporary browser caching or other feature impacting set up previously. If you run into any further issues, be sure to reach out.