Skip to:

Opened 12 years ago

Closed 12 years ago

Last modified 12 years ago

#1772 closed defect (bug) (worksforme)

@ in user ID not supported

Reported by: paulmpi's profile paulmpi Owned by:
Milestone: Priority: normal
Severity: normal Version: 2.0
Component: API - Registration Keywords:


bbPress doesn't support user IDs with @ signs in them, while those are perfectly OK for WordPress. The WordPress sanitize_user function does not remove the @ for the user_nicename and it causes no further issues. Viewing the bbPress user profile pages or editing them does not work though if there is an @ in the user ID.

Change History (2)

#1 @johnjamesjacoby
12 years ago

  • Component changed from Back-end to Registration
  • Milestone Awaiting Review deleted
  • Resolution set to worksforme
  • Status changed from new to closed

Just tested with 2.1, and this works for me. Created a user with @ is the login using both the bbPress registration form, and WordPress's registration form, with identical results. They actually use the same API to create both sign-ups.

Closing as worksforme

Feel free to reopen with clearer steps to reproduce if I've misunderstood.

#2 @paulmpi
12 years ago

I think I found what the issue is, the Shibboleth plugin that I'm using for user authentication is applying the sanitize_user function for the user_nicename, whereas WordPress is actually using the sanitize_title function for that, which means that the @ (and . ) are stripped as well. This only seems to be a problem though when passing the user_nicename through a URL such as when viewing a user's profile or author's contributions, if the permalink structure is set up like that. Anyhow, bbPress is indeed behaving the same as WordPress in that respect so the issue would have to be resolved in the Shibboleth plugin.

Note: See TracTickets for help on using tickets.