Skip to:
Content

Opened 2 years ago

Closed 12 months ago

Last modified 12 months ago

#4057 closed defect (bug) (fixed)

Usernames required to be without space without notice.

Reported by: enderpal444 Owned by:
Milestone: 1.6 Priority: normal
Severity: normal Version: 1.5.4
Component: Core Keywords:
Cc: georgemamadashvili@…

Description

I've been getting emails from people saying they couldn't sign up and didn't understand why and I figured out it's because the username is required not to include a space and yet the error it shows when you try that doesn't point that out. It seems like all the parameters for the username should be pointed out up front also as a mass majority of new signups will throw in a number or capitol letter for their first choice.

Change History (9)

comment:1 DJPaul2 years ago

  • Milestone changed from Awaiting Review to 1.6

This process has changed a bit in BuddyPress 1.6/trunk, but has caused some inconsistencies. Moving this to the 1.6 for the core team to review.

comment:2 DJPaul2 years ago

My plan for this ticket is to rip out the mess of user/blog registration functions that we have, and let WordPress (be it regular or multisite) deal with user name validation, etc. If there are differences in regular/multisite user name validation after this is done, we can at least make sure WordPress trac has tickets for such an issue.

comment:3 Mamaduka2 years ago

  • Cc georgemamadashvili@… added

comment:4 DJPaul2 years ago

  • Owner set to DJPaul
  • Severity changed from major to normal
  • Status changed from new to assigned

See also #4094

comment:5 DJPaul2 years ago

  • Owner DJPaul deleted

comment:6 follow-up: boonebgorges2 years ago

  • Resolution set to fixed
  • Status changed from assigned to closed

In https://buddypress.trac.wordpress.org/changeset/5443, BuddyPress was modified so that it no longer imposes restrictions on usernames (aside from those enforced by WordPress). That should clear the issue in this ticket.

If you can reproduce with the latest BP trunk, please reopen with details. Thanks!

comment:7 in reply to: ↑ 6 anthony.bartoli12 months ago

  • Resolution fixed deleted
  • Status changed from closed to reopened
  • Type changed from enhancement to defect (bug)
  • Version changed from 1.5.4 to 1.7

Replying to boonebgorges:

In https://buddypress.trac.wordpress.org/changeset/5443, BuddyPress was modified so that it no longer imposes restrictions on usernames (aside from those enforced by WordPress). That should clear the issue in this ticket.

If you can reproduce with the latest BP trunk, please reopen with details. Thanks!

Version 1.7 still seems to impose restrictions at least as far as not allowing users to have spaces in their usernames.

To reproduce:

1) Install WordPress alone.
2) Settings > General
3) Select Anyone can register and save.
4) Log out.
5) Register as a user with spaces (i.e. "John Doe")
6) In mysql: select * from wp_users;
7) user_login will be: "John Doe" and user_nicename will be: "John-Doe"
8) Log back in as the admin user
9) Delete the new user you just created.
10) Install and configure BuddyPress.
11) Repeat steps 4-6
12) user_login will be: "John-Doe" and user_nicename will be: "John-Doe"

So it appears that BuddyPress is still preventing users from using spaces in their username.

This is my first bug report so feel free to let me know if my bug reporting could be clearer or adhere better to accepted standards.

This issue is particularly important to me as I am migrating a community from Joomla to BuddyPress and there are many users with spaces in their names. I'd be happy to write a patch for this.

Last edited 12 months ago by anthony.bartoli (previous) (diff)

comment:8 anthony.bartoli12 months ago

  • Resolution set to fixed
  • Status changed from reopened to closed
  • Version changed from 1.7 to 1.5.4

I found a more up to date version of the same bug here:

http://buddypress.trac.wordpress.org/ticket/4622

Will mark this bug as fixed as it was before, pertaining to version 1.5.4.

comment:9 boonebgorges12 months ago

Thanks, anthony.bartoli. Please feel free to add yourself as a cc on #4622 if you want to participate in fixing.

Note: See TracTickets for help on using tickets.