Opened 8 years ago

Closed 8 years ago

Last modified 8 years ago

#1587 closed defect (bug) (fixed)

Users with a space in their username cannot log in via

Reported by: netweb's profile netweb Owned by:
Milestone: Priority: normal
Component: Login & Authentication Keywords:


Users with a space in their username cannot log in via

For a username such as: My Username

Workarounds tried includes replacing caps with lowercase or replace the space with a hyphen or an underscrore:

  • my username
  • My-Username
  • My_Username
  • my-username
  • my_username

Logging in via the form on the page header at works fine though.

Change History (7)

This ticket was mentioned in Slack in #bbpress by netweb. View the logs.

8 years ago

#2 @ocean90
8 years ago

  • Keywords reporter-feedback added; needs-patch removed

Tested a few minutes ago an I could successfully log in with a username which contains a space. Was this a specific user?

It's now also possible to log in with a email address.

#3 @netweb
8 years ago

  • Keywords reporter-feedback removed

Indeed it was a specific user:

I was given the password to login and test it myself and based on all the permutations/combinations list above none would work, the workaround was to create a new user which is this user @robinwilson for a temporary solution.

The only successful login I was able to achieve was via the login form here with the username Robin W and his password.

This was all in order to get Robin on Slack and the log in tests were all performed whilst attempting to have the Slack signup page acknowledge that he was logged in at login, even once logging in at subsequently navigating to would show he was not logged in.

You can also see on his main profile page that the his plugins he has authored are not listed, e.g, his commits are in his profile via the BuddyPress activity though.

What I see as the ideal scenario would be jumping into the database and performing some whitespace and hypen surgery on his username, I know this scenario is rarely offered because of the complexity involved, though I would ask that this be considered in this case if I could please. A couple of important considerations are for obvious reasons he does not want to lose commit access for his plugins and I do not want his ~4,000 awesome bbPress contributions to the forums or bbPress Codex affected

#4 @ocean90
8 years ago

  • Keywords close added

This ticket was mentioned in Slack in #meta by ocean90. View the logs.

8 years ago

#6 @ocean90
8 years ago

  • Keywords close removed
  • Resolution set to fixed
  • Status changed from new to closed

The issue has been solved.

#7 @netweb
8 years ago

Thanks everyone, appreciated :)

Note: See TracTickets for help on using tickets.