BuddyPress.org

Is there a table in the DB that deals specifically with notifications?

Yes. That’d be bp_notifications

If so, I guess I could just empty it before I emptied the stream and stream meta tables.

Shout up if anyone thinks that could be a problem.

Instead of deleting directly from the database, you should use these functions:

• bp_notifications_delete_notifications_by_type()
• bp_notifications_delete_notifications_by_item_id()
• bp_notifications_delete_all_notifications_by_type()
• bp_notifications_delete_notifications_from_user()

Alternatively, if none of these quite suit your need, go straight for the class method:

• BP_Notifications_Notification::delete()

Add these additions to your style.css for a fix.

#buddypress div#item-header #item-header-cover-image #item-actions {
    margin-top: 0px !important;
    margin-left: 0px;
    clear: all !important;
    max-width: 80% !important;
}

This may be considered as bug in current behavior. Currently, BuddyPress only looks for published pages when looking for component associated pages in bp_core_get_directory_pages().

You may want to report it on the BuddyPress trac and the core developers and weigh their opinions on this.

I have the exact same problem.

Newest wordpress Newest Buddypress using 2014 theme.

When you click inside the textarea box, the textarea should expand and show the submit button.

Does that work?

If not, it might be related to the Sahira theme. Since Sahira is a premium theme, we do not have access to it. What happens when you switch to one of the WordPress Twenty themes?

Do you have the BuddyPress Activity Privacy plugin activated? If so, read this:
https://buddypress.org/support/topic/buddypress-2-4-0-and-buddypress-activity-privacy/#post-246630

Yes, that sounds right. Getting the user ID is slightly different in BuddyPress depending on the context. See the Playing with the user’s ID in different contexts article for details.

Hi, we’re having exactly the same problem with not being able to upload avatar photos, and we have the repeated path in the error message, e.g.: Upload Failed! Error was: The uploaded file could not be moved to wp-content/uploads/avatars/9/avatars/9.

We are on a fresh (< 1 week old) 1-click WordPress installation, with BuddyPress, bbPress and a few other plugins.

Did you have any joy with resolving this issue please?

Many thanks
Peter

You can use multiple filters with commas: &action=activity_update,new_blog_post

See the comments here for other info:
Using bp_parse_args() to filter BuddyPress template loops

There are a couple of ways to do that.
Try:

function iresource_exclude_ids( $retval ) {
    global $wpdb;

    $field_id = xprofile_get_field_id_from_name( 'FIELD NAME GOES HERE' ); 

    $query = "SELECT user_id FROM " . $wpdb->prefix . "bp_xprofile_data WHERE field_id = " . $field_id . "AND value = 'FIELD VALUE GOES HERE'";

    $exclude_ids = $wpdb->get_col( $query );

    $retval['exclude'] = implode(",", $exclude_ids);
 
    return $retval;
}
add_filter( 'bp_after_has_members_parse_args', 'iresource_exclude_ids' );

More info:

Using bp_parse_args() to filter BuddyPress template loops

Just to add, if you are looking for something to delete, old notifications might be a good place to start. The usual way (in BuddyPress) is to keep all of these, but many places around the web nuke them after they’re ~7 days old.

Am I okay to just clear the db table for bp_activity and bp_activity_meta

I wouldn’t do this because if anyone has notifications which point to the items you delete, then the member will be taken to a broken link.

I’m also guessing stream items DON’T get indexed by Google? I’m not going to create loads of broken results?

There’s nothing in BuddyPress which would stop Google indexing the single activity page. In fact, I bet that page does get indexed, not sure how popular it’d be in the results list though.

Hope this helps?

@shmk profile fields you add in the Base Field Group shows up in the Registration Form https://codex.buddypress.org/administrator-guide/extended-profiles/

Try downloading the following:

• https://translate.wordpress.org/projects/wp-plugins/buddypress/stable/de/default/export-translations
• https://translate.wordpress.org/projects/wp-plugins/buddypress/stable/de/default/export-translations?format=mo

Rename the files to buddypress-de_DE.po and buddypress-de-DE.mo respectively.

Then, move the files to /wp-content/languages/plugins/.

Since the translation is not 100% complete, you might see some English strings.

Let me know if that works for you.

greetings to all,
I put the code suggested @danbp on my bp-custom and everything ok but no mapping trough the extra Xfield type… then I add the suggested plugin ( https://github.com/mottolini/buddypress-xprofile-member-type-field ), but I can’t see any setting page or a guide to edit the file from the plugin for mapping the Xfield.
how can solve it?
Thanks in advance

This bug will be fixed in BP v2.4.1.

If you want to temporarily fix this issue manually, see:
https://buddypress.org/support/topic/profile-field-visibility-enforced-but-members-can-override/#post-246690

I think the German translation is not fully 100% translated, which is preventing WordPress from fetching the latest German translation for BuddyPress.

If you are able to help translate the remaining strings, please visit:
https://translate.wordpress.org/locale/de/default/wp-plugins/buddypress

Also, read the following guide to find out how to contribute towards the translation:

translate.wordpress.org (GlotPress)

@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.

Your question now seems to be about s2member, not BuddyPress.

How are you setting this variable: $s2member_level1 ?

If you want to display the paybox based on s2member level, then use an s2member function to set $s2member_level1 or use a constant.

if( 2 == S2MEMBER_CURRENT_USER_ACCESS_LEVEL ) // etc
https://www.s2member.com/codex/stable/s2member/api_constants/package-globals/#src_doc_S2MEMBER_CURRENT_USER_ACCESS_LEVEL

But where is the text “Vendor registration is currently closed. If you have an existing account, you may login and apply to become a vendor” coming from? I did’t find that anywhere in BuddyPress code when I just ran a search.

See: https://github.com/buddypress/BuddyPress

BuddyPress does not include forums.
You can use bbPress for forums.
bbPress is designed to integrate with BuddyPress.

Be sure to read this page in the Documentation ( aka codex ):

Getting Started

Vendor registration is currently closed. if you have an existing account, you may log in and apply to become a vendor

Are you sure this line of text is associated with BuddyPress? What plugins do you have activated? And also what theme? It could be coming from one of those?