BuddyPress.org

The simplest way to disable, at the moment, is to squelch the update_user_meta() call. Untested, but something like this should work:

add_filter( 'update_user_metadata', function( $should_update, $object_id, $meta_key ) {
    if ( 'last_activity' === $meta_key ) {
        return false;
    }

    return $should_update;
}, 10, 3 );

I’ve opened a ticket to discuss disabling the backward compatibility feature in BP. https://buddypress.trac.wordpress.org/ticket/7882#ticket

This is not a BuddyPress question.

It’d been helpful if you’d linked to it, @venuitius 😉
I’ve just tried searching myself and couldn’t find it.

At any rate, this is not a BuddyPress problem — it’s an out of date and unsupported plugin.
We are looking at trying to introduce some of these field types into the main BuddyPress plugin for future versions (it will happen, just a matter of number of contributors and time).

Our position is that we want BuddyPress to provide tools that help site owners comply with privacy legislation.

Our 4.0 release, about a month away, will be our first pass at this. Read the latter comments in https://buddypress.trac.wordpress.org/ticket/7698 for linked/related tickets, as well as https://buddypress.trac.wordpress.org/query?status=reopened&status=assigned&status=reviewing&status=new&status=accepted&group=status&milestone=4.0 to see all issues assigned to 4.0 (7855, 7856, 7866, 7867, etc).

We have this fixed for our next release, v3.1. This will be released next week (Wednesday) at the latest. The bug was addressed at https://buddypress.trac.wordpress.org/ticket/7869

@alpokoskiniva “Repair email” deletes the emails from the “Emails” menu, then re-adds them. You don’t need to do this unless you’ve added a translation to your site after installing BuddyPress, and want the translated emails, or if you’ve made a code change to the email language in the BuddyPress files, which is what @filipponeri20 has done. We strongly recommend that no-one ever changes a core file of BuddyPress, because it will be overwritten when you update.

You need to talk to whoever runs your server. It’s possible the PHP error logging configuration is different on each.

Furthermore, you can see the problem comes from the folder /plugins/buddypress-links, which is not BuddyPress itself.

I haven’t seen BuddyPress Links in a long time — I’m assuming it’s not compatible, and that your PHP configuration is indeed different (you were probably suppressing the error before).

We can’t help more.

I have fresh WordPress installation version 4.96 and Buddypress 3.0.

Unfortunately the version 3.0 of Buddypress does not send confirmation email to new registered users. I removed the version 3.0 and tested the version 2.9.4. So in that version it worked.

Several websites are in trouble if the registration process does not work as expected. Otherwise Buddypress is awesome plugin and thanks to the developers. Hopefully the team can fix the case soon.

It seems like parameters 6-8 are no longer being passed with the new version of buddypress?

This is my code which has been working:

function bp_custom_format_buddypress_notifications( $action, $item_id, $secondary_item_id, $total_items, $format = 'string', $component_action, $component_name, $id ) {

  if ("wbp_party" === $component_name && is_user_logged_in()) {

    ...

if ( 'string' === $format ) {
      $return = apply_filters( 'wbp_notification_filter','<a href="'.$custom_link.'">'.$custom_title.'</a> ', $custom_text, $custom_link );

      // Deprecated BuddyBar
    } else {
      $return = apply_filters( 'wbp_notification_filter_array', array(
        'text' => $custom_text,
        'link' => $custom_link
      ), $custom_link, (int) $total_items, $custom_text, $custom_title );
    }

    return $return;
  }

}
add_filter( 'bp_notifications_get_notifications_for_user', 'bp_custom_format_buddypress_notifications', 10, 8 );

I also had the same issue. It has been working for the past six months but for some reason I’m now getting the error:

[Thu May 31 03:17:57.637007 2018] [proxy_fcgi:error] [pid 20994:tid 140462744499968] [client 76.95.217.178:52226] AH01071: Got error 'PHP message: PHP Warning: Missing argument 6 for bp_custom_format_buddypress_notifications(), called in /opt/bitnami/apps/wordpress/htdocs/wp-includes/class-wp-hook.php on line 286 and defined in /opt/bitnami/apps/wordpress/htdocs/wp-content/plugins/wbp/lib/party/notifications.php on line 40\nPHP message: PHP Warning: Missing argument 7 for bp_custom_format_buddypress_notifications(), called in /opt/bitnami/apps/wordpress/htdocs/wp-includes/class-wp-hook.php on line 286 and defined in /opt/bitnami/apps/wordpress/htdocs/wp-content/plugins/wbp/lib/party/notifications.php on line 40\nPHP message: PHP Warning: Missing argument 8 for bp_custom_format_buddypress_notifications(), called in /opt/bitnami/apps/wordpress/htdocs/wp-includes/class-wp-hook.php on line 286 and defined in /opt/bitnami/apps/wordpress/htdocs/wp-content/plugins/wbp/lib/party/notifications.php on line 40

How about Pseudonymisation and encryption of user data in BuddyPress?

As I understand this must also be achieved under the GRPR directive.

(And yes thank you @buddyboss for your initivite, it is step in the right direction).

The “Articles” tab isn’t something that BuddyPress adds. If the count isn’t compatible with Nouveau then I suggest you let the plugin author know at https://wordpress.org/support/plugin/social-articles

BuddyPress Xprofile Fields Type has been withdrawn and if unsupported.

If you do a lookup for BuddyPress Xprofile Custom Fields (note the extra s) you will find that there’s a new fork of this plugin that should fix the problem.

We have released a plugin to help with GDPR compliance: https://wordpress.org/plugins/bp-gdpr/
This will be helpful for now, until there is a major BuddyPress release with these features.

Is there a date for a fix to BuddyPress for this issues?

You can try these patches https://buddypress.trac.wordpress.org/ticket/7845

@shahriar83 You have already created a thread with BP activity plus support, Explain to them how to replicate the issue.

You can replicate the issue with Template Pack BuddyPress Nouveau after BP 3.0 install using WordPress Default theme “Twenty Seventeen” at singe group activity page.

I had some issues with this earlier too, using the code supplied in this thread should clear up your issue.

Here’s the code if you’re unable to click the link for some reason. You should put it in your bp-custom.php file.

function toa_check_page_reqiurement_and_lie_to_buddypress ($is, $component) {
    global $bp;
    if ($is || "activity" !== $component) return $is;
    if ((defined('BP_GROUPS_SLUG') && bp_is_groups_component() && 'activity' == $bp->current_action)){
        return true;
    }
    return $is;
}
function toa_setup_activity_filter () {
    add_filter('bp_is_current_component', 'toa_check_page_reqiurement_and_lie_to_buddypress', 10, 2);
}
function toa_teardown_activity_filter () {
    remove_filter('bp_is_current_component', 'toa_check_page_reqiurement_and_lie_to_buddypress', 10);
}
add_action('bpfb_init', 'toa_setup_activity_filter');
add_action('bpfb_add_cssjs_hooks', 'toa_teardown_activity_filter');

I am able to replicate the issue, You can report here once
https://wordpress.org/support/topic/problem-with-new-buddypress-template/

@dannydlb You can try these patches https://buddypress.trac.wordpress.org/ticket/7845