BuddyPress.org

Keep an eye on https://buddypress.trac.wordpress.org/ticket/7845#ticket !

Thanks for the details. Keep an eye on https://buddypress.trac.wordpress.org/ticket/7845#ticket

We don’t have enough information to figure out what the cause might be yet, I think we will need to try to reproduce the problem, but it doesn’t seem to be unique to your site, so I’ve created a bug report at https://buddypress.trac.wordpress.org/ticket/7844 — please keep an eye on that for updates.

We don’t have enough information to figure out what the cause might be yet, I think we will need to try to reproduce the problem, but it doesn’t seem to be unique to your site, so I’ve created a bug report at https://buddypress.trac.wordpress.org/ticket/7844 — please keep an eye on that for updates.

Are you using WordPress with multisite enabled, or not?

This might be related to https://buddypress.trac.wordpress.org/ticket/7837

Were you using the new Nouveau template pack when you had this problem?

Hi

I assume you’re using the new Nouveau template pack? Have you tried looking in the WordPress Customizer for the options?

This would have been better posted on the wordpress.org forum for that specific plugin next time, please.

Bug: https://buddypress.trac.wordpress.org/ticket/7843

Keep an eye on that. Sorry for the inconvenience.

Bug: https://buddypress.trac.wordpress.org/ticket/7843

Keep an eye on that, and sorry for the inconvenience in the meanwhile.

@mrlen Legacy Forums support is removed with BuddyPress v3.0.0 and theme also need to update accordingly. Please check with your theme support
For details, you can check https://bpdevel.wordpress.com/2017/12/07/legacy-forums-support-will-be/

@kelvinnm no need to alter codes inside the plugin you can simply use https://wordpress.org/plugins/wp-mailfrom-ii/ it will give your option to set name and from

@bjoerndz rtMedia working fine with BP 3.0.0 with the legacy template.
For Nouveau, they have to work on the template file, you can check with their support for template styling related to Nouveau.
https://drive.google.com/a/wbcomdesigns.com/file/d/11vfmqRo0QO9J6-euUnvmAQOm4dHFCruc/view?usp=drivesdk with default WordPress theme.

@andreia22
bp_is_user_forums() no longer used in core, but supported for third-party code.
legacy forum support removed in BP v3.0 you can find the details here https://bpdevel.wordpress.com/2017/12/07/legacy-forums-support-will-be/

You can check with your theme support to update the corresponding codes inside the theme.

You can keep using legacy template pack for while and after your theme vendor announces support for nouveau you can switch on it.

I can’t duplicate gcmaryland’s problems with group meta.

For those with problems, can you post what group plugins you are using and what the expected behavior is? Please list clear steps to duplicate. Imagine a person that does not know anything about BuddyPress and WordPress and expect that person to duplicate the problem.

Update – duplicated the problem with the bp-nouveau template pack. I have some tentative fixes that I’ve added to the ticket.

However, here’s the easiest fix you can add to your site for now:
https://buddypress.trac.wordpress.org/attachment/ticket/7837/7837.01.patch

@kelvinnm

add_filter( 'wp_mail_from',      $admin_email_filter );
add_filter( 'wp_mail_from_name', $from_name_filter );

is defined inside https://github.com/boonebgorges/buddypress-group-email-subscription/blob/master/bp-activity-subscription-digest.php
which you can override via functions or try
try https://wordpress.org/plugins/wp-mailfrom-ii/

Posted to: https://buddypress.trac.wordpress.org/ticket/7837#ticket with code sample

(First issue, so please let me know if this is right – thanks!)

@ma3ry there is a temp fix for BuddyPress Xprofile Custom Fields Type by @venutius you can check it.
https://wordpress.org/support/topic/warning-breaks-with-bp-3-0/

Issue confirmed for some of our sites as well. Rolling back BP to 2.9.4 fixes issues in both the previous and current versions of WP. It appears to be linked to sites currently using custom group meta through an active or inactive plug-ins. I’ve noticed that removing the line: add_filter( ‘groups_custom_group_fields_editable’, ‘group_header_fields_markup’ ); from active plug-ins using the group meta template (https://codex.buddypress.org/plugindev/how-to-edit-group-meta-tutorial/) breaks the plug-in and allows the group pages to be loaded correctly. I’ve noticed that all of these functions have the $wpdb object referenced in (https://buddypress.trac.wordpress.org/ticket/7834). Perhaps there’s a connection? Otherwise, it still appears to be limited to sites using custom group meta plug-ins.

hmm, with the recent changes in WP it’s not that straightforward. You’d need to download the files from the BP SVN here https://plugins.svn.wordpress.org/buddypress/tags/2.9.4/ and for that you would need an SVN browser such as tortoise SVN. One you had the files you would also need FTP access to your site, to rename the current BP directory in plugins to something else (buddypress-3.0 for example) and then copy the 2.9.4 files into a new buddypress directory. then you could test it.

Hello,

Starting from BuddyPress 3.0 we have removed support for the deprecated and unsupported bbPress 1.x that was bundled with BuddyPress.

As written in our release post:

Most notably, the Legacy Forums component has been removed after 9 years of service. If your site was using Legacy Forums, you need to migrate to the bbPress plugin.

And here is our general bbPress 2.x forum installation guide:

Installing Group and Sitewide Forums

So, @m1000, please follow the migration guide and move everything forum-related to bbPress 2.x, which is faster and overall works better.

You should raise this on BuddyPrss Trac as a bug.

@dggerhart you can try https://wordpress.org/plugins/ban-hammer/ it will allow you to block list domain TTL.