My www.abc.com domain is hosting the articles on a Webflow site 

Members are stored in that site. But as my site is growing I will hit 10K users probably in a month so I am preparing a subdomain member.abc.com to host the member pages for those new members. 

All is going well. But I am struggling with the login flow. 

The first login page is on www.abc.com (it's where they register). Users get a daily mail to the new article and can access it after logging in on www. 

I use a data-ms-member field to specify to which member cluster users belong and use this to rewrite the member page links. 

All works fine so I can scale up. However I am getting asked to login again on the member subdomain site when I go to the member page. 

I assume from the docs this scenario is possible and the cookies are shared across the domain but I am probably overlooking some things

Muchos gracias for the help (and the awesome product) 

Hendrik
Matthew, 

Thanks for clarifying. Makes sense cookie / security wise. 

Signing in twice might be a hurdle but it solves the 10K records limit for members in Webflow. All content is on one server but the member only page to track their progress. 

A hurdle but manageable. 

Thanks

Hendrik
Hi Hendrik! 👋

This is an awesome question! I'm happy to inform you we do have a solid solution for this. 🙂  Here's some helpful information from an article on Managing multiple domains using Memberstack:


Can I use multiple domains?

Yes and no. Memberstack will work on an unlimited number of domains IF the domains point to the same content. The issues begin when a user logs into one domain, but travels to another domain in the same session. They would have to log in again to access members-only content on that "new" domain.

Can I use a sub domain?

Yes! We just recommend that members sign up and log in on whatever subdomain contains your members-only content. A session is specific to the domain. Memberstack.io and app.memberstack.io are a great example of this. You'll notice that the signup page appears to be on the main site, but is actually on the app.



Please let me know if you have any questions or concerns! 😀  I hope this helps you get set up in a way that works best for you!

So the trick is to handle the login on a subdomain and not on the main domain? 

So I could create login.mydomain.com and this would grant access to content on any other domain with the mydomain.com suffix? 


Hendrik
Hi 

I have a Memberstack Update Member trigger. 

I wonder if this gets fired when a user updates his profile information (custom fields, email address) with a custom profile form (data-ms-form="profile") in webflow? 

The data in MS gets updated without issues but the Zapier trigger is not fired for that user. 

Hendrik
Hello Hendrik 👋
Weird, well it seems like Memberstack is working since it's getting updated. Do you think you could create a loom.com video of your Zap so we can take a further look? 
Hi JS, Thanks for the response. I bypassed the update member flow via a webflow form and use that as a trigger. That worked. 

The flow was like this: 
* Webflow forms with data-ms-form atrribute
* submit form 
* data in memberstack gets correctly updated

Over to zapier
* select update memberstack member trigger
* only updates from the onboarding flow (different flow) get shown in test results. Even after reloading. The update member trigger doesn't receive the web form update. 

I could do a loom video but have already build and deployed the alternative version. Which is triggering it with Webflow Form update. 


JS replied
  ·  1 reply