[wp-trac] [WordPress Trac] #19810: Autocomplete for users and sites in Network admin
WordPress Trac
wp-trac at lists.automattic.com
Thu Jan 12 11:03:16 UTC 2012
#19810: Autocomplete for users and sites in Network admin
----------------------------+------------------
Reporter: markjaquith | Owner:
Type: task (blessed) | Status: new
Priority: high | Milestone: 3.4
Component: Multisite | Version:
Severity: normal | Resolution:
Keywords: |
----------------------------+------------------
Comment (by japh):
Replying to [comment:11 DrewAPicture]:
> '''Autocomplete Libary'''
> * Based on most of the implementations I'm seeing, it looks like the
standard jQuery Autocomplete library is pretty popular. Anybody have
tested alternatives in mind?
At the moment suggest.js is being used in the admin, so unless there's a
specific reason to go with Autocomplete instead then perhaps we see if
that can be used? I'm working on a patch now just to see if that will
transfer easily and be useable.
For an example of where this is used, check out Tags on the Edit Post
page.
> '''Scaling'''
> * Whatever implementation we go with, we're (obv) going to have to take
scaling into account. I've got a MultiSite in the wild with a (modest)
couple hundred users and the autocomplete searches are taking longer than
they should. I can't even imagine what it would be like on larger-scale
installs. Regardless, my first instinct is transients, we'd just have to
figure out the logistics of resetting the stored query data when new users
are registered/added so the query stays current. (Feel free to call me out
if this is an absurd concept).
I wonder if a closer look at the way it works for Tags would help? I mean,
surely some sites have a LOT of Tags, so perhaps that scales ok.
> '''Global User List'''
> * Should Site Admins get access to the global user list? Good question.
My first instinct is to answer 'yes', if they have X information about the
user already, such as a username, but then it would make autocomplete
nearly moot. If 'no', then only Super Admins would have the ability to add
users, which would probably be neither efficient nor reasonable. I guess
it would be pertinent to look at use cases for why Site Admins would need
access the user list or not.
> * Taking it from a different tack, it might be prudent to consider an
option (instead of a decision) in this case. Super Admins already have the
ability to enable Plugin administration menus, why not enable/disable Site
Admin access to the global user list? Then it would become a question of
whether that was network-wide or per-site.
I actually think I might agree with an option rather than decision in this
case too. Some sites will be used like WordPress.com where global user
list access might be useful(?), and some will prefer to keep their sites
completely siloed.
--
Ticket URL: <http://core.trac.wordpress.org/ticket/19810#comment:12>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software
More information about the wp-trac
mailing list