[wp-trac] [WordPress Trac] #20835: Multisite subdirectory autocompletes are broken
WordPress Trac
wp-trac at lists.automattic.com
Tue Jun 5 03:38:45 UTC 2012
#20835: Multisite subdirectory autocompletes are broken
--------------------------+------------------
Reporter: nacin | Owner:
Type: defect (bug) | Status: new
Priority: high | Milestone: 3.4
Component: Multisite | Version:
Severity: blocker | Resolution:
Keywords: has-patch |
--------------------------+------------------
Comment (by nacin):
New thoughts, after an IRC conversation earlier in the day:
* Autocomplete for a search field is useless, unless it allows you to
click a suggestion and go directly to that result.
* Autocomplete should therefore be removed for any "search" inputs, which
would account for the user and site searches on the network dashboard, on
network/sites.php, network/users.php, and wp-admin/users.php, etc.
* This removes all site auto-completes, so we would kill off site-
search.js and wp_ajax_autocomplete_site(). This likely removes a decent
amount of code from user-search.js. This may remove some code from
wp_ajax_autocomplete_user().
* Autocomplete is most effective for adding existing users to a site, in
multisite, whether that is on network/site-users.php or wp-admin/user-
new.php. This is really the only place the feature should have been
implemented with the current UX. (See point 1 for what that might look
like.)
* Should the autocomplete handlers in user-search.js be dependent on IDs?
Seems like they would work better as classes.
* "user-search" (and "site-search") should really be "user-autocomplete",
or "user-suggest". I think I intend to rename the script handles and files
to reflect their actual purpose.
I hope to resolve this in its entirety, and quickly, on June 5.
--
Ticket URL: <http://core.trac.wordpress.org/ticket/20835#comment:8>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software
More information about the wp-trac
mailing list