Hi!
I hope this isn;t a dup. I searched first!
Usernames are permitted to contain a spacein themupon signup. For instance, uid1 is named "John Doe" but you are unable to edit it; you receive a
"The username contains invalid characters."
error and a red boxed username field error if ANY changes are attempted on the "My Account" page.
And,of course,username changed themselves are not permitted.
Thanks!
-Brian

Comments

michelle’s picture

Project: Advanced Profile Kit » Drupal core
Version: 6.x-1.x-dev » 6.12
Component: User interface » user system
Category: bug » support

This is part of core, not APK. And more likely a support request than a bug as I suspect a bug this big would have been found by now. Moving to the appropriate queue.

Michelle

brianbrown’s picture

Category: support » bug

No. Its a bug!
-Brian

michelle’s picture

Category: bug » support

This may be a bug in some contributed module you are using, but it is not a bug in core. Core has no issues with editing usernames that contain spaces. As far as this queue is concerned, it is a support request. If you want some help with it, you may want to try listing any modules you use that could impact user names. Beyond that, I don't know. It's hard to troubleshoot with the limited information you provided.

Michelle

brianbrown’s picture

Category: support » bug
Priority: Normal » Critical

This also occurs when attempting to manually add a user and the username contains spaces at:
* * * /admin/user/user/create
The advice below the username box says:
Spaces are allowed; punctuation is not allowed except for periods, hyphens, and underscores.
which also shows on the user registration page. But if a user registers a username containing a space (which is permitted at this point), the user can NEVER be edited by an administrator!
Attempting to do so generates a red box at the username field whth the following error message:
The username contains invalid characters.
Either spaces should be disallowed site-wide, or not!
Thanks!
Brian

michelle’s picture

Sigh. You are not reading what I am writing. This is not a bug as far as the core Drupal queue is concerned since this works fine in core Drupal. Something you have installed is affecting this. What, I don't know. But core is not broken therefore this is not a bug but a support request.

Honestly, you would be better off posting for help in the forums because I don't think as many people read the core issue queue looking to help with support requests but that is up to you. But, please stop changing this to a bug report when it's not because that just clutters the bug queue.

Michelle

brianbrown’s picture

Category: bug » support
Priority: Critical » Normal

This is exactly why I left Drupal!

michelle’s picture

Status: Active » Closed (won't fix)

You seriously came back over a year later to tell us that you left Drupal because you can't tell a bug from a support request? Good grief.

Michelle