Members Actions
17 unique action hooks currently map to this category, across 24 call sites.
Hook Inventory
| Hook | Edition | Call Sites | First Source |
|---|---|---|---|
fluent_community_sync_user_points | PRO | 1 | fluent-community-pro/app/Modules/LeaderBoard/LeaderBoardModule.php:96 |
fluent_community/after_sync_bp_users | Core | 2 | fluent-community/app/Hooks/CLI/BuddyPressMigrator.php:153 |
fluent_community/before_unblocking_user | PRO | 1 | fluent-community-pro/app/Http/Controllers/FollowController.php:205 |
fluent_community/before_unfollowing_user | PRO | 2 | fluent-community-pro/app/Http/Controllers/FollowController.php:76 |
fluent_community/blocked_user | PRO | 1 | fluent-community-pro/app/Http/Controllers/FollowController.php:176 |
fluent_community/followed_user | PRO | 2 | fluent-community-pro/app/Http/Controllers/FollowController.php:47 |
fluent_community/managed/after_remove | PRO | 1 | fluent-community-pro/app/Http/Controllers/ProAdminController.php:132 |
fluent_community/manager/added | PRO | 1 | fluent-community-pro/app/Http/Controllers/ProAdminController.php:108 |
fluent_community/manager/before_remove | PRO | 1 | fluent-community-pro/app/Http/Controllers/ProAdminController.php:128 |
fluent_community/manager/updated | PRO | 1 | fluent-community-pro/app/Http/Controllers/ProAdminController.php:91 |
fluent_community/members_query_ref | Core | 1 | fluent-community/app/Http/Controllers/MembersController.php:124 |
fluent_community/profile_deactivated | Core | 1 | fluent-community/app/Http/Controllers/ProfileController.php:175 |
fluent_community/reactivate_account | Core | 1 | fluent-community/app/Hooks/Handlers/PortalHandler.php:232 |
fluent_community/track_activity | Core | 3 | fluent-community/app/Hooks/Handlers/ActivityMonitorHandler.php:87 |
fluent_community/update_profile_link_providers | Core | 1 | fluent-community/app/Http/Controllers/AdminController.php:528 |
fluent_community/user_level_upgraded | PRO | 1 | fluent-community-pro/app/Modules/LeaderBoard/LeaderBoardModule.php:111 |
fluent_community/user_points_updated | Core (also fired by Pro) | 3 | fluent-community-pro/app/Modules/LeaderBoard/Http/Controllers/LeaderBoardController.php:82 |
fluent_community_sync_user_points
- Type: action
- Edition: PRO
- Call sites: 1
- When it fires: Action Scheduler task that recalculates leaderboard points for a batch of members.
Scheduled job
This action is not fired inline. It is registered as a recurring background job and runs on a schedule, so the source below is where the job is scheduled, not where it fires. Hook it with add_action() as usual.
Pro-only, part of the leaderboard module, and note the underscore-only naming — it does not use the fluent_community/ prefix. The handler walks members in batches, storing its cursor in the last_leaderboard_synced_user_id option, and re-queues itself when it runs out of time, so it fires repeatedly for one logical sync. It takes no arguments. Each recalculation that changes a total fires fluent_community/user_points_updated.
Call Sites
| Edition | Source | Parameters |
|---|---|---|
| PRO | fluent-community-pro/app/Modules/LeaderBoard/LeaderBoardModule.php:96 | No parameters |
Example
add_action('fluent_community_sync_user_points', function () {
}, 10, 0);Related: fluent_community/user_points_updated · fluent_community_daily_jobs
fluent_community/after_sync_bp_users
- Type: action
- Edition: Core
- Call sites: 2
- When it fires: Fires after a batch of BuddyPress users has been migrated into FluentCommunity.
Two call sites — the WP-CLI migrator and the admin migration screen — both firing once per batch rather than once per migration, and the controller loops until every user is done, so expect many invocations. The profiles have already been created by BPMigratorHelper::syncUser(). Pro uses it to carry BuddyPress follower relationships across.
Parameters
| # | Name | Type | Description |
|---|---|---|---|
| 1 | $users | \FluentCommunity\Framework\Database\Orm\Collection | The User models synced in this batch. |
Call Sites
| Edition | Source | Parameters |
|---|---|---|
| Core | fluent-community/app/Hooks/CLI/BuddyPressMigrator.php:153 | $users (array) |
| Core | fluent-community/Modules/Migrations/Http/Controllers/BPMigrationController.php:162 | $users (array) |
Example
add_action('fluent_community/after_sync_bp_users', function ($users) {
}, 10, 1);fluent_community/before_unblocking_user
- Type: action
- Edition: PRO
- Call sites: 1
- When it fires: Fires just before a block is lifted.
The row still exists when callbacks run; the handler deletes it on the next line. Unblocking deletes the row outright rather than restoring it to level 1, so the previous follow relationship is not recovered and no follow action fires afterwards.
Parameters
| # | Name | Type | Description |
|---|---|---|---|
| 1 | $follow | \FluentCommunityPro\App\Models\Follow | The level-0 follow row about to be deleted. |
| 2 | $xProfile | \FluentCommunity\App\Models\XProfile | Profile of the user being unblocked. |
Call Sites
| Edition | Source | Parameters |
|---|---|---|
| PRO | fluent-community-pro/app/Http/Controllers/FollowController.php:205 | $follow (mixed)$xProfile (XProfile) |
Example
add_action('fluent_community/before_unblocking_user', function ($follow, $xProfile) {
}, 10, 2);Related: fluent_community/blocked_user
fluent_community/before_unfollowing_user
- Type: action
- Edition: PRO
- Call sites: 2
- When it fires: Fires just before a follow relationship is deleted.
Fired from both the explicit POST /profile/{username}/unfollow endpoint and the toggle-follow endpoint when the toggle resolves to "unfollow". The row still exists when callbacks run — this is the last chance to read it, since the handler calls $follow->delete() on the next line. There is no matching "after" action.
Parameters
| # | Name | Type | Description |
|---|---|---|---|
| 1 | $follow | \FluentCommunityPro\App\Models\Follow | The follow row about to be deleted. |
| 2 | $xProfile | \FluentCommunity\App\Models\XProfile | Profile of the user being unfollowed. |
Call Sites
| Edition | Source | Parameters |
|---|---|---|
| PRO | fluent-community-pro/app/Http/Controllers/FollowController.php:76 | $follow (mixed)$xProfile (XProfile) |
| PRO | fluent-community-pro/app/Http/Controllers/FollowController.php:113 | $follow (mixed)$xProfile (XProfile) |
Example
add_action('fluent_community/before_unfollowing_user', function ($follow, $xProfile) {
}, 10, 2);Related: fluent_community/followed_user
fluent_community/blocked_user
- Type: action
- Edition: PRO
- Call sites: 1
- When it fires: Fires after one member blocks another.
A block is stored as a Follow row with level 0, so this fires both when a brand new row is created and when an existing follow is demoted to a block. This is a member-to-member block, not a moderation action: the endpoint explicitly refuses when the target has community moderator access, and also refuses when the caller is a moderator.
Parameters
| # | Name | Type | Description |
|---|---|---|---|
| 1 | $follow | \FluentCommunityPro\App\Models\Follow | The follow row now at level 0. |
| 2 | $xProfile | \FluentCommunity\App\Models\XProfile | Profile of the blocked user. |
Call Sites
| Edition | Source | Parameters |
|---|---|---|
| PRO | fluent-community-pro/app/Http/Controllers/FollowController.php:176 | $follow (mixed)$xProfile (XProfile) |
Example
add_action('fluent_community/blocked_user', function ($follow, $xProfile) {
}, 10, 2);Related: fluent_community/before_unblocking_user
fluent_community/followed_user
- Type: action
- Edition: PRO
- Call sites: 2
- When it fires: Fires immediately after one member starts following another.
Fired from two call sites — the explicit POST /profile/{username}/follow endpoint and the POST /profile/{userId}/toggle-follow endpoint when the toggle resolves to "follow". The Follow row has already been inserted with its default level of 1, so a callback can read $follow->id. It does not fire when an existing block is lifted, and it never fires for self-follows or for a user who already has any Follow row (including a block, which is a Follow row at level 0).
Parameters
| # | Name | Type | Description |
|---|---|---|---|
| 1 | $follow | \FluentCommunityPro\App\Models\Follow | The newly created follow row (follower_id, followed_id, level). |
| 2 | $xProfile | \FluentCommunity\App\Models\XProfile | Profile of the user being followed. |
Call Sites
| Edition | Source | Parameters |
|---|---|---|
| PRO | fluent-community-pro/app/Http/Controllers/FollowController.php:47 | $follow (mixed)$xProfile (XProfile) |
| PRO | fluent-community-pro/app/Http/Controllers/FollowController.php:120 | $follow (mixed)$xProfile (XProfile) |
Example
add_action('fluent_community/followed_user', function ($follow, $xProfile) {
}, 10, 2);Related: fluent_community/before_unfollowing_user · fluent_community/blocked_user
fluent_community/managed/after_remove
- Type: action
- Edition: PRO
- Call sites: 1
- When it fires: Fires after a user's community manager roles have been deleted.
The paired action for manager/before_remove. The segment is spelled managed rather than manager, which looks like a typo but is part of the public surface; the role row no longer exists by the time this runs.
Parameters
| # | Name | Type | Description |
|---|---|---|---|
| 1 | $user | \FluentCommunity\App\Models\User | The demoted user. |
Call Sites
| Edition | Source | Parameters |
|---|---|---|
| PRO | fluent-community-pro/app/Http/Controllers/ProAdminController.php:132 | $user (User) |
Example
add_action('fluent_community/managed/after_remove', function ($user) {
}, 10, 1);Related: fluent_community/manager/before_remove
fluent_community/manager/added
- Type: action
- Edition: PRO
- Call sites: 1
- When it fires: Fires when a user is given community manager roles for the first time.
Fires only on first assignment — updating an existing manager fires fluent_community/manager/updated instead. The roles array has already been normalised: "admin" collapses the list to just ["admin"], and course_creatror is dropped when course_admin is also present.
Parameters
| # | Name | Type | Description |
|---|---|---|---|
| 1 | $user | \FluentCommunity\App\Models\User | The user, with community_role freshly loaded. |
| 2 | $roles | array | Normalised list of role slugs. |
Call Sites
| Edition | Source | Parameters |
|---|---|---|
| PRO | fluent-community-pro/app/Http/Controllers/ProAdminController.php:108 | $user (User)$roles (mixed) |
Example
add_action('fluent_community/manager/added', function ($user, $roles) {
}, 10, 2);Related: fluent_community/manager/updated · fluent_community/manager/before_remove
fluent_community/manager/before_remove
- Type: action
- Edition: PRO
- Call sites: 1
- When it fires: Fires just before a user's community manager roles are deleted.
The community_role relation is still readable here, which is the only place to capture which roles are being taken away — the paired after-action runs once the row is gone. Note the after-action is named managed/after_remove, not manager/after_remove.
Parameters
| # | Name | Type | Description |
|---|---|---|---|
| 1 | $user | \FluentCommunity\App\Models\User | The manager being demoted, with community_role still loaded. |
Call Sites
| Edition | Source | Parameters |
|---|---|---|
| PRO | fluent-community-pro/app/Http/Controllers/ProAdminController.php:128 | $user (User) |
Example
add_action('fluent_community/manager/before_remove', function ($user) {
}, 10, 1);Related: fluent_community/managed/after_remove
fluent_community/manager/updated
- Type: action
- Edition: PRO
- Call sites: 1
- When it fires: Fires when an existing community manager's roles change.
Guarded by a value comparison, so re-saving the same set of roles fires nothing. The roles have already been normalised the same way as on add.
Parameters
| # | Name | Type | Description |
|---|---|---|---|
| 1 | $user | \FluentCommunity\App\Models\User | The manager being updated. |
| 2 | $roles | array | The new normalised list of role slugs. |
Call Sites
| Edition | Source | Parameters |
|---|---|---|
| PRO | fluent-community-pro/app/Http/Controllers/ProAdminController.php:91 | $user (User)$roles (mixed) |
Example
add_action('fluent_community/manager/updated', function ($user, $roles) {
}, 10, 2);Related: fluent_community/manager/added
fluent_community/members_query_ref
- Type: action
- Edition: Core
- Call sites: 1
- When it fires: Passes the members-directory query by reference before it is paginated.
Fired with do_action_ref_array(), so take &$query and mutate it — a return value is ignored. It runs after sorting, search and status scoping, and immediately before paginate(). The mention-autocomplete branch of the same endpoint returns earlier and never reaches this hook, so anything you add here does not affect who can be @-mentioned.
Parameters
| # | Name | Type | Description |
|---|---|---|---|
| 1 | $members | \FluentCommunity\Framework\Database\Orm\Builder | The XProfile query, passed by reference. |
| 2 | $requestData | array | The full request parameters. |
Call Sites
| Edition | Source | Parameters |
|---|---|---|
| Core | fluent-community/app/Http/Controllers/MembersController.php:124 | &$members (mixed)$request->all() (array) |
Example
add_action('fluent_community/members_query_ref', function ($members, $requestData) {
}, 10, 2);Related: fluent_community/members_api_response · fluent_community/mention_members_api_response
fluent_community/profile_deactivated
- Type: action
- Edition: Core
- Call sites: 1
- When it fires: Fires when a member deactivates their community profile.
Deactivation blanks xprofile.status to an empty string rather than setting a deactivated value, and stamps _fcom_deactivated_at on the WordPress user; the WordPress account itself is untouched. It requires either the can_deactive_account privacy setting or site-admin rights, and the profile is already saved by the time the hook runs. Reactivation fires fluent_community/reactivate_account.
Parameters
| # | Name | Type | Description |
|---|---|---|---|
| 1 | $xprofile | \FluentCommunity\App\Models\XProfile | The profile, already saved with an empty status. |
Call Sites
| Edition | Source | Parameters |
|---|---|---|
| Core | fluent-community/app/Http/Controllers/ProfileController.php:175 | $xprofile (XProfile) |
Example
add_action('fluent_community/profile_deactivated', function ($xprofile) {
}, 10, 1);Related: fluent_community/reactivate_account
fluent_community/reactivate_account
- Type: action
- Edition: Core
- Call sites: 1
- When it fires: Fires when a member reactivates their previously deactivated profile.
Reached through the portal action URL rather than the REST API, and only after a nonce check, a confirmed empty status, and the can_deactive_account privacy setting still being enabled — turn that setting off and deactivated members can no longer come back. The profile is already saved as active; the _fcom_deactivated_at user meta is deleted immediately after the hook, and the request then redirects to the portal home.
Parameters
| # | Name | Type | Description |
|---|---|---|---|
| 1 | $xprofile | \FluentCommunity\App\Models\XProfile | The profile, already saved as active. |
Call Sites
| Edition | Source | Parameters |
|---|---|---|
| Core | fluent-community/app/Hooks/Handlers/PortalHandler.php:232 | $xprofile (XProfile) |
Example
add_action('fluent_community/reactivate_account', function ($xprofile) {
}, 10, 1);Related: fluent_community/profile_deactivated
fluent_community/track_activity
- Type: action
- Edition: Core
- Call sites: 3
- When it fires: A no-argument ping that a user did something worth refreshing their last-seen timestamp for.
Fired after a post or comment activity row is written, and on every portal ticker poll. It carries no payload — the handler resolves the current profile itself, and debounces so last_activity is written at most once every five minutes. Do not treat it as a content event; use the specific content hooks for that.
Call Sites
| Edition | Source | Parameters |
|---|---|---|
| Core | fluent-community/app/Hooks/Handlers/ActivityMonitorHandler.php:87 | No parameters |
| Core | fluent-community/app/Hooks/Handlers/ActivityMonitorHandler.php:109 | No parameters |
| Core | fluent-community/app/Http/Controllers/FeedsController.php:1098 | No parameters |
Example
add_action('fluent_community/track_activity', function () {
}, 10, 0);Related: fluent_community/feed/created · fluent_community/comment_added
fluent_community/update_profile_link_providers
- Type: action
- Edition: Core
- Call sites: 1
- When it fires: Delivers the set of social link providers an administrator has enabled.
The free plugin does not persist this itself — the endpoint validates the submitted keys against the known providers, fires the hook and returns a success message, and it is Pro that writes the enabled_profile_link_keys option from a callback. Without Pro the setting appears to save but has no effect. The payload is a re-indexed list of provider keys, not a map.
Parameters
| # | Name | Type | Description |
|---|---|---|---|
| 1 | $config | array | The enabled provider keys, filtered against the registered providers. |
Call Sites
| Edition | Source | Parameters |
|---|---|---|
| Core | fluent-community/app/Http/Controllers/AdminController.php:528 | $config (mixed) |
Example
add_action('fluent_community/update_profile_link_providers', function ($config) {
}, 10, 1);Related: fluent_community/social_link_providers · fluent_community/profile_link_providers_api_response
fluent_community/user_level_upgraded
- Type: action
- Edition: PRO
- Call sites: 1
- When it fires: Fires when a member's point total moves them into a higher leaderboard level.
Fires only on a genuine level change, not on every point change: the handler first checks that the new total exceeds the old level's ceiling and then that the level slug actually differs. Because it hangs off fluent_community/user_points_updated it can fire from the hourly point recalculation or the daily sync job, not only from live activity. It is one-directional — there is no downgrade action. Requires the leader_board_module feature to be enabled; FluentCRM automations use it as a trigger.
Parameters
| # | Name | Type | Description |
|---|---|---|---|
| 1 | $xprofile | \FluentCommunity\App\Models\XProfile | The member who levelled up, with the new total_points already saved. |
| 2 | $newLevel | array | The new level — title, tagline, slug, level, min_points, max_points. |
| 3 | $oldLevel | array | The previous level, same shape. |
Call Sites
| Edition | Source | Parameters |
|---|---|---|
| PRO | fluent-community-pro/app/Modules/LeaderBoard/LeaderBoardModule.php:111 | $xprofile (XProfile)$newLevel (mixed)$oldLevel (mixed) |
Example
add_action('fluent_community/user_level_upgraded', function ($xprofile, $newLevel, $oldLevel) {
}, 10, 3);Related: fluent_community/leaderboard_api_response
fluent_community/user_points_updated
- Type: action
- Edition: Core (also fired by Pro)
- Call sites: 3
- When it fires: Fires after a member's total leaderboard points are recalculated to a different value.
Points are recalculated lazily and cached for an hour per user, so this fires at most once an hour per member under normal traffic, and not at all when the recalculated total matches the stored one. The profile is already saved with the new total; $oldPoints is the only way to see the delta. Pro's leaderboard listens here to detect level changes.
Parameters
| # | Name | Type | Description |
|---|---|---|---|
| 1 | $xprofile | \FluentCommunity\App\Models\XProfile | The member profile, already saved with the new total. |
| 2 | $oldPoints | int | The point total before the recalculation. |
Call Sites
| Edition | Source | Parameters |
|---|---|---|
| PRO | fluent-community-pro/app/Modules/LeaderBoard/Http/Controllers/LeaderBoardController.php:82 | $profileModel (mixed)$oldPoints (mixed) |
| PRO | fluent-community-pro/app/Modules/LeaderBoard/Services/LeaderBoardHelper.php:189 | $xprofile (XProfile)$oldPoints (mixed) |
| Core | fluent-community/app/Hooks/CLI/Commands.php:153 | $xProfile (XProfile)$oldPoints (mixed) |
Example
add_action('fluent_community/user_points_updated', function ($xprofile, $oldPoints) {
}, 10, 2);