Skip to:

Opened 11 years ago

Closed 11 years ago

Last modified 11 years ago

#4942 closed defect (bug) (no action required)

Base profile group visibility settings in BuddyPress

Reported by: henrywright's profile henrywright Owned by:
Milestone: Priority: normal
Severity: normal Version: 1.7
Component: Extended Profile Keywords:


The base profile group visibility settings don't seem to be honoured.

  1. Set up some optional text fields under the 'base' profile group.
  1. Under 'Default Visibility', select the 'logged in users' option.

I expect the fields to be hidden on the registration page (for logged out users) but the fields are visible to all.

The following check apparently fails by returning true for all users if ( bp_current_user_can( 'bp_xprofile_change_field_visibility' ) )

Please note I am using BuddyPress version 1.6.5 but this version number is not available in the 'version' option list on this bug report tool (hence I have selected 1.7).

Using WordPress 3.5.1

Change History (2)

#1 @boonebgorges
11 years ago

  • Component changed from Website to XProfile
  • Keywords base profile fields removed
  • Milestone Awaiting Review deleted
  • Resolution set to invalid
  • Status changed from new to closed

Hi henrywright. Thanks for the report.

I think this ticket hinges on a misunderstanding about what "visibility" means in this context. BP interprets "visibility" as referring to the *values* of the fields, as filled in by the user. In other words, if you have a field "Phone Number", and the user 'boone' selects the visibility level Logged In Users, then only logged-in users will be able to see boone's phone number. In contrast, BP is set up so that all Base fields are available to users during registration - Visibility does not affect this.

If you have fields that you don't want to appear during registration, please put them in a group other than Base.

#2 @henrywright
11 years ago

Hi Boone

Thank you for the clarification. I understood visibility to relate to the actual form input field. Now I know it relates to the field's value.

Note: See TracTickets for help on using tickets.