[envieme]

Just one more nudge on this. As this is really important in securing the privacy on my site members.

I was successfully able to set my own profile privacy levels editing it from front end. So I see the bp-x-profile-visibility-levels field in user_meta table with value:
a:7:{i:1;s:6:”public”;i:2;s:8:”loggedin”;i:3;s:8:”loggedin”;i:4;s:8:”loggedin”;i:7;s:10:”adminsonly”;i:8;s:10:”adminsonly”;i:11;s:6:”public”;}

Is there a simple SQL that I can execute to make all users get this field in their user meta and set to this value? Can someone with SQL knowledge help?

Thanks

[envieme]

Hi there, just nudging to see if there’s a work around or hack in BP code I can do to enforce desired x-profile visibility levels as in my case users need not have an option to choose their visibility levels. So I hope someone can point me in the right direction on how to hardcode the visibility levels for my x-profile fields in the code.

Many thanks.

[envieme]

I haven’t tested it on a fresh install and assume the problem is with my instance. May be after the import something got messed up.

But then when new members register, I expect Buddypress should be setting the default profile visibility settings which is not the case.

Any ideas on what could have gone wrong would be really helpful. Thanks.

[envieme]

@bp-help Thanks for reverting back quickly. I did search before I posted and the only one that found similar to my case was https://buddypress.org/support/topic/how-do-i-hide-extended-profile-fileds-from-users/

But I haven’t used the plugin the post mentions about, I did a backend database import by exporting and importing sql.

And I have done all the standard steps I do when something is amiss in WP or BP like deactivating all plugins and reverting to default theme. Yet the problem persists. Further I noticed in my DB that a meta field bp_xprofile_visibility_levels is only set for a handful of users in the users_meta table. Though it being set doesn’t really set the visibility level properly.