BuddyPress.org

@lagodny

Put this code in functions.php of your (child) theme.

function lagodny_document_title_separator_pipe( $separator ) {
    return '|';
}
add_filter('document_title_separator', 'lagodny_document_title_separator_pipe');

I assume that you are on the WordPress 4.4+.

This helped me A LOT! Solved my error. Got it from:

https://wordpress.org/support/topic/fatal-error-with-buddypress-26?replies=3#post-8563337

Open Quote:

If you’re like me and have buddypress groups turned off, this will produce the error shown. I fixed by adding this to

/wp-content/plugins/buddypress/bp-groups/classes/class-bp-group-extension.php

change:

$group_id = bp_get_current_group_id();

to:

$group_id = (bp_is_active('groups') ? bp_get_current_group_id() : '');

and change:

if ( empty( $group_id ) && bp_get_new_group_id() ) {
    $group_id = bp_get_new_group_id();
}

to:

if(bp_is_active('groups')) {
    if ( empty( $group_id ) && bp_get_new_group_id() ) {
        $group_id = bp_get_new_group_id();
    }
}

IMO, they should have tested this before pushing out an update. Hopefully they figure things out.

Close quote

I posted a topic on the Buddypress Cover Photo support forum, on wordpress.org. (Same authors as KLEO theme and support forum so easier to access). Bye !

Looks like the code example doesn’t work in your theme’s functions.php unless you change the hook from 'bp_groups_register_group_types' to 'bp_init'.

However, the code example from the codex works as-is if used in wp-content/plugins/bp-custom.php.

Going to file a bug report. Thanks for testing, @d8vjork!

Update: Here’s the ticket – https://buddypress.trac.wordpress.org/ticket/7138

Confirming, that @destac solution works ok.
First appeared in a Yoast/wordpress-seo repository open issue.

For the moment, it will continue to work (more or less)

Have you read this on 2.6 About page?
https://buddypress.trac.wordpress.org/changeset/10745

…& as example, check comments in this file:
https://buddypress.trac.wordpress.org/browser/trunk/src/bp-core/bp-core-buddybar.php?rev=10745

I’ve created a bug report for this issue so we can improve it in future

https://buddypress.trac.wordpress.org/ticket/7137

https://buddypress.trac.wordpress.org/changeset/10745

Добрый день @valery-kondakoff,

no it’s not a regression ! Just a question of delay after BP’s update. Translations are made by volonteers, which are humans, not programmed machines. You have to wait that the translation is completed.

Or you can download the trunk version, which is already completed to 100%.
https://translate.wordpress.org/projects/wp-plugins/buddypress/dev/ru/default

At the page bottom you have a download button and a file type selector. Select po and mo format and rename both files to buddypress-ru_RU

https://wordpress.org/plugins/buddypress-announce-group/

Turn off WP_DEBUG in wp-config.php and you should be able to continue using the “Re-order Group Tabs” plugin.

As for BP Group Hierarchy, that probably requires an update to function properly.

BuddyPress 2.5.3 can be found here:
https://downloads.wordpress.org/plugin/buddypress.2.5.3.zip

Try switching your theme to a WordPress default theme.

If that doesn’t work, disable all unnecessary plugins. If that works, then re-enable your plugins one at a time to see which plugin is causing trouble.

Sorry to hear you are experiencing trouble.

You could try adapting the friend count script:
https://buddypress.trac.wordpress.org/browser/tags/2.5.3/src/bp-core/admin/bp-core-admin-tools.php#L168

Or, if you are familiar with wp-cli, you could convert that script into a wp-cli command:
http://wp-cli.org/docs/commands-cookbook/

Then, you could run the script through wp-cli.

@terpz – I think your problem is similar to this thread:
https://buddypress.org/support/topic/registration-and-edit-profile-issue/

Try the recommendation listed here:
https://buddypress.org/support/topic/registration-and-edit-profile-issue/#post-254078

I’ve listed this bug report here:
https://buddypress.trac.wordpress.org/ticket/7109

@djpaul that was to avoid breaking plugins playing with the user meta for regular WordPress install (non multisite).

You can skip it by using:
define( 'BP_SIGNUPS_SKIP_USER_CREATION', true );

Sorry, i can’t help you for this, but i can advice you about this codex page containing some information about lighttpd. Don’t miss to read chapter 8. 😉

BuddyPress share the DB with WordPress (the wp where it is activated).

An association between Polylang and Lingotek could be a good compromise.

If you really want 3 WP, it’s possible for them to use one DB.

Read also the documentation about installing BuddyPress on multisite.

Many topics about this question are already on the forum. You can also read here to get an idea.

Since WP 4.2, you can use get_avatar_url. More on this discussion.

Perhaps this may work too: bp_loggedin_user_avatar( 'html=false' );