How to fix signup page linking to login instead of signup despite using "signup" in custom attributes? Answered
hi, I'm not sure why my signup page is linked/being a login page even though in the custom attributes I put "signup'

hi, I'm not sure why my signup page is linked/being a login page even though in the custom attributes I put "signup'

Comments
9 comments
You need to share the webflow project
https://zapr-ai.webflow.io/user-sign-up
Upon checking your website, I discovered you have the data-ms-form="signup" attribute in the div instead of the form. Kindly remove it from the div, and place it in the form and the issue will be gone.
oh wow haha, thank you very much
You're welcome.
for this button, I was trying to figure out a way so that even though it shows login to the user, once the user logins in the button now says "Account" which will redirect to the users account now to show memberships.
Here's a simple way to implement this:
You can add data-ms-content="!members" attribute to the Login button and create a second button, Account with data-ms-content="members" data attribute. This way, the Login button will be displayed for logged-out members, and hidden for logged-in Members while the Account button on the hand will do the opposite i.e. Show for logged-in members and HIdden for logged-out members.
This article would be helpful.
Hi!
Today, I wanted to add an additional field to the login and account creation page for repeating the password (in the account creation form).
Unfortunately, the script (since there's a login panel next to it) checks both fields with: data-ms-member:password, and even if the passwords are identical (in the registration panel), it throws out information about incorrect passwords.
I've created a simple workaround. Maybe it will be useful to someone.
The first password field has been given an additional attribute: ms-code-password:first.
A small change in the code (no. 46):
Instead of: document.querySelector('[data-ms-member=password]')
I added: document.querySelector('[ms-code-password:first]')
Problem solved.
Thanks Tomasz Moszyński for sharing workaround for such specific use-case.
Please sign in to leave a comment.