[buddypress-trac] [BuddyPress] #3695: Basic profile privacy

[buddypress-trac at lists.automattic.com]

#3695: Basic profile privacy
--------------------------+------------------------
 Reporter:  boonebgorges  |       Owner:  cnorris23
     Type:  enhancement   |      Status:  closed
 Priority:  normal        |   Milestone:  1.6
Component:  Core          |     Version:
 Severity:  normal        |  Resolution:  fixed
 Keywords:                |
--------------------------+------------------------
Changes (by boonebgorges):

 * status:  accepted => closed
 * resolution:   => fixed


Comment:

 DJPaul - Thanks for your very helpful feedback. Most of your issue have
 been fixed.

 > Hardcoded html in bp_profile_privacy_radio_buttons(), not sure how best
 to work around that.
 $fetch_privacy_level_default in bp_has_profile(). If, for the sake of
 argument, someone had a custom widget that displayed profile data of a
 specific user, would that sort of use case be handled? Or some sort of
 profile field RSS feed?

 All that means is that there'll be an extra query involved. Just a bit of
 extra overhead that I engineered to avoid.

 > Hardcoded html in bp_profile_privacy_radio_buttons(), not sure how best
 to work around that.

 I thought about putting it right into the template, but it was ugly. For
 form elements, I think that outputting markup is not the worst thing in
 the world, especially if it's filtered (which this is) and if there is an
 alternative way to get the required raw data (which there is -
 bp_xprofile_get_visibility_levels()). So I'm suggesting we leave it as is.

 Marking this ticket resolved. Specific issues can get separate tickets.

-- 
Ticket URL: <https://buddypress.trac.wordpress.org/ticket/3695#comment:16>
BuddyPress <http://buddypress.org/>
BuddyPress