Skip to content

Registration form fails with 404 in Volto #6987

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

Open
rohnsha0 opened this issue Apr 14, 2025 · 5 comments · May be fixed by #6988
Open

Registration form fails with 404 in Volto #6987

rohnsha0 opened this issue Apr 14, 2025 · 5 comments · May be fixed by #6988
Assignees
Labels
01 type: bug 30 needs: triage New issue that needs confirmation before work begins

Comments

@rohnsha0
Copy link

rohnsha0 commented Apr 14, 2025

Describe the bug
The registration form in Volto is failing because it doesn't include the required username field when submitting to the backend API, resulting in a 404 error. The form currently only sends fullname and email fields, but the backend API requires an explicit username field.
When submitting the registration form, the following error is returned:

{
  "error": {
    "errors": [
      {
        "field": "username", 
        "message": "Property 'User Name' is required."
      }
    ], 
    "message": "Error in fields. Property 'User Name' is required.", 
    "type": "WrongParameterError"
  }
}

To Reproduce
Steps to reproduce the behavior:

  1. Navigate to the registration page (/register)
  2. in the fullname and email fields
  3. the form
  4. the 404 error in the network tab

Expected behavior
Since the email field description states "This will be your login name", the form should automatically use the email as the username when submitting to the API:

Screenshots

Image

Software (please complete the following information):

  • Volto 18.8.1
  • Plone 6.1.1
  • plone.restapi 9.13.3
  • CMF 3.7
  • Zope 5.13
  • Python 3.12.9 (main, Mar 17 2025, 23:25:08) [GCC 12.2.0]
  • PIL 11.0.0 (Pillow)
@rohnsha0 rohnsha0 added 01 type: bug 30 needs: triage New issue that needs confirmation before work begins labels Apr 14, 2025
Copy link

boring-cyborg bot commented Apr 14, 2025

Thanks for opening your first issue here! Your engagement is essential for open source projects, including Plone. 🤗

If you haven't done so already, read Plone's Code of Conduct. Also please follow the issue template, as it helps both you and other community members contribute more effectively.

If your issue is a feature request, others may raise its prominence through feature voting.

Welcome to the Plone community! 🎉

@davisagli
Copy link
Member

Also related: #5951. We need to make it work when use_email_as_login is True and also when it is False.

@addymistrel
Copy link

I have gone through this issue and i believe i can solve it so can you assign me this issue.

@rohnsha0
Copy link
Author

rohnsha0 commented Apr 16, 2025

@addymistrel A PR is already open...
See #6988

@rohnsha0 rohnsha0 self-assigned this Apr 16, 2025
@stevepiercy
Copy link
Collaborator

@addymistrel we don't assign issues. Please read and follow First-time contributors, especially Things not to do, Contributing to Plone, and Contributing to Volto.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
01 type: bug 30 needs: triage New issue that needs confirmation before work begins
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants