How to develop Memberstack on Webflow staging without breaking OAuth and component links? Answered

Post author
Angelo Sadeghpour

Hey everyone, pleasure to be here. I’m trying to set up memberstack with webflow and running into a few things. 1. OAuth via Google can only be set up on a custom domain, and not on a staging webflow.io server? - it’s unclear to me how to then develop without breaking the production server 2. When I copy and paste a memberstack component into Webflow, I always great broken links, is this expected? Now I am starting to see it on a cloned template. It puts a hamper on the ability to deploy. Thanks for your input, Angelo

Comments

2 comments

  • Comment author
    Chukwudi Onyekwere

    Hi Angelo,

    You're right about a few things here. Let's break it down:

    1. Google OAuth requires a verified custom domain because it needs to match the authorized domains in the Google Cloud Console. Unfortunately, webflow.io domains aren't considered secure custom domains. A workaorund would be to set up a subdomain (like staging.yourdomain.com) on your custom domain specifically for testing. This allows you to develop without affecting the production environment while maintaining OAuth functionality.
    2. Broken links** **might happen due to missing attributes, incorrect script placements, or conflicts during the copy-paste process.

    Troubleshooting Tips:
    - Ensure you've added the Memberstack embed script where the component is used.
    - Double-check that the Memberstack attributes (data-ms-*) remain intact after pasting.
    - If cloning a template, confirm the Memberstack settings and URLs match between both projects.

    I hope this helps.

    0
  • Comment author
    Angelo Sadeghpour

    This worked great. Thanks!

    0

Please sign in to leave a comment.