Switch to WP_User_Query for BP_Core_User
|Reported by:||cnorris23||Owned by:|
WP 3.1 introduced the WP_User_Query class. If BP utilized this, it would reduce the amount of code that needs to be maintained (no need to reinvent the wheel), and have the added benefit/reduced headache of caching. However, this would require that XProfile data be moved into the user_meta table, rather than it's own table as it is now. Since I didn't join the BP community until 1.2-alpha, I don't know the logic behind a separate table over the user_meta table. Therefore, this ticket may be short-sighted. I've opened this ticket to start (or end if I'm way off base) a discussion on this. I'm more than willing to write up a patch, but I wanted to get feedback first.
Initial thoughts on moving the XProfile fields would be to move them to a CPT, with profile options and any meta being stored in the post_meta table. Again, this would reduce code we need to maintain by giving us access to WP_Query.
Too much caffeine, and having to decide what/what not to say in this ticket has me all verklempt. Talk amongst yourselves.
Change History (14)
- Milestone changed from Awaiting Review to Future Release
- Type changed from defect to enhancement
comment:13 boonebgorges — 19 months ago
- Milestone Future Release deleted
- Resolution set to duplicate
- Status changed from new to closed