[Wishlist] More redirect control on signup, login, upgrade, etc. Completed
1) The problem → I'm teasing features that are only available to paying members. If a free member decides to upgrade to get access to a feature, I want them to stay on the page after upgrade (or go back to the page they were on before entering the upgrade flow).
2) Why is this important → It's critical to the UX of my site. Dropping someone on a generic welcome page after upgrading doesn't make sense given my use case (it might for someone else, but not for me).
3) What's your plan B → Write some custom code to override this behavior. I wanted to use the Redirect after signup or login power-up, but that only works for static websites and on sign up.
4) Possible solutions we could build for you → Give me a way to "remember" the current URL and return the person to that page after they upgrade. Maybe with a data attribute, snippet of code, or a list of URLs in the dashboard.
Comments
7 comments
🎉 Good news!
You can now use the attribute
data-ms-redirect="current-url"to save the current URL. The next time that visitor goes to sign up or login they will be returned to the page.Here's the full help center article.
We will likely solve this problem with custom code in 2023.
User logs in without "refreshing" / "redirected"
Idea - add "?redirect=return" or something to the signup link to ignore the signup/login redirect.
This is something that is also critical to the UX of my site. I would love to see this feature added.
One strategy I'm working on is to set two cookies - 1) the memberID and 2) the membership.name attributes. It's been kinda tricky with latency, loading Memberstack member attributes. So I wrote some code with an event listener that set the cookies when the USER interacted with the page (mouseover). The memberstack attributes are in hidden fields initially. By the time the user interacts with the page the attributes have been loaded for sure. In subsequent pages I use the cookies in API calls where I need the memberID to get data relevant to the user - for CRUD operations.
Codepen
https://codepen.io/david78737/pen/ExoVdLm
Once the cookies are set on the user machine, the latency issue goes away. The membership.name attribute can be used to set a visibility attribute (CSS) on buttons so the appropriate button and redirect URL is active when the user clicks it.
Hello everyone,
Any news about this feature? It would be essential for my application.
Take care!
Please sign in to leave a comment.