Skip to:

Opened 12 years ago

Closed 6 years ago

#4142 closed enhancement (maybelater)

Add xprofile fields in bp_get_users

Reported by: dennissmolek's profile DennisSmolek Owned by:
Milestone: Priority: normal
Severity: normal Version: 1.5.4
Component: Members Keywords: trac-tidy-2018
Cc: DennisSmolek


While working on a pretty large site Im running a large import of users (20,000+) and I'm afraid of going down the wrong path.

Core WP lets me define any user_meta I want in the meta table, but this data isn't then tied back to xprofile data so its not easy to display on profiles. It does however let me use get_users() which I can then query that meta data and return an array of users.

Which for example I wanted to pull everyone with the state of TX is very easy. If this data was xprofile data its hard to query that data.

Looking at bp_core_get_users it already joins the xprofile table so converting off from "meta_key"/"meta_value" to "field"/"value" shouldn't be too bad.

This would allow a single bp_get_users() to pull users based upon their profile data.

In the mean time I'm adding meta AND xprofile data which is redundant but a stop gap until I can either code my own query or bp adds one.

Change History (3)

#1 @boonebgorges
12 years ago

  • Milestone changed from Awaiting Review to Future Release

This is something I would like to have as well, but it seems unwise to add an xprofile join in this method. It simply won't scale, due to the xprofile table schemas. (In truth, xprofile_data has the same problems as usermeta in terms of scalability.)

Once we have done some of the fixes in #4060 - which are the very first thing I plan to do during the 1.7 cycle - we can start to consider truly scalable methods of the kind of filtering you're hoping to do.

#2 @DJPaul
6 years ago

  • Keywords trac-tidy-2018 added

We're closing this ticket because it has not received any contribution or comments for at least two years. We have decided that it is better to close tickets that are good ideas, which have not gotten (or are unlikely to get) contributions, rather than keep things open indefinitely. This will help us share a more realistic roadmap for BuddyPress with you.

Everyone very much appreciates the time and effort that you spent sharing your idea with us. On behalf of the entire BuddyPress team, thank you.

If you feel strongly that this enhancement should still be added to BuddyPress, and you are able to contribute effort towards it, we encourage you to re-open the ticket, or start a discussion about it in our Slack channel. Please consider that time has proven that good ideas without contributions do not get built.

For more information, see
or find us on Slack, in the #buddypress channel:

#3 @DJPaul
6 years ago

  • Milestone Awaiting Contributions deleted
  • Resolution set to maybelater
  • Status changed from new to closed
Note: See TracTickets for help on using tickets.