Member-to-Member Blocks: Sample Flows

This article presents possible use cases and corresponding sample flows that you can support. It provides a useful starting point as you plan your implementation.

Let members manage their blocked list

Members who block others may later want to review who they blocked and undo a block. For example, a community site can offer a "Blocked members" page in the member's account settings.

To let members manage their blocked list:

1. Call List Current Member Blocking with the current member's identity, and save the returned blockedMemberIds.
2. Call Query Members with a Wix user or app identity, filtering by the saved IDs, to retrieve each blocked member's name and profile photo for display.
3. When the member selects a blocked member to unblock, call Unblock Member with the current member's identity, passing that member's ID as memberId.

Hide content from blocked members in a custom feed

If your app shows member-generated content, such as posts or comments, it should respect blocks the same way the Members Area does. Neither member in a block should see content from the other.

To hide content from blocked members in a custom feed:

1. Before building the feed for a member, call List Member Blocks, passing that member's ID as memberId. Use cursorPaging to retrieve all pages.
2. Save the memberId of every returned block, regardless of blockDirection.
3. Remove content created by any of the saved members from the feed before you display it.