Skip to content

HCC Checkout registration to respect DNN's use email as username field. #511

Description

@alex-pommier

Sponsorship

If this request requires additional support (e.g., such as direct email/phone/meeting/development), I have the following interest in helping to sponsor the effot via GitHub Sponsors:

  • None, please continute to work for me for free :P
  • Absolutely, I get value out of this!
  • Maybe later
  • I'm already a sponsor... Woot!

Is your feature request related to a problem?

Please describe.
Username's are often forgotten by consumers and email as the username is the prefered methodology as it's easier for consumers to remember their emails than usernames they might have only used once for a particular site. This is happening on many websites causing loads of inquiries to reset passwords/accounts beceause users guest checkout and HCC creates DNN user accounts causing issues when multiple accounts exist for the same user requiring staff to intevene. The "use email as username" option in DNN is great because it eliminates usernames from the consumer's perspective. It would be ideal if HCC Checkout page respects this setting and presents users with only an email box not requiring them to specify or create a username.

Similarly for the login option, username should be switched to a email input respectively.

Describe the solution you'd like

HCC should adapt it's checkout registration fields in conjunction with the setting: "Use email as username".

Describe alternatives you've considered

Hiding the username field via CSS is not adaquete as it triggers validation and causes issues.
Hiding all other registration options except guest checkout via CSS. Also not ideal.

Additional context

None
Screenshot 2024-12-13 114147
Screenshot 2024-12-13 114227
Screenshot 2024-12-13 114124

Metadata

Metadata

Assignees

No one assigned

    Labels

    Requires TriageSomeone needs to reproduce this issue.sponsors welcomeWe're looking for one or more people to directly sponsor this update.

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions