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

[buddypress-trac at lists.automattic.com]

#3695: Basic profile privacy
------------------------------------+-----------------------------
 Reporter:  boonebgorges            |       Owner:  cnorris23
     Type:  enhancement             |      Status:  accepted
 Priority:  normal                  |   Milestone:  Future Release
Component:  Core                    |     Version:
 Severity:  normal                  |  Resolution:
 Keywords:  dev-feedback has-patch  |
------------------------------------+-----------------------------

Comment (by DJPaul):

 Tested this a bit. Initial thought is that you commit this so we can
 iterate. It's a lot more compact than what I feared.

 * Maybe call this visibility instead of privacy.
 * If user's profile field value is emptied, and the privacy option is
 changed at the same time, the empty field is to the database, but the
 privacy option isn't updated.
 * With the new bit of javascript, use jQuery 1.7's $.on() to bind the
 click event (I can't see there's much point in updating the rest of the
 javascript as it's backwards compatible, but may as well get any new
 javascript correct).
 * Add a class property for "privacy_levels" to BP_XProfile_Component or
 BP_Component.
 * 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?
 * Maybe use wp_parse_id_list() to sanitise integer arrays.

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