BuddyPress doesn’t notify anyone when their activity gets favorited. Check the core notification settings and you’ll find toggles for friend requests, mentions, group invitations, and private messages, but nothing for favorites. A member can hunt through their whole community, mark a dozen posts as favorites, and the people who wrote them will never know unless they happen to scroll back through their own activity stream and notice the star. BuddyPress Favourite Notification closes that one specific gap, nothing more, nothing less.
Why This Gap Exists in the First Place
BuddyPress’s favoriting feature has been part of core for a long time, long enough that a lot of site owners assume it must already trigger some kind of notification, the same way a comment or a mention does. It doesn’t, and that’s not an oversight so much as a design choice from a much earlier era of the plugin. Favoriting was originally treated as a lightweight, private bookmarking action, closer to saving a post for later than to a public social signal. Facebook’s like button and Twitter’s heart didn’t exist in their current notification-driving form when BuddyPress’s activity component was first built, so there was no obvious precedent pushing the core team to wire favorites into the notification system the way mentions and friend requests were.
That history matters less than the practical result: on a modern community site, where members expect a like or a favorite to produce at least a small acknowledgment, the silence reads as a bug even though it’s working exactly as core BuddyPress was designed. Site owners who notice usually find out from a member asking “does anyone see when I favorite their post?” rather than from anything in the documentation.
What It Does
Two things, and only two things: it lets members mark or unmark an activity as a favorite (already possible in core BuddyPress), and it sends a live notification to the activity’s owner when that happens. Nothing else, no leaderboards, no featured-activity dashboards, no extra settings screen. It’s a deliberately narrow plugin, and that narrowness is arguably its best feature. A lot of engagement plugins try to bolt on gamification, badges, and points systems around a simple action, and end up adding admin overhead that most communities never touch. This one does the one job it advertises and stops.
Setup is install-and-activate, no configuration screen. It does need the BuddyPress notifications component enabled to work, which is worth double-checking before assuming the plugin itself is broken if notifications don’t show up after activation. Go to BuddyPress > Settings and confirm Notifications is checked among the active components. If it isn’t, nothing built on top of BuddyPress’s notification system, including this plugin, has anywhere to send its alerts.
Why the Notification Actually Matters for Engagement
It’s worth being specific about the mechanism here rather than just asserting that notifications are good. A member who favorites something and gets zero acknowledgment isn’t discouraged from favoriting again, favoriting is nearly frictionless, but the person on the receiving end never learns that their post connected with anyone. Over time, on a community with this gap, contributors quietly lose the small feedback loop that keeps them posting. They see comments, they might see a reply, but the softer signal of “people are engaging even when they don’t say anything” is invisible. Adding the notification doesn’t change member behavior around favoriting itself, it changes whether the person who gets favorited actually knows it happened, which is a different and arguably more important half of the loop.
This matters more on communities where posting takes real effort, a long-form update, a detailed answer to a question, a piece of original content, than on ones built around quick one-line status updates. The people writing that longer content are the ones most sensitive to feeling like their effort disappeared into silence, and they’re also usually the members a community can least afford to lose.
Where the Notification Shows Up
Once active, the plugin routes through BuddyPress’s existing notification pipeline rather than inventing a new one. That means favorited members see the alert in the same place they’d see a mention or a friend request, the notifications bell or dropdown in their member menu, depending on which theme is running. Because it uses the native pipeline instead of a custom overlay, it also inherits whatever notification styling and behavior your theme already applies, there’s no separate visual system to theme or maintain on top of what BuddyPress already provides. On BuddyX and most well-built BuddyPress themes, that means the favorite notification looks and behaves exactly like every other notification type a member already understands.
Whether that notification also triggers an email depends on the member’s own notification preferences under BuddyPress’s Notifications settings tab, assuming your BuddyPress email notification settings are configured to include third-party or custom notification types. On a default setup, most members will see it in-app rather than by email unless they’ve specifically opted into broader email notifications, which keeps this feature from adding to inbox noise for most communities.
Setting Expectations Before Installing
A few things worth knowing going in, since a two-function plugin can still surprise you if you assume it does more than it does:
- It doesn’t retroactively notify for existing favorites. Only favoriting actions that happen after activation trigger a notification. Anyone who favorited something last month won’t suddenly generate a backlog of alerts.
- It doesn’t add a favorites count or leaderboard anywhere. If you want to surface “most favorited” content or members, that’s a separate build, this plugin only handles the notification side of an existing core action.
- It respects existing favorite/unfavorite toggling. Unfavoriting doesn’t send a notification, only the act of favoriting does, which matches how most people expect a like-style notification to behave.
- It works across both the sitewide activity stream and group activity streams, since favoriting itself is a core BuddyPress action available in both contexts.
Worth Knowing Before You Deploy
The plugin hasn’t seen an update since late 2024, not abandoned (it’s a two-function plugin with little surface area to break), but old enough that it’s worth a quick staging test before deploying on a site running a recent BuddyPress release. In practice, plugins this narrow in scope tend to age well precisely because they’re not chasing new BuddyPress features or API changes, they hook into one action and one notification call, both of which have been stable in BuddyPress core for years. That said, “probably fine” isn’t the same as “confirmed fine,” and a five-minute staging check costs a lot less than discovering a conflict on a live community site.
A reasonable staging test: activate the plugin, log in as two separate test accounts, favorite an activity update from one account, and confirm the notification appears for the other account within a normal page refresh. Then check that unfavoriting doesn’t produce a stray notification, and that the plugin doesn’t throw any PHP warnings in your debug log during either action. That covers the entire functional surface of the plugin in under five minutes.
Building This Yourself Instead
If you’d rather not add another plugin to your stack, the underlying mechanism is simple enough that a developer comfortable with BuddyPress hooks can replicate it in a few dozen lines. Favoriting in BuddyPress fires the bp_activity_add_user_favorite action when a member marks an activity as a favorite, passing the activity ID and the user ID doing the favoriting. A custom function hooked to that action can look up the activity’s original author with bp_activity_get_meta() or a direct query against the activity object, then fire bp_notifications_add_notification() to create the alert, matching the same call BuddyPress core uses internally for mentions and other built-in notification types.
The tradeoff is exactly what you’d expect: writing it yourself means one less plugin dependency and full control over exactly how and when the notification fires, custom digest logic, excluding self-favorites more gracefully, whatever your community specifically needs. It also means you own the maintenance burden if a future BuddyPress core update changes how the favoriting hook or the notification API behaves. For most sites, the free plugin covers the need without the custom development cost. For a larger platform with a dedicated developer already touching BuddyPress hooks regularly, folding this into existing custom code isn’t a large lift.
Troubleshooting: Notification Isn’t Appearing
If you’ve activated the plugin and favorites still aren’t producing a notification, work through these in order rather than assuming the plugin itself is broken:
- Confirm the Notifications component is active under BuddyPress > Settings > Components. This is the single most common cause, and it’s easy to overlook on a site that never used notifications for anything else.
- Check for a caching layer serving a stale notification count. Object caching or aggressive page caching can occasionally delay a notification count update on the front end even though the underlying database record was created correctly. Clear the relevant cache and reload.
- Test with two genuinely separate accounts, not two browser tabs logged into the same account. BuddyPress generally doesn’t notify a member for favoriting their own content, which is expected behavior, not a bug, but it’s a common false alarm during testing.
- Check your theme’s notification dropdown markup. A heavily customized theme that overrides BuddyPress’s default notification template can sometimes filter out notification types it doesn’t explicitly recognize. If other notification types (mentions, friend requests) display correctly but this one specifically doesn’t, that’s a strong signal to check the theme’s notification template code rather than the plugin.
- Confirm no other plugin is hooking the same action and short-circuiting it. Rare, but a heavily plugin-laden BuddyPress install can occasionally have two plugins competing for the same hook in a way that breaks one of them silently.
How This Compares to Building Engagement Around Comments Instead
It’s worth stepping back and asking whether favoriting is even the engagement signal your community should be investing notification infrastructure around in the first place. Favoriting is a low-effort action, which is exactly its appeal, but low-effort signals also carry less social weight than a comment or a reply. A community that’s already comment-heavy may get more return on making sure comment notifications are fast, reliable, and well-formatted than on adding a favorite notification layer, since comments are already the stronger engagement signal doing more of the retention work. Communities that lean more toward quick status-update culture, closer to a feed than a forum, tend to get proportionally more value from surfacing the favorite signal, since it’s often the only acknowledgment a quick post gets at all. There’s no wrong answer here, just worth being deliberate about which engagement loop actually matches how your specific community behaves before assuming this particular gap is the one worth closing first.
If You Need More Than Just Favorites
Favorite notifications solve one specific engagement gap, but they’re rarely the only one on a community that’s been running a while without much attention to its feedback loops. If members are also asking why they can’t easily share an update outside the community, BuddyPress Activity Social Share covers that adjacent gap with one-click sharing on activity updates. And if profile depth is the actual bottleneck, members feeling like their profile doesn’t represent them well, that’s a separate problem best solved with a dedicated profile plugin rather than anything notification-related. Treat each engagement gap as its own small fix rather than reaching for one plugin to solve all of them at once, that’s generally how you end up with the leaner, more maintainable plugin stack in the first place.
Measuring Whether It Actually Changed Anything
Installing a notification plugin and assuming it worked because nothing broke is a common way to under-invest in following through on a small engagement fix. If you have access to activity data, a quick before-and-after comparison over two to three weeks is worth running: total favorite actions per week, and separately, whether members who get favorited are posting again sooner than they were before. You’re not looking for a dramatic swing, a two-function notification plugin isn’t going to transform a quiet community into a busy one on its own, you’re looking for a small, real signal that closing the feedback loop nudged people who’d otherwise gone quiet back into posting. If you don’t have the appetite for that level of tracking, a simpler gut check works too: ask a handful of active members directly whether they’ve noticed the new notification and whether it changed how they think about favoriting or being favorited. Direct member feedback on a change this small is often more useful than a spreadsheet, since the effect you’re after is emotional (feeling noticed) rather than strictly behavioral.
A Note on Notification Fatigue
Every notification type you add competes for attention with every notification type already in place. On a very active community where favoriting happens constantly, adding a notification for every single favorite can tip from “nice acknowledgment” into “another badge cluttering the bell icon,” particularly for a prolific poster who might get favorited dozens of times a day. There’s no built-in throttling or digest-batching in this plugin specifically, it fires one notification per favorite action, full stop. If your community is large and active enough that this becomes noisy rather than pleasant, that’s a signal to look at BuddyPress’s broader notification settings and consider whether a digest-style approach (batching notifications into a periodic summary rather than a live stream) fits your community better than instant, individual alerts for every minor engagement action. That’s a bigger architectural decision than this one plugin, but it’s worth having in mind before adding several more granular notification types on top of what you already have.
Quick Answers
Does this plugin work with BuddyBoss? It’s built against BuddyPress’s core notification and activity APIs, which BuddyBoss Platform is built on top of, so it generally works in BuddyBoss-powered communities as well, though given the plugin’s age it’s worth the same staging test recommended above before relying on it in a BuddyBoss environment specifically.
Can I disable the notification for specific members or groups? Not through the plugin itself, it applies sitewide once active. Per-member or per-group control would require custom code layered on top.
Will this slow down my site? No meaningfully measurable impact. It hooks into an action that already fires when a member favorites something, adding one notification insert to an event that’s already happening rather than introducing a new heavy process.
What happens if I deactivate BuddyPress’s notification component later? The plugin has nowhere to send its alert and effectively goes silent, favoriting itself still works as a core BuddyPress feature, it’s just the notification layer that depends on that component being active.
Does it mark notifications as read automatically once a member views their activity stream? It follows BuddyPress’s standard notification read/unread behavior, the same as any other core notification type, so a member clicking through their notifications dropdown or visiting the relevant activity item marks it read the same way it would for a mention or comment notification.
Is there a way to test this safely on a live site without emailing real members? Test with two staff or admin accounts rather than live member accounts, and confirm your site’s email notification settings for the notifications component aren’t set to broadcast to all members before running any test that could theoretically trigger an email. In-app notification testing carries essentially no risk either way, since it only affects the two accounts directly involved in the test action.
Pricing
Free. Download it here.
Interesting Reads:
How Does the Social Sharing Feature Increase User Engagement Within the BuddyPress Community?
How Does Profile Pro Enhance the Functionality of BuddyPress Profiles?
How Do Shortcodes Enhance the Functionality and Display of BuddyPress Components?