[antoniokenaz1]

Hello, good afternoon.

I would like to request your support, as when I try to sign in with Google from the login page, a modal opens but no information is displayed to complete the login process. When clicking “Sign in with Google”, no error or message appears to indicate what might be happening.

Could you please help me review this issue?

Thank you in advance.

[serkan]

Hi there, good evening,

Thanks for reporting this — a blank Google sign-in modal is usually caused by one of these: browser blocking (pop-ups/3rd-party cookies), a JavaScript conflict/minification, or an OAuth configuration mismatch (Redirect URI / Client ID).
Please try these quick checks first:

Incognito window (no extensions) and temporarily disable ad-blockers/privacy extensions
Make sure the browser allows pop-ups and third-party cookies for your domain
Clear cache (and if you use any performance plugin/CDN, temporarily disable JS minify/combine/defer and retest)

Best regards,
Serkan

[antoniokenaz1]

Good morning. I tried everything: I cleared the cache, disabled plugins, and it still doesn’t work. I also purged the CDN and it’s still not working. I kindly ask you to please review it.

[serkan]

Good morning,

Thanks for testing all of that — if it still opens a blank Google sign-in modal even with plugins disabled and CDN purged, the most common remaining causes are:

OAuth mismatch (incorrect Client ID / Redirect URI not whitelisted)
Blocked third-party cookies / SameSite cookie behavior (especially on embedded/modals)
A JavaScript console error coming from the Google API script or the social login plugin

So I can review this properly and pinpoint the exact cause, could you please send me:
Which plugin is handling “Sign in with Google” (name + version)

A screenshot of your Google Cloud Console → OAuth 2.0 Client settings showing:
Authorized JavaScript origins
Authorized redirect URIs
A screenshot (or copy/paste) of your browser Console + Network tab right after clicking “Sign in with Google” (any red errors / blocked requests)

In the meantime, please also confirm:
Are you using www vs non-www (and http vs https) consistently? The Redirect URI must match exactly.
If you have a security plugin/WAF (Cloudflare, Wordfence, etc.), temporarily allow/whitelist Google endpoints and retest.
Once you share the 3 items above, I’ll tell you exactly what needs to be changed in the OAuth/plugin setup.

Best regards,
Serkan

[antoniokenaz1]

Urgent: Login Page Layout Issue Affecting User Experience
Hello,

Thank you very much for your support. After following your steps, I was able to correctly configure the Google login. The issue was that I had another related domain, which is why it was not opening correctly before. I truly appreciate your help with that.

However, the problem I am currently seeing is that the login layout appears to be broken. It is showing the same behavior as the input fields issue described in the open ticket: “Login Page Layout Compression Issue When Using [tutor_login] Shortcode.” The layout is also being cut off, which creates a poor user experience.

I would like to clarify that you mentioned I am using the shortcode, but that is not the case. I am using the main Tutor LMS dashboard page as the login page, which is:
https://aulamy.com/dashboard/

From this page, users are able to log in. Please let me know if this is the correct way to implement the login, or if there is a recommended approach that I should be using instead.

I kindly ask for your urgent assistance in resolving this issue, as some users will begin registering soon, and this could negatively impact their experience.

Thank you in advance for your prompt support.

[serkan]

Good morning,
Thank you for the update — I’m glad the Google login issue is resolved.
Regarding the layout compression / cut-off on the login view at:
https://aulamy.com/dashboard/
Even though you are not using the [tutor_login] shortcode, the /dashboard/ page still displays a login form when the user is logged out. In cases like this, a “blank space / cut-off / compressed fields” layout is typically caused by a front-end styling or optimization behavior (global CSS rules, responsive container settings, or delayed/minified assets) that applies after the page initially loads.

Is /dashboard/ the correct way to implement login?
Yes — using the Tutor LMS Dashboard page as the login entry can work and is a common configuration. Alternatively, some sites prefer a dedicated login page and then redirect users to /dashboard/ after login, but we can keep your current approach and simply fix the layout.

To review and pinpoint the exact cause, could you please send:
A screenshot of the broken layout (desktop + mobile if possible)
The list of currently active plugins (especially any caching/optimization ones, even if you tested disabling them earlier)
A screenshot of your browser Console right after the page finishes loading (any red errors)

Once I have these, I’ll identify the exact rule/script affecting the form and provide a targeted fix (CSS + placement) so the login view displays correctly without being cut off.

Best regards,
Serkan