Yes, the subdomain approach is the sensible one, since BuddyPress needs WordPress and bolting it onto a custom shop usually creates more work than it saves. Keeping the logins separate at first is fine for a small community, and matching the header and footer is theme work. For features, Extended Profiles and the Activity stream are the two to switch on in Settings > Components, and I’d leave Friend Connections and Internal Messages off until people actually ask for them. Photo uploads aren’t in the core list, so that part would need an add-on. On a modest VPS with tens of users the load should be fine, and the Members screen has a Mark as Spammer option for bad accounts.
Hello,I run a small flower delivery shop in Nizhny Novgorod, Russia. The shop itself is built on a custom PHP codebase — not WordPress — and rebuilding it is not on the table right now.What we would like to add next to it is a small community section for customers: a place where people can share photos of how the bouquets looked at their celebrations, leave feedback, and discuss flower care. BuddyPress keeps coming up in my research, so I would like to ask people with real production experience a few questions before we commit:1. Is it realistic to run BuddyPress as a separate WordPress install on a subdomain (community.ourshop.example) alongside a non-WP main site, with a shared visual header/footer, without deep integration? Or does this path usually create more problems than it solves?2. Which BuddyPress components fit a retail audience best? We would need roughly: member profiles, photo uploading, and a simple activity/discussion stream. We do not need friend graphs or private messaging at the start.3. How heavy is BuddyPress on shared hosting in practice? Our shop is on a modest VPS, and the community would start with tens of active users, not thousands.4. Are there known pitfalls with spam control for public community sections, especially for small non-English communities? Any extension you would consider essential from day one?I would be grateful for any honest experience — including “do not do it this way”. Thanks for reading.
This was addressed and fixed in ticket 9350 which was included in the releases of:
Version 14.5.6
Version 12.7.4
Version 11.6.4
Hello all. Versions 14.5.6, 12.7.4 & 11.6.4 are Security Releases. Please update, accordingly, when possible.
Version 14.5.6
Version 12.7.4
Version 11.6.4
You may need to check BuddyPress notification settings or use a small custom code snippet to add multiple recipients. Hopefully someone can share the exact solution.
@rthwm
“BuddyPress Member Type” is not a plugin that is maintained by the BuddyPress team. You should contact the author of said plugin.
Just a heads-up, Wordfence is flagging as abandoned.
The Plugin “BuddyPress Member Type” appears to be abandoned (updated November 3, 2024, tested to WP 6.7.1).
Type: Plugin Abandoned
Has anyone had an update on this issue with 14.5.4? Do I need to delete buddypress?
Hello,
we use BuddyPress Version 14.5.4 with WordPress Version 7.1.4
I don’t know how to change the recipients of certain activities.
When a user writes a new question, only one person gets the notification. We want two persons to get these.
I searched through all menu entries, but can’t find any hints to solve my problem.
Can anybody help?
Thanks and kind regards,
Regina
Thanks for bringing this up. If Patchstack is reporting a high-priority vulnerability affecting BuddyPress 14.5.4, it would be worth checking the exact vulnerability details and affected versions before assuming that the latest security release is fully protected.
For now, I would recommend keeping regular backups, reviewing the official BuddyPress security announcements, and monitoring the issue for an update from the development team. Hopefully, the maintainers can clarify whether this vulnerability affects the released versions and whether another patch is needed.
I can also confirm the above. Following the upgrade to BuddyPress 14.5.4, the registration form stopped working. Submitting the form simply reloads the page without creating an account.
Rolling back to version 14.5.2 immediately fixes the issue.
I can confirm that I am experiencing what appears to be the same issue.
After upgrading BuddyPress from 14.5.2 to 14.5.4, the registration form on my site stopped working. Rolling BuddyPress back to 14.5.2 immediately resolved the problem and registrations are working normally again.
I do not use Youzify, so in my case the problem does not appear to be related specifically to a conflict between BuddyPress and Youzify.
The site was working normally with BuddyPress 14.5.2 before the upgrade. I have currently remained on 14.5.2 because registration is an essential function of the site.
I have also opened a ticket about the issue. If useful, I can provide additional information about my WordPress installation, active plugins, PHP version, or other environment details to help reproduce the problem.
Patchstack shows that BuddyPress Plugin <= 14.5.4 is vulnerable to a high priority Deserialization of untrusted data. So we need another security release urgently please!
found a log in my mail from before the reroll, perhaps it helps:
When seeking help with this issue, you may be asked for some of the following information:
WordPress version 7.1.4
Active theme: Astra Child (version 4.12.3.1770806820)
Current plugin: BuddyPress (version 14.5.4)
PHP version 8.3.36
Error Details
=============
An error of type E_ERROR was caused in line 725 of the file /var/www/html/wp-content/plugins/buddypress/bp-templates/bp-legacy/buddypress-functions.php. Error message: Uncaught TypeError: urldecode(): Argument #1 ($string) must be of type string, array given in /var/www/html/wp-content/plugins/buddypress/bp-templates/bp-legacy/buddypress-functions.php:725
Stack trace:
#0 /var/www/html/wp-content/plugins/buddypress/bp-templates/bp-legacy/buddypress-functions.php(725): urldecode(Array)
#1 /var/www/html/wp-includes/class-wp-hook.php(353): bp_legacy_theme_ajax_querystring(”, ‘activity’)
#2 /var/www/html/wp-includes/plugin.php(206): WP_Hook->apply_filters(”, Array)
#3 /var/www/html/wp-content/plugins/buddypress/bp-core/bp-core-template.php(1157): apply_filters(‘bp_ajax_queryst…’, ”, ‘activity’)
#4 /var/www/html/wp-content/plugins/buddypress/bp-activity/bp-activity-filters.php(560): bp_ajax_querystring(‘activity’)
#5 /var/www/html/wp-includes/class-wp-hook.php(355): bp_activity_heartbeat_last_recorded(Array, Array)
#6 /var/www/html/wp-includes/plugin.php(206): WP_Hook->apply_filters(Array, Array)
#7 /var/www/html/wp-admin/includes/ajax-actions.php(3554): apply_filters(‘heartbeat_recei…’, Array, Array, ‘front’)
#8 /var/www/html/wp-includes/class-wp-hook.php(353): wp_ajax_heartbeat(”)
#9 /var/www/html/wp-includes/class-wp-hook.php(377): WP_Hook->apply_filters(”, Array)
#10 /var/www/html/wp-includes/plugin.php(523): WP_Hook->do_action(Array)
#11 /var/www/html/wp-admin/admin-ajax.php(192): do_action(‘wp_ajax_heartbe…’)
#12 {main}
thrown
11.6.3 contains security fixes based on what was conveyed in the changelog.
Version 11.6.3
I’m still using the 11.x version of Buddypress, updated my version today to 11.6.3
All seems fine.
Could somebody please confirm this is a secure version?
Thanks.
Thanks for the notification. The other day, a ticket was opened by another user. See ticket 9350 – Buddypress 14.5.4 registration form not working
You are welcome to monitor and/or add any other info to the ticket that will help to identify the cause which should lead to finding a remedy.
There was an attempt to address the vulnerability in 14.5.4, see the Version 14.5.4 changelog. The 5th bulleted item reads:
Prevent exploit of maybe_unserialize() function. Special thanks to a WordFence researcher who first reported this issue responsibly.
At the moment, I’m not sure why there is a conflict in understanding. We will investigate this further.
We noticed that the latest version, 14.5.4, has a high priority Deserialization of untrusted data vulnerability. Here is the link to Patchstack that details the vulnerability: https://patchstack.com/database/wordpress/plugin/buddypress/vulnerability/wordpress-buddypress-plugin-14-5-0-authenticated-subscriber-php-object-injection-vulnerability. We wanted to bring this to your attention because the current version of the plugin is vulnerable and there there is currently no update that patches the issue. Please issue an update to the plugin that patches the issue and let us know when the vulnerability is patched. Thanks very much!
Hello all. Versions 14.5.4, 14.5.3, 12.7.3 & 11.6.3 are Security Releases. Please update, accordingly, when possible.
Version 14.5.4
Version 14.5.3
Version 12.7.3
Version 11.6.3
You should check to see if you are loading the bp-templates/bp-nouveau/css/buddypress.css file that has the CSS rules that can be found in Changeset 14203.
I like this idea. Having all BuddyPress settings and features under one main menu would make the dashboard easier to navigate, especially for beginners. It can be confusing when related options are spread across different sections. A unified menu with clearly organized submenus would make managing a community much simpler.
This was fixed in versions 14.5.0 & 12.7.0 via ticket 9324. What version are you using?
The best approach depends on the level of assurance the site needs and the privacy requirements that apply to its users. I’d look for a solution that minimizes the personal data collected while still meeting the site’s legal and safety requirements. It’s also worth checking whether the verification plugin integrates properly with BuddyPress registration and profile workflows.