Every new Memberstack project is in Test Mode by default. Once you are ready to go live, you will need to specify which domains should be used for testing and which are in production (a.k.a used by real members). You can configure your domains on the Settings Page.
If you want to remove the "Test Mode" badge please watch or read the rest of the article.
If you're using our DOM Package in a front-end framework, you will want to swap your Live Mode and Test Mode API keys to toggle between staging and production environments.
Managing Test Mode and Live Mode Domains
Every new Memberstack project is in Test Mode by default. Once you are ready to go live, you will need to specify which domains should be used for testing and which are in production (a.k.a used by real members). You can configure your domains on the Settings Page.
Switching to Live Mode and Removing the Test Mode Badge
If you see the Test Mode badge on your published website, Memberstack is running in sandbox mode on that domain. To switch your site to Live Mode and remove the badge:
1. Go to Application Domains
In your Memberstack dashboard, click Settings in the left sidebar and select Application. Scroll down to the Application Domains section.
2. Add your primary domain
Enter your custom domain (for example, yourdomain.com) and ensure the environment dropdown next to it is set to Live Mode.
3. Add your subdomain variations
Webflow and custom hosting providers frequently redirect between root and www domains. Add your subdomain variation (such as www.yourdomain.com) as a separate entry and set it to Live Mode as well.
4. Update custom code API keys (if applicable)
If you installed Memberstack using custom JavaScript or the @memberstack/dom package, check your header code and make sure you replace your sandbox public key (pk_sb_...) with your live public key (pk_...). If you are using the standard Webflow script tag without custom keys, this step is handled automatically.
5. Republish and refresh
Republish your website and perform a hard refresh in your browser (Ctrl+F5 or Cmd+Shift+R). The Test Mode badge will disappear, and real transactions and member signups will be active.
1) How to Launch your Project (1 min video)
When you "go live" your plans, gated content, permissions, custom fields, metadata fields, etc. all carry over.
You only thing you may need to update/change is your API keys. You’ll want to make sure you’re using your live-mode keys in your live project. You can continue using the test mode keys for testing.
2) Errors:
- My live mode domain is still showing the test mode badge. You can usually fix this by adding www. to the beginning of your live mode domain.
- My Application Domains section is missing!
- This domain is already connected to an app.
What is the difference between Live Mode and Test Mode?
- Functionality: Live mode is the production environment where real transactions and interactions occur. Test mode, on the other hand, is a sandbox environment for testing and development purposes. In test mode, you can simulate transactions and interactions using test cards. You can learn more about test cards here.
- API Keys: Memberstack provides separate API keys for live mode and test mode. Test mode keys allow you to interact with test members, while live mode keys allow you to interact with live mode members. You can find your API keys in the Memberstack dashboard here.
- Data Separation: Live mode and test mode have separate data environments. This means that members in test mode will not be in live mode.
- Member Limit: While in test mode there is a member limit of 50. If you reach this limit while testing you need to delete members to continue testing. Members are not able to be switched between live and test modes.
Comments
7 comments
Thanks
Hi
Awesome, super easy and very helpful. Thanks!
Glad it was helpful Joseph Carroll 🙏 Thanks for letting us know
Can test members be logged in by using the next server actions such as loginWithPassword({email, password}) ?
Christopher Fletcher I'm afraid I don't have a test server ready for testing... I do you have a test project live you could use to test it? If you can do that with live members then yes, it should also work with test members.
Thanks for your response, unfortunately when testing this an "invalid credentials" error is returned. Running with the react package instead however works fine, but does not of course have the cache functionality of which server action carry.
I have opened a support ticket on this case to find out more.
Please sign in to leave a comment.