Managing Test Mode and Live Mode Domains

Article author
Duncan Hamra

Every new Memberstack project is in Test Mode by default. Once you're 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.

Screen_Shot_2023-02-10_at_1.47.27_PM.jpg

If you're using our React API or another front-end framework, you'll want to swap your Live Mode and Test Mode API keys to toggle between staging and production environments.

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.

Possibles errors:

My Application Domains section is missing!

This domain is already connected to an app.

What the difference between Live Mode and Test Mode?

  1. 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.

  2. 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.

  3. Data Separation: Live mode and test mode have separate data environments. This means that members in test mode will not be in live mode.

  4. 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.

Was this article helpful?

Comments

7 comments

  • Comment author
    Enmanuel Alonzo

    Thanks

    0
  • Comment author
    Enmanuel Alonzo

    Hi

    0
  • Comment author
    Joseph Carroll

    Awesome, super easy and very helpful. Thanks!

    1
  • Comment author
    Duncan Hamra

    Glad it was helpful Joseph Carroll 🙏 Thanks for letting us know

    0
  • Comment author
    Christopher Fletcher

    Can test members be logged in by using the next server actions such as loginWithPassword({email, password}) ?

    0
  • Comment author
    Duncan Hamra

    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. 

    0
  • Comment author
    Christopher Fletcher

    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.

    0

Please sign in to leave a comment.