WordPress.org
Get WordPress

Make WordPress Core

Opened 16 years ago

Last modified 5 years ago

#5918 new enhancement

Allow non-ASCII usernames

Reported by: marshosh's profile marshosh Owned by:
Milestone: Future Release Priority: normal
Severity: normal Version: 2.3.3
Component: Users Keywords: has-patch needs-refresh
Focuses: Cc:

Description

Hello ...
I can't make New username with arabic characters ...

who i can apply an arabic characters in usernams ?

Thank you ...

Attachments (5)

registration.php.patch​ (779 bytes) - added by dwright 14 years ago.
dont enforce strict on registration names patch, against revision 12187
arabic_user_register.png​ (14.8 KB) - added by dwright 14 years ago.
register user with arabic name
arabic_user_login.png​ (24.2 KB) - added by dwright 14 years ago.
arabic user login
arabic_user_admin_area.png​ (2.3 KB) - added by dwright 14 years ago.
admin area (simple)
arabic_user_admin_area_edit2.png​ (42.6 KB) - added by dwright 14 years ago.
edit arabic user

Download all attachments as: .zip

Change History (37)

#1 @Denis-de-Bernardy
15 years ago

  • Keywords needs-patch added; Arabic Non-English characters removed

related: #9591

#2 @Denis-de-Bernardy
15 years ago

  • Component changed from General to Users
  • Owner anonymous deleted

#3 @Denis-de-Bernardy
15 years ago

possibly related: #5472

#4 @dwright
14 years ago

  • Cc david_v_wright@… added

Here is a patch that will enable a user to register with an arabic name.

(however, it also probably introduces security issues)

@dwright
14 years ago

dont enforce strict on registration names patch, against revision 12187

@dwright
14 years ago

register user with arabic name

@dwright
14 years ago

arabic user login

@dwright
14 years ago

admin area (simple)

@dwright
14 years ago

edit arabic user

#5 @dwright
14 years ago

  • Keywords has-patch added; needs-patch removed

#6 @ryan
14 years ago

  • Milestone changed from 2.9 to 3.0

Something to consider for 3.0 after considering all security ramifications.

#7 @dd32
14 years ago

  • Keywords early added
  • Milestone changed from 3.0 to 3.1

Moving to 3.1, As ryan said, We need to consider any of the security ramifications of this change. We're nearing beta right now, it doesn't seem appropriate to change this late in the game.

#8 @nacin
13 years ago

  • Keywords early removed
  • Milestone changed from Awaiting Triage to Future Release

#9 @mamouneyya
13 years ago

  • Cc mamouneyya added
  • Summary changed from Registr with Arabic (Non-English) characters ? to Allow non-ASCII usernames
  • Version changed from 2.3.3 to 3.1

Please consider implementing this in 3.2. Registration always confuses my users because they cannot use non-ASCII characters.

#10 @dd32
13 years ago

  • Version changed from 3.1 to 2.3.3

Please leave the version field set to when it was originally reported.

#11 @mamouneyya
13 years ago

Sorry, I was just trying to say that the same issue still exists in the latest version.

#12 @cupid4
13 years ago

  • Version changed from 2.3.3 to 3.3

I think this is really a must-have feature for WordPress, from my experience, trying to create Arabic website with WordPress, it made a lot of confusion to users cause they simply tried to make Arabic names and every time it tell them the name is wrong and never mentioned anything about language, not even a warning or a comment to say the name should be in English, so it took me a while and losing a lot of users too before I figured out that WordPress doesn't support Arabic names at all.

It's really needed fix for WordPress localization, there is no point of creating Arabic website if your users can't choose their name in Arabic :) I hope this is being considered for 3.3

#13 follow-up: @dd32
13 years ago

  • Version changed from 3.3 to 2.3.3

Version changed from 2.3.3 to 3.3

The version field is used to track when a issue was first raised, This need not be updated to a current release upon commenting. Any version between the "Version" and "Milestone" field is considered to be affected

#14 in reply to: ↑ 13 @cupid4
13 years ago

Replying to dd32:

Version changed from 2.3.3 to 3.3

The version field is used to track when a issue was first raised, This need not be updated to a current release upon commenting. Any version between the "Version" and "Milestone" field is considered to be affected

Okay, didn't mean to mess with anything, I just thought it's the right way to promote the ticket to the version. well, any comments about the ticket subject itself?

#15 @SergeyBiryukov
13 years ago

#18666 has a workaround plugin to allow Arabic usernames.

#16 @bpetty
12 years ago

Username values related: #17793, #16833

Also, this does not appear to actually be a bug, more of a feature request / enhancement.

WP might not have been clear in the past, and may have allowed more, but there is a specific set of valid characters for usernames, and it doesn't even include the full ASCII range now. See #17793 for a patch currently open to make valid characters more clear in user creation error messages.

I think it's safe to say at this point that the username values will never support any characters outside of it's current range of characters.

#17 @nacin
12 years ago

  • Type changed from defect (bug) to enhancement

#18 @alex-ye
11 years ago

  • Cc nashwan.doaqan@… added
  • Keywords needs-refresh added
  • Version 2.3.3 deleted

As the WordPress is a global script , non-ascii user names should be supported in the core , This ticket was opening before 5 years !

Last edited 11 years ago by alex-ye (previous) (diff)

#19 @alex-ye
11 years ago

  • Version set to trunk

#20 @SergeyBiryukov
11 years ago

  • Version changed from trunk to 2.3.3

#21 @alex-ye
11 years ago

  • Version 2.3.3 deleted

#22 @alex-ye
11 years ago

  • Version set to 3.5

The problem is still exists in WordPress 3.5

#23 follow-up: @SergeyBiryukov
11 years ago

  • Version changed from 3.5 to 2.3.3

Version number indicates when the enhancement was initially suggested. See comment:13.

#24 in reply to: ↑ 23 @alex-ye
11 years ago

Replying to SergeyBiryukov:

Version number indicates when the enhancement was initially suggested. See comment:13.

:) , Thank you for explaining .

#25 @SergeyBiryukov
11 years ago

#23238 was marked as a duplicate.

#26 @iseulde
10 years ago

Is this possible considering that usernames are used in urls like author pages? It's also worth noting that plugins might rely on the fact that the username is alphanumeric (e.g. P2's @mentions).

This is related to allowing non-ASCII post slugs and IDN support (see #10690 and #10298).

This ticket was mentioned in IRC in #wordpress-dev by SergeyBiryukov. ​View the logs.
10 years ago

#28 @SergeyBiryukov
9 years ago

#24939 was marked as a duplicate.

#29 @Clorith
8 years ago

#38325 was marked as a duplicate.

#30 @Clorith
8 years ago

#38325 was marked as a duplicate.

#31 @macmanx
8 years ago

#38325 was marked as a duplicate.

#32 @macmanx
8 years ago

#38325 was marked as a duplicate.

Note: See TracTickets for help on using tickets.