BuddyPress.org

I wish you had longer to edit posts here. My apologies for triple posting here, but I want to mention that what I put above actually may not stop the error logging. I thought it was working, but it is not. 🙂 Not with my hosting anyway. I’m sure the BuddyPress gods will fix this soon. May the force be with you all.

If you’re like me and you do not want these PHP warnings added to your error log every second, you could temporarily do the following until the BuddyPress developers fix this. I stress temporarily because knowing about PHP errors and warnings is a good thing. Add this to your wp-config.php file:

ini_set('error_reporting', 0 );

Again, don’t forget to remove this once you know this is fixed so you can catch the next warning/error your site has.

I know this is slightly pointless… why not just let the warnings log for now… but it’s more of a mental appeasement. 🙂

Or, to really ensure no warnings/errors show in logs or on your live site (once again only until this is fixed), remove the existing define('WP_DEBUG', false); line in wp-config.php, and replace it with all of the following:

ini_set('display_errors','Off');
ini_set('error_reporting', 0 );
define('WP_DEBUG', false);
define('WP_DEBUG_DISPLAY', false);

Same for me. A honking great string of errors that are showing at the top of the page to visitors on the front end.

It’s still there, even when I disable BP (I don’t want to delete it and lose my settings). I’ve had to take my site offline for the past 24 hrs.

Is BuddyPress releasing an update to fix this soon? Every other major app has since the latest version of WordPress.

Please help guys!

Yes it will! I have a WordPress install on a subdomain and BuddyPress works absolutely fine.

`Warning: Declaration of BP_Walker_Nav_Menu::walk($elements, $max_depth) should be compatible with Walker::walk($elements, $max_depth, …$args) in /home/xxxx/public_html/wp-content/plugins/buddypress/bp-core/classes/class-bp-walker-nav-menu.php on line 0

I am having the same problem after updating wordpress 5.3.

Regards.

Yes, the easiest way is to activate the BP Legacy Template Pack from the BuddyPress Options screen into your WordPress Dashboard.

Using the WordPress control for generating passwords is a BP Nouveau only feature. The benefits of it is to have the same control than WordPress (eg: when your member are resetting their passwords from the site.url/wp-login.php page).

> Buddypress: version 5.0 was added to the theme as a plugin

What does it mean?

BuddyPress is not installed from the Plugins Management screen?

Please make sure to follow all suggested checks into this topic, in particular testing with only BuddyPress activated and a Twenty* WordPress bundled theme.

They can choose the password of their choice and use the checkbox to confirm the use of weak password if needed.

Having a password to log in is required. Having a strong password is important for the safety of your site.

Disabling this feature would be too bad imho. But you can always override the /members/register.php from a /buddypress/members/register.php template in your active theme (or better child theme).

Thanks for the screenshot of the error.
Just before the word ‘Intervention’, there is an arrow. Click it and you should see the whole error message. Copy and paste it in a reply here.

You may need to open a ticket.
use the same login you use here. And include all the info you posted here.

Hi buddy, have you found a solution? I’m stuck with a similar issue.
I have been using a plugin to export buddypress members and xprofile fields and it is no longer working since 7 november. i cant find another plugin to export the members data.. anyone can help?

Edit timed out on me up there and didn’t get to revise my reply in time!

/buddypress/activity/post.form.php, overload it child theme

/*
 * Template tag to prepare the activity post form checks capability and enqueue needed scripts.
 */

if( bp_is_group() && !current_user_can('administrator') ) {

} else {

bp_nouveau_before_activity_post_form();
?>

<h2 class="bp-screen-reader-text"><?php echo esc_html_x( 'Post Update', 'heading', 'buddypress' ); ?></h2>

<div id="bp-nouveau-activity-form" class="activity-update-form"></div>

<?php
/*
 * Template tag to load the Javascript templates of the Post form UI.
 */
bp_nouveau_after_activity_post_form();

}

@meisinotti you can restrict the post form to admins depending on what template pack you use… you could set something like,

with nouveau, /buddypress/activity/post.form.php, overload it child theme

/*
 * Template tag to prepare the activity post form checks capability and enqueue needed scripts.
 */

if(bp_is_group_activity() && current_user_can('administrator')) {

bp_nouveau_before_activity_post_form();
?>

<h2 class="bp-screen-reader-text"><?php echo esc_html_x( 'Post Update', 'heading', 'buddypress' ); ?></h2>

<div id="bp-nouveau-activity-form" class="activity-update-form"></div>

<?php
/*
 * Template tag to load the Javascript templates of the Post form UI.
 */
bp_nouveau_after_activity_post_form();
}

assuming you don’t allow users to create their own groups, if you want to allow them to post updates on their own created groups then you’d need to check for that.

All 3 of these options (BP Simple Private, Buddypress Lock, or the custom code) all cause significant page speed issues. (like 3 seconds)

Any suggestions to combat the privacy issue without compromising speed?