Osclass Themes and Osclass Plugins

Google Login Tutorial for Osclass: Setup and Testing

Configure Google social login end-to-end and validate the user flow before rolling it out on production.
Case Studies & Real Implementations
16. February 2026
2 min read
28108 views
Google Login Tutorial for Osclass: Setup and Testing

Quick overview

Configure Google social login end-to-end and validate the user flow before rolling it out on production.

What this article covers

  • Google login for osclass

Practical notes

  • Validate changes in staging before production updates.
  • Track user impact with analytics, logs, and search performance signals.

Google login for osclass

Increase registration conversion for your osclass with social networks. Enable your visitors to login with their google account into your osclass website. You will need google account and Google login plugin.

Compare options in our social login comparison.

  1. Go to the Google API Console..
  2. Select an existing project from the projects list, or click NEW PROJECT to create a new project:
    • Enter the Project Name.
    • Under the Project Name, you will see the Google API console automatically creates a project ID. Optionally you can change this project ID by the Edit link. But project ID must be unique worldwide.
    • Click on the CREATE button and the project will be created in some seconds.
  3. In the left side navigation panel, select Credentials under the APIs & Services section.
  4. Select the OAuth consent screen tab, specify the consent screen settings.
    • In Application name field, enter the name of your Application.
    • In Support email field, choose an email address for user support.
    • In the Authorized domains, specify the domains which will be allowed to authenticate using OAuth.
    • Click the Save button.
  5. Select the Credentials tab, click the Create credentials drop-down and select OAuth client ID.
    • In the Application type section, select Web application.
    • In the Authorized redirect URIs field, enter the following redirect URLs:
      https://{your_site.com}/ggl/1
      https://{your_site.com}/index.php?page=custom&route=ggl-redirect&gglLogin=1
    • Click the Create button.
  6. A dialog box will appear with OAuth client details, note the Client ID and Client secret. This Client ID and Client secret allow you to access the Google APIs.
  7. Save Client ID and Client secret into plugin.
  8. Add google login button to your theme (OsclassPoint themes has this button usually pre-integrated).
  9. Now you should be able to login to your osclass with google account.

Frequently asked questions

Question: Which Authorized redirect URIs does OsclassPoint Google Login plugin need in Google Cloud?

Answer: OsclassPoint Google Login plugin needs https://yoursite.com/ggl/1 and https://yoursite.com/index.php?page=custom&route=ggl-redirect&gglLogin=1 in Google Cloud Authorized redirect URIs. Both must match the live https host, including www if you use it. A www mismatch is a different URI and Google blocks the OAuth return.

Question: Why does Osclass Google Login plugin need two redirect URLs?

Answer: Google Login uses /ggl/1 when Friendly URLs are on, and index.php?page=custom&route=ggl-redirect&gglLogin=1 as the fallback controller route. Paste both URIs in the OAuth client so either path can complete login. A missing fallback fails when Friendly URLs are off. Match the live https host exactly.

Question: Where do I paste Google Client ID and Client secret in Osclass?

Answer: Copy Client ID and Client secret from Google Cloud into OsclassPoint Google Login plugin settings. The consent screen Authorized domains must include the Osclass host. Paste both values; a blank Client secret cannot finish the Google token step. Save the plugin, then test login on the live URL.

Question: Can I use an existing Google Cloud project for Osclass Google Login?

Answer: You can pick an existing Google Cloud project. Still add a Web application OAuth client, both Google Login plugin redirect URIs, and the site domain on the consent screen. A project used for other APIs is fine if those fields are set. Then paste Client ID and secret into the plugin.

Question: How do I add the Google Login button on a custom Osclass theme?

Answer: OsclassPoint themes such as Zara and Sigma often already print the Google Login plugin button. On a custom theme, add the plugin hook in login and register templates. Without that markup the OAuth client can work while users never see a button. Check the login page source after the hook.

Question: What should I check if Osclass Google Login fails after I save Cloud credentials?

Answer: Check four Google Cloud pieces separately: Authorized domains, both redirect URIs, Web application client type, and the consent screen. Then confirm Client ID and secret in the plugin. A domain or URI mismatch is common. Open the login URL and read the Google error instead of assuming the plugin never gets a code.

About the Author

My passion is building classifieds marketplaces, automating workflows, and turning messy data into useful products. From PHP, HTML, CSS, and JavaScript to Python, crawlers, imports, and SEO, I enjoy solving technical challenges and sharing lessons learned from real-world projects. Most ideas start with a problem, a cup of coffee, and a curiosity to see how far automation can go.
Osclass, PHP, JavaScript, CSS, Python
52 posts Publishing since 04/2018

Shopping cart
Support tickets Downloads Reviews Orders & Invoices Payments
Dashboard My profile Change password Download user data
Logout