[lonecrowdotnet]

Thanks for the comment. But how does that explain the fact the there are two different functions that both return collections of members; but that each function returns a different member class with different fields/properties available?

Is this a purposeful design pattern common to PHP or WordPress apps? or is it just a product of open source development and the lack of an over riding design model?

[lonecrowdotnet]

Has anyone ever produced a class diagram for BuddyPress?

[lonecrowdotnet]

Thanks that helps a lot Looks like that belongs to something called Page Security by Contexture, which won’t be any good to me in this instance.

So then my question is, what is the best way to filter the member directory based on an extended buddypress field? They have a profile field that is a multi-selct box and it contains an option that would identify those that are not to be displayed in their member directory.

I was presuming that BP would have some $user.extended-field.value that I could use to filter the list in the member-loop page but as I said before I am concerned this it would be a cheesy little hax that would probably mess up the pagination and god knows what else.

If I wanted to modify the SQL statement just for the member-loop what is the best practice way to do that?

Thanks