[buddypress-trac] [BuddyPress Trac] #7435: XProfile caching: The Next Generation

buddypress-trac noreply at wordpress.org
Thu Feb 2 18:43:56 UTC 2017


#7435: XProfile caching: The Next Generation
------------------------------+-----------------
 Reporter:  boonebgorges      |      Owner:
     Type:  enhancement       |     Status:  new
 Priority:  normal            |  Milestone:  2.9
Component:  Extended Profile  |    Version:
 Severity:  normal            |   Keywords:
------------------------------+-----------------
 I'm currently building a member directory that uses a tabular format,
 populated by xprofile data. Pulling up this data is painful, for a couple
 of reasons:

 - `BP_XProfile_Field::get_id_from_name()` is uncached, which means that I
 have to build my own name/id map to avoid all the extra lookups. This
 makes it unfeasible to use `xprofile_get_field_data()`
 - `BP_XProfile_Group::get()` has a few uncached queries, which makes
 building the map fairly expensive
 - My alternative strategy of calling
 `BP_XProfile_ProfileData::get_all_for_user()` in the loop ran into some of
 the same problems

 Let's think about ways to unify the caching strategy (or lack thereof) in
 these areas with what's happening through the rest of XProfile.

--
Ticket URL: <https://buddypress.trac.wordpress.org/ticket/7435>
BuddyPress Trac <http://buddypress.org/>
BuddyPress Trac


More information about the buddypress-trac mailing list