groups_get_group() and BP_Groups_Group tuning

[boonebgorges]

Currently, when you load a group object, you also get things like group admins and mods, which adds a query. When all you need is, for example, the group name or the group avatar, you don't need this info. There should be a way to call up the group without getting this extra crap.

[tw2113]

The Admin/Mods query is all part of the "generic" populate_extras argument, which is your basic true/false boolean value.

We would need to separate out and/or add extra params to $group_args to indicate whether or not to fetch these values, and act accordingly inside of BP_Groups_Group class.

Perhaps add both a param and/or a filter to exclude, and leave included by default to avoid backcompat issues.

[boonebgorges]

Yes, a parameter to exclude just these options would be a start.

A more complete solution, IMO, would be to do the following:

1. Ensure that the admin/mods query is properly cached.
2. Lazy-load the admin/mods data. That is: make the properties protected, limiting access to __get(); and in __get(), fetch them only if they're needed. In the case of a groups loop, I'd say that they should all be pre-fetched into the cache no matter what (unless we want some sort of more sophisticated lazyload like WP does: ​https://core.trac.wordpress.org/browser/trunk/src/wp-includes/class-wp-metadata-lazyloader.php). But the more simple lazy-load would be quite effective when calling groups_get_group() outside of a loop.

[dcavins]

This ticket has been addressed in commits that improved BP_Groups_Group, especially r11071, r11087, r11089.