BuddyPress.org

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

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.

I’ll be exploring this further: https://buddypress.trac.wordpress.org/ticket/9349

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.

I’m the author of XYZ Age Verification. (There’s a free version in the WordPress.org repository.) I have integrations built for other membership systems and would be happy to add support for BuddyPress. I don’t have any personal experience with BuddyPress, yet.

Since the term is actually created/deleted and only the admin response fails, this does sound more like BuddyPress interfering with the AJAX response than the taxonomy operation itself.

I’d inspect the browser Network tab for the admin-ajax.php response and compare it with BuddyPress disabled. If there’s extra output, malformed JSON, or a delayed hook firing after wp_delete_term, that should point to the component causing it. Given that it happens with both core and custom taxonomies, the term count may just be exposing a timing/scaling issue rather than being the root cause.

Hi,

There is an old plugin called BuddyPress Full user Sync, but, all it does, is translate bp xprofile fields into a WP equivalent. Would that help?
But, being five years out of date, it is likely to have security issues, etc.
So I’m looking to fork it, and integrate the two plugins.
Perhaps add more features and better diagnostics.
which bp features are you looking to sync?
I think anything more than the xprofile fields is likely to get quite complex.

One BuddyPress menu sounds easier to navigate. It would be useful to show only the enabled components underneath it, so sites using just profiles and activity don’t get extra menu items they don’t need.

Yeah, I’d check the BuddyPress User Handbook first. it should cover both setting up the buttons and making the signup fields actually editable.

Yeah, I’d avoid editing the BuddyPress plugin file directly too, since an update could overwrite the change. I’d first check whether the theme is overriding the avatar template, and if not, Loco Translate sounds like a cleaner way to change that text.

With a few exceptions, those who are “Moderators” and “Keymasters” are members of the BuddyPress development team.

Having stated the above, you are welcome to open a New Ticket because this has run its course as a forum topic.