BuddyPress.org

@garprogram – This fatal error is due to some changes we made in BP v2.4.0 to give users proper feedback messages when a private message fails to send.

It looks like we might have to add some additional hooks so plugin devs can set the error message.

In the meantime, here are two things I would recommend:

1. Use the 'bp_messages_recipients' filter instead of using the 'messages_message_before_save' action:
https://buddypress.trac.wordpress.org/browser/tags/2.4.0/src/bp-messages/bp-messages-actions.php?marks=77-84#L77

2. As Henry mentioned, if you have to unset one recipient, you should unset all of the recipients to avoid the message from sending. The default error message will probably not suit your needs, so you might have to filter the error message with the 'gettext' filter temporarily until we introduce better error handling for plugin developers.

How do I remove buddyPress completely from my wordpress and restore everything as pre-installation of BuddyPress?

You can just deactivate the plugin and remove the “Register” and “Activate” pages you created at Dashboard > Pages.

You can ignore this message if you’re using BuddyPress on a production site.

To turn off debugging notices on production, set WP_DEBUG to false in wp-config.php:
https://codex.wordpress.org/WP_DEBUG

This is a notice caused by a plugin that is initializing user info too early. If you want to find out which plugin is causing this, deactivate all your plugins and only activate BuddyPress. Next, activate your plugins one-by-one until you find the culprit.

One tip is to check if is because YouYupe are using different URL’s these days, I had an issue which I’ve still got where the old URL works fine but the new one does not, wordpress wraps the content in a link instead of previewing it.

I have no idea if this plugin still functions because it was last updated ~4 years ago, but check out BuddyPress Block Activity Stream Types.

I’ve got a fix ready:
https://buddypress.trac.wordpress.org/attachment/ticket/6745/6745.01.patch

Apply the lines in that patch to your BuddyPress install.

To test this, you’ll need to set WP_DEBUG to true so it will load the unminified version of the javascript:
https://codex.wordpress.org/WP_DEBUG

Let me know if this fixes the problem.

We do not store avatar data in the database.

We do a look up at the files level instead.

If you want to show an avatar based on a custom avatar stored in the database, you’ll need to use the 'bp_core_fetch_avatar' filter to override how BuddyPress shows avatars:
https://buddypress.trac.wordpress.org/browser/tags/2.4.0/src/bp-core/bp-core-avatars.php?marks=531-546,660-664#L531

If you just want to display a user avatar, use the bp_core_fetch_avatar() function:

echo bp_core_fetch_avatar( array(
    'item_id' => USER_ID_TO_GRAB_AVATAR_FOR
) );

@doublef

Here is the latest error log:

PHP message: WordPress database error Table ‘mysitename.wp_16_bp_xprofile_groups’ doesn’t exist for query SELECT DISTINCT g.id FROM wp_16_bp_xprofile_groups g WHERE g.id = 0 ORDER BY g.group_order ASC made by require(‘wp-blog-header.php’), require_once(‘wp-load.php’), require_once(‘wp-config.php’), require_once(‘wp-settings.php’), do_action(‘init’), call_user_func_array, bp_init, do_action(‘bp_init’), call_user_func_array, woffice_social_fields, xprofile_insert_field_group, BP_XProfile_Group->__construct, BP_XProfile_Group->populate, BP_XProfile_Group::get
PHP message: WordPress database error Table ‘mysitename.wp_16_bp_xprofile_groups’ doesn’t exist for query INSERT INTO wp_16_bp_xprofile_groups (name, description, can_delete) VALUES (‘Social’, ”, 1) made by require(‘wp-blog-header.php’), require_once(‘wp-load.php’), require_once(‘wp-config.php’), require_once(‘wp-settings.php’), do_action(‘init’), call_user_func_array, bp_init, do_action(‘bp_init’), call_user_func_array, woffice_social_fields, xprofile_insert_field_group, BP_XProfile_Group->save
PHP message: WordPress database error Table ‘mysitename.wp_16_bp_xprofile_groups’ doesn’t exist for query SELECT * FROM wp_16_bp_xprofile_groups WHERE name = ‘CoverOptions’; made by require(‘wp-blog-header.php’), require_once(‘wp-load.php’), require_once(‘wp-config.php’), require_once(‘wp-settings.php’), do_action(‘init’), call_user_func_array, bp_init, do_action(‘bp_init’), call_user_func_array, woffice_cover_add_field
PHP message: WordPress database error Table ‘mysitename

Tricky task… I don’t envy your use case testing!

BP uses the WP user – but stores profile data separately. But some fields are duplicated – like name.

You may have to write profile data to both user meta and xprofile tables.
And then use a conditional re whether the BP Extended Profiles component is enabled.
If it isn’t, then pull from user meta, etc.

More info:

xprofile_sync_wp_profile() syncs Xprofile data (nickname, first name and last name) to the standard built in WordPress profile data.

xprofile_sync_bp_profile() syncs the standard built in WordPress profile data to XProfile.

Hey @alessandrat

Welcome to the BuddyPress forum!

1. Have two separate front ends for different user types (with differently configured profiles), appearances, and accesses.

Yes. This can be done with either a plugin (try searching the Plugin Directory) or coded through the Member Types feature introduced in version 2.2.

2. Have a place where shortcode could be put in so that users can take a questionnaire containing likert questions on their profile and/or while creating their profile.

Either a post, page or perhaps even an activity update all spring to mind as possible places to add it.

3. One but not both kinds of users can create their own group (public, semiprivate or private) or forum and browse/ join existing ones

The ability for all members to create new groups comes as standard.

4. One kind of user but not the other needs to be able to set up ways for the other type of user to purchase products (I assume I can use another plugin but will need a place to put the shortcode)

This will need to be either custom coded, or you may find a plugin with the functionality you need.

Hope this info helps!

I don’t know why your function isn’t working, but since you only want subscribers, there are more efficient ways to approach the task.

Here is one:
Review this: https://codex.wordpress.org/Function_Reference/get_users

Try something like:

function subscribers_only() {
   $subscribers = get_users( array( 'role' => 'subscriber', 'fields' => array( 'ID' ) ) );
   $subscribers = implode(",",$subscribers);
   return $subscribers;
}

And

$subscribers = subscribers_only();
bp_has_members( bp_ajax_querystring( 'members' ) . '&include=' . $subscribers )

– Make sure email is working from WordPress.
– Tell users to check their spam folder.

If that doesn’t work, some have had success with the following plugin(s):
– Mail From: https://wordpress.org/plugins/search.php?type=term&q=mail+from
– A plugin that sends email via SMTP instead of PHP: https://wordpress.org/plugins/tags/smtp

See also https://wordpress.org/plugins/mass-messaging-in-buddypress/

Thanks @joost-abrhahams.

I’ve filed a ticket here:
https://buddypress.trac.wordpress.org/ticket/6738

We’ll get this fixed for v2.4.1.

Hi, I use Simple WordPress Membership Plugin. It works.

Great work!

I´m REALY new in WordPress/Buddypress.
Now i have a question:

How can i do it in another language now (Buddypress), in this case german needed?

greetings

Aphelion

We have deprecated support for the bp-default theme since v1.9:
The future of the bp-default theme

That being said, we can look into supporting this feature in bp-default for BP v2.5.0.

You might have to do a fresh install because BuddyPress 2.4.0 uses new code for the /groups/single/home.php template:
https://buddypress.trac.wordpress.org/browser/tags/2.4.0/src/bp-templates/bp-legacy/buddypress/groups/single/home.php#L75

The code you listed above is older code.

If you already have those changes, then I’m guessing you are using a custom theme with BuddyPress support that has overriden the groups/single/home.php template. If that is the case, you’ll have to change the group home template to use these new lines.

Since you modified the home.php template, you have to make some adjustments so the new changes will work.

Read the bpdevel post on this:
Get Ready! 2.4.0 will introduce important changes in Groups homes

Especially the last section – Changes in 2 templates.

Please use the code button when sharing code.
For long pieces of code, please use a service like gist.

You can submit an enhancement ticket here. Please search the existing tickets first for entries that already make the same request.