Hi Nifty,
Thank you for reporting the issue.

We logout the user and clear all their sessions(managed by WordPress) on suspension. It seems that the JWT auth plugin might be managing their own token that needs to be invalidated. We will look into it and add the support within a week if doable.

Regards
Brajesh

Hi David,
Thank you.
If the feed is not loading, Please disable the asset cleanup temporarily and test.

You may disable some part of BuddyPress assets but I won’t suggest it. saving a few Kb is not going to make much of a difference in today’s world where for most of the part, speed is a lot better than what it used to be in 2010(That’s a general assumption, your actual choice should depend on the demography of your users).

Regards
Brajesh

Hi Tosin,
I am certainly expecting that. i haven’t been to the meeting for couple of months, so not sure when it will be available as part of core.

Regards
Brajesh

Hi Abhist,
Welcome to BuddyDev forums.

Thank you for the question. Here are my answers.

1. The profile field visibility is a BuddyPress core feature and has nothing to do with teh xprofile cusotm field types plugin.

2. You can not change the visibility for a user. It is saved for each field of the user. So, if you have 20 fields, you will need to update it for all the 20 fields.

Here is the function which is used to set it

xprofile_set_field_visibility_level( $field_id, $user_id, $visibility_level );

Where $field_id is the numeric xprofile field id.
$user_id is the numric id of the user in context.
$visibility_level is a string which is one of the registered visibility levels(e.g ‘loggedin’).

Hope that helps.

PS:- The visibility setting is stored in user meta, so if you wnat to avoid too many queries, you can directly update the user meta key ‘bp_xprofile_visibility_levels’ with an associative array containing field id as key and its visibility as the value.

Regards
Brajesh