Changeset 11705 for trunk/src/bp-core/classes/class-bp-user-query.php

Timestamp:

09/27/2017 10:24:10 AM (8 years ago)

Author:

johnjamesjacoby

Message:

Members: trust WP_User::get_data_by() and eliminate an additional user cache layer.

This change removes ye olde bp_core_userdata_ cache key system, relying 100% on the baked-in object cache for user data and improving the liklihood of cache hits (particularly when other membership or community plugins are looking for user data outside of a BuddyPress specific context.)

For example, bbPress will look for authors of topics and latest posts on various forum pages, but BuddyPress will want to make sure it's XProfile Field display names are used. Previous to now, BuddyPress would need to re-query for these users and keep a separate cache of them. By relying on the traditional user objects, those duplicate database queries never happen, resulting in much joy.

This additionally improves page performance throughout the entire application. When user accounts are updated (via XProfile or related) and then immediately prime their caches, there is no more secondary BuddyPress-specific user object cache to prime.

Fixes #7595.

File:

• trunk/src/bp-core/classes/class-bp-user-query.php (modified) (1 diff)

trunk/src/bp-core/classes/class-bp-user-query.php

@@ -571 +571 @@
         ), $this ) );
 
-        // WP_User_Query doesn't cache the data it pulls from wp_users,
-        // and it does not give us a way to save queries by fetching
-        // only uncached users. However, BP does cache this data, so
-        // we set it here.
-        foreach ( $wp_user_query->results as $u ) {
-            wp_cache_set( 'bp_core_userdata_' . $u->ID, $u, 'bp' );
-        }
-
         // We calculate total_users using a standalone query, except
         // when a whitelist of user_ids is passed to the constructor.