How to fix the login redirect issue in Memberstack with Webflow when using data-ms-action? Answered
Hi guys Anyone help me?
I was able to set a specific member' login redirect by zaiper and everything works fine in memberstack.
But the problem is a button with data-ms-action=login-redirect in webflow page doesn't redirect.
When the button is clicked, I am able to see a response with member data
But it doesn't go to domain.com/members/mem_sb_xxxxxxxxxxx
read-only link https://daniels-fantastic-site-a3b8fb.webflow.io/
If you open this page, you can signup and it goes to /signup-success page
In thie page, you can see a button.
The button should redirect to memebers/mem_sb_xxxxx
But it doesn't redirect first time. After you refresh the page, it is returning member data
As you can see, there is no loginRedirect in response payload.
But after I refresh the signup-success page, I can see it
Comments
4 comments
I can see that there is a delay and that might be because it takes time to run the automation which handles the signup of a user. So I can guess, once a user signs up the data is passed on to webflow as a cms item which is then published and the login redirect is also set newly for this member on memberstack, to complete this process, the automation needs time.
That's why what I always do is have a screen in between the sign up and the dashboard page, so that the automation gets enough time to publish the item.
So, in your case I can see that after few seconds, when I click on the button, it does take me to a members/xxx page although I can see the webflow CMS item is not published as I am directed to a 404 error.
So what you can probably do is after a sign up you can have a welcome / thank you page which explains your site or what to expect or some info along with a button at the bottom which directs to the login page. Ideally while the user takes time to read the stuff on the page, the Webflow CMS item would be published and login redirect would have been set and user can navigate to their personalized dashboard without any blockers. This is what I did for my clients, let me know if it helps your use-case.
Thanks for replying.
I tried above scenario using timeout for a few seconds, but same result.
When I tried to login instead of signup, it works fine.
But it happens when I tried to signup.
Is there any way to trigger login after signup manually?
You can setup signup, login and logout redirects in the dashboard. Default settings are for all plans, and if you want to customize per plan it will override the default settings.
The thing AJ said makes sense. If Zapier hasn't still processed the member creation in your Webflow collection it could cause a 404 on redirect the first time the user signs up. Handling a loading state until Zapier has finished processing could be a complex task for you, you'll have to do it with Webhooks. His solution for redirecting (only on signup) to a different success page is appropriate. Many people use an /onboarding page so the user can finish up registering all the profile details.
Hey Noda Hikaru, yes I understand, does your use-case have any requirement to onboard users i.e. something like a simple onboarding form to personalize their experience etc.?
Many a times, my clients have wanted an onboarding form for the first time they sign up which sets the goal for the user to use the platform / service and while the users take time to fill that out, the automation would have made a dashboard for the user ready and it won't lead to an experience you are facing currently.
Just need to find a smart workaround for this which buys us time before users try to access the dashboard for the first time upon signup.
Please sign in to leave a comment.