Opened 10 years ago

Closed 9 years ago

Last modified 7 years ago

#588 closed defect (bug) (wontfix)

Plugin Info API has case-sensitive username check for profile url

Reported by: extendwings's profile extendwings Owned by:
Milestone: Priority: normal
Component: API Keywords:


In, there is 2 contributors.

The difference is whether the person has commit permission or not.

Change History (9)

#1 @extendwings
10 years ago

  • Cc daisuke@… added

#2 @Otto42
10 years ago

No, it's just that username is case sensitive in a lot of assorted places, and this is one of those places.

That user's name is "HeadOnFire", not "headonfire". If the readme.txt contained the correct case, then you'd get the results you expect.

#3 @Otto42
10 years ago

  • Summary changed from Plugin Info API returns wrong contributors list to Plugin Info API has case-sensitive username check for profile url

#4 @extendwings
10 years ago

@Otto42 Do you have any plan to make Plugin Info API non-case-sensitive?

#5 @netweb
9 years ago

Related: #1150

Maybe even fixed now, @Otto42 ?

#6 follow-up: @Otto42
9 years ago

  • Resolution set to wontfix
  • Status changed from new to closed

Not related to that ticket, and no current plans to fix it. You need to put the correct information in the readme.txt, including the correct usernames. Case matters for usernames. WordPress usernames are case-sensitive.

#7 in reply to: ↑ 6 @SergeyBiryukov
9 years ago

Replying to Otto42:

WordPress usernames are case-sensitive.

FWIW, I can't seem to confirm that.

wp_authenticate_username_password() uses get_user_by( 'login', $username ), which ultimately results in a case-insensitive query without further restrictions:

SELECT * FROM $wpdb->users WHERE user_login = '%s'

Looks like usernames are case-insensitive since 2.8:

#8 @Otto42
9 years ago

Okay. However, being that the forums are still on bbPress 1, those usernames are case-sensitive in lots of places. Until we get everything converted to WordPress and bbPress 2 (WIP), case-sensitivity is always going to be something of an issue.

This is something that will eventually cease to be a problem, but for now, it's relatively easy for a plugin author to fix themselves in the readme.txt file.

This ticket was mentioned in Slack in #forums by sergey. View the logs.

7 years ago

Note: See TracTickets for help on using tickets.