Adam Dunnage
Forum Replies Created
-
@bilalfromfocusteck I just wanted to check back in with you to see if you were able to find a solution to this? If not then I am happy to continue troubleshooting this for you if you’d like to share any further details.
@aalexandrov Thanks for sharing the information. I have passed this on to the team who will check this for you. This can take a couple of days but as soon as I hear back I will update you here.
@aalexandrov Yes we can certainly check this for you. To get all the required information, please can you share your Site Health information. You can use this form to share privately if preferred.
Please be sure to also share the callback URL you are seeing which includes the staging URL. This information will be helpful for us in looking for your site records. We may need to remove or invalidate site records for you to allow you to complete Site Kit setup once more.
@aalexandrov Understood, thanks for clarifying this. Did you perform a Site Kit reset on the staging site before you performed the sync between staging and production sites? If not then it’s likely that the issue is due to mismatched records on the Site Kit service which will be expecting the original URL you connected Site Kit with.
If you can revert back to the original setup then please do this and perform a Site Kit reset. Once done you can go through the sync again and connect Site Kit once more on the production site.
If this isn’t possible then let me know as we may need to request a record check for your site.
Hi @aalexandrov, thanks for opening a support topic with us. From the information you have shared with us, it’s possible that the site records are mismatched and Site Kit is expecting your previous staging URL. This is something we can look into further but before we do that, I’d like to point out that Site Kit will not work if you need to access your website via password as you have stated.
You can see this listed in our installation requirements so this will need to be addressed first. If you address this and are still facing the URL issue then I will be happy to investigate this further for you.
@beatty67 Can you confirm that the error is no longer showing and you are able to use Site Kit without any issue at this time?
@beatty67 I can see you have shared your site health so thanks for that. Could I please also ask you to share the other information requested as well as the outcome of running the troubleshooting checks. This information will be helpful in determining the cause of this error.
I can also see that you have the GTM4WP plugin active on your site. It’s possible that if you are using this and Site Kit for Tag Manager code placement and management, there could be a conflict between the two plugins. If you disable the GTM4WP plugin, do you still encounter the same error?
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.
Hi @beatty67, thanks for opening a support topic with us and sharing the error message you are seeing. I’d be happy to look into this further for you. Please could you share the following:
- Your Site Health information. You can use this form to share privately if preferred.
- Have you tried setting up Site Kit in an Incognito browser? And does the same issue occur?
- Does the error message display when accessing the Site Kit dashboard? Please share a screenshot of it if possible.
You could also try following the troubleshooting steps here to see if the same happens while in troubleshooting mode with just Site Kit active. Let me know how you get on with that and the above checks.
If you have anymore questions at this time please feel free to ask them.
@reivorz Thanks for the added context that has been really helpful in helping me to understand what is happening here. On further inspection and after discussing with the team, it appears that the Sign in with Google button HTML only renders buttons that exist when the page is first loaded, but because the button in the popup is created/rendered AFTER the page is loaded, the Sign in with Google JavaScript doesn’t render the button.
We have opened a new GitHub issue to address this which you can follow for updates but currently there is no workaround for this at this time. I hope this helps to explain this to you and as mentioned above please follow the issue for updates.
If you have any other questions at this time on Sign in with Google in Site Kit then please don’t hesitate to ask.
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.
@bilalfromfocusteck Thanks for sharing the information that’s very helpful. As this appeared to work when using an Incognito browser, it’s possible that a browser extension could be causing Site Kit to disconnect. In a regular browser, go to chrome://extensions/ which will list all your extensions. Try disabling all extensions and attempting Site Kit setup once more.
If this works without disconnecting you, then you can enable extensions one by one checking Site Kit until it disconnects which would then show the conflicting extension.
Please try this and let me know if you find any conflict. I will continue to review your site health in the meantime.
Hi @bilalfromfocusteck, thanks for getting in touch. Sorry to hear that Site Kit isn’t staying connected for you. I’ll be happy to investigate this for you. To start, please can you share the following information:
- Your Site Health information. You can use this form to share privately if preferred.
- Have you tried setting up Site Kit in an Incognito browser? And does the same issue occur?
- Any screenshots or recordings you can share as you stated above. Feel free to add links to these via the private form.
You could also try following the troubleshooting steps here to see if the same happens while in troubleshooting mode with just Site Kit active. Let me know how you get on with that and the above checks.
If you have anymore questions at this time please feel free to ask them.
Hello @reivorz, thanks for reaching out. I’d be happy to help you with your Sign in with Google questions.
Sign in with Google when enabled in Site Kit will place a login button on standard WordPress login pages, including WooCommerce login pages. This is why you aren’t seeing the option within your popup/modal login form.
If you wish to place a Sign in with Google button elsewhere on your site you have a couple of options available to you:
- Sign in with Google block – A dedicated WordPress editor block that can be placed anywhere on your site.
- Sign in with Google shortcode – If your site or theme doesn’t support the block editor, you can output a Sign in with Google button using the following shortcode:
[site_kit_sign_in_with_google].
This should help you to achieve what you’re looking for in your popup/modal login form. If you have any other questions or need some further help with Sign in with Google then please let me know and I will be happy to help.
@mrwweb I just wanted to check back in to see if this was working for you now?