The plugin works great, however I can’t seem to get the “redirect_to” parameter to work in the shortcode. I’ve made sure to disable any redirect plugins, but no matter what I do, I end up on the login page after logging in. Please help?
Thanks for getting back to me and sharing the older issue is resolved.
Regarding the OneTap login: Can you please confirm the browser in use? Also, can you share the details I requested earlier? This will help me re-create the same enviroment to test the issue out at my end
@pakey Thanks for getting back to me. I apologize for the back and forth.
Can you please open your browser developer console, retry the one tap and and share the error details with me? There should be some extra details logged within your browser.
I enabled the Google Chrome AI to check it, here it is;
It appears the “one tap login error” is primarily due to the Google Identity Services client library (gsi.js) not being loaded or initialized correctly. The <code class=” “>g_id_onload element is present in the DOM with a client ID, but the necessary JavaScript functions from the Google library are not available.
Here are the potential causes and solutions:
<strong class=” “>gsi.js script not loaded: The most common reason for this error is that the Google Identity Services JavaScript library (<code class=” “>https://accounts.google.com/gsi/client) is not being loaded on the page.
<strong class=” “>Solution: Ensure that the <code class=” “><script async defer src=”https://accounts.google.com/gsi/client”></script> tag is present in the <code class=” “><head> or at the beginning of the <code class=” “><body> of your HTML document. It should load before the <code class=” “>g_id_onload div and any related JavaScript calls.
<strong class=” “>Script loading order: Even if the script tag is present, if other scripts are blocking its execution or if the <code class=” “>g_id_onload element or any related JavaScript tries to access <code class=” “>google.accounts.id before <code class=” “>gsi.js has fully loaded, it can lead to this error.
<strong class=” “>Solution: Place the <code class=” “>gsi.js script tag as early as possible in your <code class=” “><body> or <code class=” “><head>, ideally with <code class=” “>async and <code class=” “>defer attributes. Ensure any custom JavaScript that initializes Google One Tap is executed only after the <code class=” “>gsi.js library has loaded (e.g., within a <code class=” “>window.onload event listener or by placing the script at the end of the <code class=” “><body>).
<strong class=” “>Network issues or ad blockers: Occasionally, network connectivity problems or browser extensions like ad blockers can prevent <code class=” “>gsi.js from loading.
<strong class=” “>Solution: Check the browser’s Network tab in DevTools to confirm <code class=” “>gsi/client is loading successfully (HTTP 200 status). Temporarily disable browser extensions to rule out ad blockers.
<strong class=” “>Client ID mismatch or misconfiguration: While the client ID was present, double-check that it is the correct one for your Google Cloud project and that the “Authorized JavaScript origins” in your Google Cloud Console are correctly configured to include your website’s URL.
<strong class=” “>Solution: Verify the <code class=” “>data-client_id value against your Google Cloud project credentials. Ensure <code class=” “>https://mywebsite.org (or the appropriate origin for your login page) is listed in “Authorized JavaScript origins.”
To investigate further and potentially fix this, let’s check if the <code class=” “>gsi.js script is present in the DOM.
So I add URI under the ‘Authorized JavaScript origins’ (ex; https://mywebsite.org) and it works well so far. I’ll do more testing.
Just for info, I’m unable to locate instructions in the rtCamp GitHub repository regarding where to enter the ‘Authorized JavaScript origins’. I wasn’t aware this was a required step, and I genuinely didn’t see it mentioned in the existing documentation. My apologies if I simply overlooked it! 🙂
However, you’re correct that our documentation needs to be clearer. I’ve raised the concern internally on making things easier to check when you experience an error; its likely cause and possible fixes.
Thanks for sharing your insights.
Viewing 11 replies - 1 through 11 (of 11 total)
The topic ‘Redirect_to in shortcode not working’ is closed to new replies.
