[buddypress-trac] [BuddyPress Trac] #4728: Visibility API refactoring/restructuring

buddypress-trac noreply at wordpress.org
Wed Mar 4 20:36:20 UTC 2015

#4728: Visibility API refactoring/restructuring
 Reporter:  chrisclayton       |       Owner:
     Type:  enhancement        |      Status:  new
 Priority:  normal             |   Milestone:  Future Release
Component:  Component - Core   |     Version:
 Severity:  normal             |  Resolution:
 Keywords:  reporter-feedback  |
Changes (by r-a-y):

 * keywords:  2nd-opinion reporter-feedback => reporter-feedback


 > I'm totally behind the idea of working toward privacy/visibility
 features that will work across more content types, but just porting over
 the stuff from the xprofile component won't work. (We could keep the
 levels - 'loggedin', 'friends', etc, but that's about it.)

 I think the comments by Chris about extrapolating the default levels from
 XProfile is valid.  This is so plugins can work from a consistent set of
 levels instead of having to define their own custom ones.

 Visibility userdata can be handled by plugins and can follow how XProfile
 is doing it with usermeta.

 Going to work on a patch just for levels.

Ticket URL: <https://buddypress.trac.wordpress.org/ticket/4728#comment:7>
BuddyPress Trac <http://buddypress.org/>
BuddyPress Trac

More information about the buddypress-trac mailing list