Skip to content

Move email above username field. #3204

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 6 commits into from
Oct 29, 2019
Merged

Conversation

thabaum
Copy link
Contributor

@thabaum thabaum commented Oct 26, 2019

Summary

Email address is at the bottom below password. when you have to enter in the captcha code you have to scroll up to get to enter password again. would be nice not to have to re-enter passwords as this is an issue as well but at least the email address is below the username field with this pull request if accepted.

image

NOTE: I wish I could move "Display Name" below User Name but this is where the bio registration fields go so no way to really move this easily.

If you have Email as Username set the email address is at the bottom making a user enter passwords first and I can't find any other website that does this. However email address under Username is more industry standard I believe for a registration form.

@thabaum thabaum changed the title Update user.ascx to change order of fields for Registration Update user.ascx to change order of fields for user registration moving email address below username and above password fields Oct 26, 2019
Copy link
Contributor

@david-poindexter david-poindexter left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I do understand the logic here, but it is common practice for Username and Password fields to be together. Thus, I am not convinced this is the best approach. I'd be interested to hear what others think.

@sleupold
Copy link
Contributor

IMO it would be best, if the order is confgurable by admins without limit

@thabaum
Copy link
Contributor Author

thabaum commented Oct 27, 2019

image

I didnt change "Username" position. I changed Email Address, username is still above email address. And it would be nice to have the option to be able to move things around, but this makes the form look right as Mitchel pointed out a while back on my site that the order was wrong so I made this pull request. I was thinking it might get dealt by someone else that might notice the same issue but never has. I am just hoping I did it right... :)

And if someone can one up this pull request please be my guest just trying to help the next person... "Logic is the beginning of wisdom; not the end." -- Spock (Star Trek VI)

@thabaum
Copy link
Contributor Author

thabaum commented Oct 27, 2019

IMO it would be best, if the order is configurable by admins without limit

Yes, I totally agree and it looks like it would take breaking the BIO fields down as well to allow adding/removing those and putting them in an order that works best for the website purpose. Some pretty dynamic code from what is currently present.

I am interested in taking on this task potentially down the road if it does not get done. I am just too swamped for past few years now... Maybe we can work on this together I would really love to understand all the pieces to DNN so I can make some better pull requests in the future that might raise an eyebrow...

@thabaum
Copy link
Contributor Author

thabaum commented Oct 27, 2019

For clarity this pull request changes things to this order: Username, Email, Password, Verify Password, Bio, Terms, Submit, authentication, sign in. The previous way had Email after Password. This pull request puts Email on top of the password.

https://www.template.net/web-templates/htmlcss-templates/signup-form/

Here are 20+ HTML5 examples that I believe would be nice to get the login to look like one of these two IMO
I like icons here but not neccessary
image

I like the look and feel of this one
image

and there are about 5 other ones I like but regardlesss they are all pretty much setup like how I put this pull request together.

Copy link
Contributor

@mitchelsellers mitchelsellers left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

IMHO I think that the proper order for this, if we change it should be

  • Email
  • Username
  • Password
  • Confirm Password.

This follows the industry standard of keeping username next to password. If email as username is selected then it would just be

  • Email
  • Password
  • Confirm Password

@thabaum
Copy link
Contributor Author

thabaum commented Oct 28, 2019

I can make this change. I only seen one other form that worked like this, but really it is to satisfy keeping the email and username above the password so I really do not care which way it goes. I was just looking at the way most did it but I do like email on top as that was my preference originally prior to researching...

Moved email above username field.
@thabaum
Copy link
Contributor Author

thabaum commented Oct 28, 2019

IMO it would be best, if the order is confgurable by admins without limit

To discuss this a little further can anyone give me a heads up on what to expect to make this happen if you coded it and I will give it a shot... it would be a good way to get my feet a little wetter here and build some confidence. I figure a few things need to be thought about which is the db schema, sp's and admin ui plus back end code. I am still getting used to github and the new tools along with the latest best practices and future but I am ready to fly soon I believe. I should be able to do this in github overtime with help :)

Maybe show me a proper way to open this up as a discussion issue and I will take some notes from it as far as what details to include and presentation. I tend to be long winded. I can then use this as a template and try to tackle this task with a solution that works. It would really help me understand how everything needs to be connected and written. Of coarse someone else could definitely take this on and I can work on something else if there is someone that can whip this out in the best logical way please do. It would be awesome! I think I could create "something" by version 10 release candidates possibly with some help.

@@ -20,6 +20,17 @@
<asp:requiredfieldvalidator id="valLastName" runat="server" cssclass="NormalRed" display="Dynamic" errormessage="<br>Last Name Is Required."
controltovalidate="txtLastName" resourcekey="valLastName"></asp:requiredfieldvalidator></td>
</tr>
</tr>
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
</tr>

@mitchelsellers mitchelsellers added this to the 10.0.0 milestone Oct 29, 2019
@valadas
Copy link
Contributor

valadas commented Oct 29, 2019

Thanks @thabaum , nothing major here, but next time, we like to have an issue before a pull request and a link back to it in the issue comments (like closes #8948484) (using a big number here to not actually link to a real issue... And in a perfect world it is best to create a branch specific to your change instead of doing it in the development branch because if you do other work before we merge this, you have a better separation. But nothing huge, we are approving this. Thanks for your efforts

@bdukes bdukes changed the title Update user.ascx to change order of fields for user registration moving email address below username and above password fields Move email above username field. Oct 29, 2019
@bdukes bdukes merged commit b1d155b into dnnsoftware:development Oct 29, 2019
@thabaum
Copy link
Contributor Author

thabaum commented Oct 30, 2019

Thank you for the pointers @valadas @bdukes @david-poindexter @mitchelsellers and everyone helping me get my first PR through GitHub and DNN CE. I had to figure out to re-request reviews and it seemed like I had to hit a refresh icon for david to re-review which I spent time looking for.

I am also trying to understand the branches better so I can keep fixes and issues separate. I will play with this more takes time which I am short on but really wanting to dig in here and help. I will watch your video tutorials again refresh things as I want to +1 this PR soon hopefully. Thanks again for accepting my first PR! 👍

@thabaum
Copy link
Contributor Author

thabaum commented Oct 31, 2019

nothing major here, but next time, we like to have an issue before a pull request and a link back to it in the issue comments

isaacs/github#1125

this current issue in GitHub could use some support... this is what I am trying to figure out and find easily how to create an issue and then create a branch. And I wish to understand what is done on my fork as far as development version and how everyone gets to play with it.

I also see an option to delete fork below this message area. Not going to touch it since I don't know why it is there yet.

image

DnnSoftwarePersian pushed a commit to DnnSoftwarePersian/Dnn.Platform that referenced this pull request May 17, 2020
Update user.ascx to change order of fields for user registration (dnnsoftware#3204)
@thabaum thabaum deleted the development branch May 12, 2023 15:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants