[wp-trac] [WordPress Trac] #25697: User search in network admin returns different results to user search in a sub-site

WordPress Trac noreply at wordpress.org
Sun Oct 27 23:46:23 UTC 2013


#25697: User search in network admin returns different results to user search in a
sub-site
---------------------------+------------------------------
 Reporter:  tomdxw         |       Owner:
     Type:  defect (bug)   |      Status:  new
 Priority:  normal         |   Milestone:  Awaiting Review
Component:  Network Admin  |     Version:  3.1
 Severity:  normal         |  Resolution:
 Keywords:                 |
---------------------------+------------------------------
Changes (by jeremyfelt):

 * version:  3.7 => 3.1


Comment:

 This behavior was set in place by [17189] via #16014, in which a specific
 decision was made to wrap single site searches with a leading and trailing
 `*` for wildcard searching while leaving it to the searcher to add a
 wildcard in multisite.

 Searching with an explicit wildcard as `*@example.com` and `camel@*`
 should work as intended unless `wp_is_large_network( 'users' )` is true.
 If so, then leading wildcards will be stripped and only `camel@*` should
 work as intended.

 For the `example.com` and `camel` searches, if the `@` character is not
 found in a search term, `WP_User_Query` does not include `user_email` in
 the search and looks in `user_login` and `user_nicename` instead. This
 behavior can be filtered with `user_search_columns`, introduced in
 [24056].

 IMO, the way wildcards are treated between single and multisite makes
 sense. See #20661 for a request to better document this in the admin help.

 The search behavior around `@` is somewhat confusing and could be
 interesting to take another look at.

 Related: #15170, #16366, #20135

--
Ticket URL: <http://core.trac.wordpress.org/ticket/25697#comment:3>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software


More information about the wp-trac mailing list