BP integration lacking public visibility option

[clavaque]

About custom profile fields integrated with BuddyPress.

Since BP has public profiles, the s2 profile fields cause a problem not letting the site owner pick the visibility setting as the BP profile fields allow.

The video doesn't mention this limitation: https://www.youtube.com/watch?v=YDDoNrzOi6Q

I think this improvement should be done to s2 fields so this setting is more correct: WP Admin -> s2Member -> General -> Registration/Profile Fields -> BuddyPress -> Public Profiles

Related ticket: https://websharks.zendesk.com/agent/#/tickets/3188

[jaswrks]

Thank you! So the issue is that site owners would like more control over the visibility of profile fields in display on-site (i.e. in a list of the members, or in the profile). Got it.

The current functionality in s2Member says that any field which is not invisible will be displayed publicly. I agree, this could use some improvement whenever BuddyPress comes into the picture.

---

NOTE TO FUTURE SELF: Referencing this line in the s2Member source code which asks for a context of profile-view. The handler there could be updated to consider an additional context/visibility setting whenever BuddyPress is installed.

[clavaque]

Great, thanks!

Maybe that visibility setting from BP, could be achieved, and even improved, if we have a conditional similar to what we added to s2Drip, based on access. Maybe you can use the method that already checks that for s2Drip.

That way we can make it public to visitors, or just logged in users, or certain levels higher than 0, and combinations. Rather than visibility, it'd be an access setting for the custom field. I think this goes well with s2 because it improves what BP allows taking advantage of our own features.