Hi Brajesh,

We don’t yet have access to expertise to extend the endpoints.
Would you be open to extending the BuddyPress API endpoints to include the block and unblock functionality at some point in the future? We’d be happy to pay for this.

Thanks. 🙂

Hi Brajesh,

We’re still doing some testing. Would it be possible to still have the blocker be able to access the blocked person’s profile? This would be for unblocking purposes, and would also keep how the plugin works on the API and website consistent.

Thank you. 🙂

Hi Brajesh,

Thank you for looking into this. Regarding the client co-ordination, are you able to give us some advice on how we would go about achieving that?

We’ve had a quick chat with our app developer and he says (verbatim) :

“If BuddyDev can change the /wp-json/buddypress/v1/members API call to exclude the blocker’s profile when a blocked person does a search then we could do the following;
– Anywhere in the app where a person (e.g. Tim) tries to open the another person’s profile (e.g Jill), the app will do a /wp-json/buddypress/v1/members API call with Jill’s “user_login” in the “search” field as part of the API call
– The app will go through any returned results to check if the “user_login” matches, if there is a matching “user_login” that means Jill has not blocked Tim, and the app will proceed to Jill’s profile.
– If there is no matching “user_login”, that means Jill has blocked Tim, and the app will display a notification to say the user’s profile cannot be viewed (or something like that).”

Does this seem like a feasible approach?

We will look forward to hearing back from you. 🙂

Thanks.

Hi Brajesh,

Thank you for your reply and looking into this! 🙂

If it’s any help, we are using the “JWT Authentication for WP REST API” plugin by Enrique Chavez (https://wordpress.org/plugins/jwt-authentication-for-wp-rest-api/).

Thanks again.

Thanks again, Brajesh. We’ve reported this to the Gwangi authors.