BuddyPress.org

@thesun2012 bp_legacy_theme_ajax_messages_star_handler is not mandatory; you can also create your custom handler based on it
for example

function wbcom_custom_buddypress_ajax_handler() {
    check_ajax_referer('custom-bp-ajax-nonce', 'security');

    $displayed_user_id = isset($_POST['displayed_user_id']) && !empty($_POST['displayed_user_id']) 
                         ? (int) sanitize_text_field($_POST['displayed_user_id']) 
                         : get_current_user_id();

    $message_id = isset($_POST['message_id']) ? (int) sanitize_text_field($_POST['message_id']) : 0;
    $star_status = isset($_POST['star_status']) ? sanitize_text_field($_POST['star_status']) : '';
    $bulk = isset($_POST['bulk']) && !empty($_POST['bulk']);

    if (!bp_is_active('messages', 'star') || empty($message_id) || !is_user_logged_in() || !bp_core_can_edit_settings()) {
        wp_send_json_error(array('message' => 'Invalid request or insufficient permissions.'));
        return;
    }

    $result = bp_messages_star_set_action(array(
        'action' => $star_status,
        'message_id' => $message_id,
        'bulk' => $bulk,
        'user_id' => $displayed_user_id
    ));

    if ($result) {
        wp_send_json_success();
    } else {
        wp_send_json_error(array('message' => 'Failed to update message status.'));
    }
}

add_action('wp_ajax_wbcom_custom_buddypress_action', 'wbcom_custom_buddypress_ajax_handler');

AJAX Request Adjustments like this

jQuery.ajax({
    url: ajaxurl,
    type: 'POST',
    data: {
        'action': 'wbcom_custom_buddypress_action',
        'displayed_user_id': displayedUserId, // Include if available
        'message_id': messageId,
        'star_status': starStatus,
        // Additional data...
    },
    success: function(response) {
        // Handle success
    },
    error: function(error) {
        // Handle error
    }
});

We can suggest modifying the bp_legacy_theme_ajax_messages_star_handler() function to handle the displayed user ID and use the logged-in user ID as a fallback.

function bp_legacy_theme_ajax_messages_star_handler() {
    if ( false === bp_is_active( 'messages', 'star' ) || empty( $_POST['message_id'] ) ) {
        return;
    }

    // Check nonce.
    check_ajax_referer( 'bp-messages-star-' . (int) $_POST['message_id'], 'nonce' );

    // Check capability.
    if ( ! is_user_logged_in() || ! bp_core_can_edit_settings() ) {
        return;
    }

    // Get the displayed user ID or fallback to the logged-in user ID.
    $user_id = isset($_POST['displayed_user_id']) && !empty($_POST['displayed_user_id']) 
               ? (int) $_POST['displayed_user_id'] 
               : get_current_user_id();

    if ( true === bp_messages_star_set_action( array(
        'action'     => $_POST['star_status'],
        'message_id' => (int) $_POST['message_id'],
        'bulk'       => ! empty( $_POST['bulk'] ) ? true : false,
        'user_id'    => $user_id  // Use the determined user ID
     ) ) ) {
        echo '1';
        die();
    }

    echo '-1';
    die();
}

Hi @imath,

I have a similar / related issue. I’m using Restrict Content Pro’s registration page with the latest Buddypress version (12.1.1) on a staging site and my registration page broke. It told me “Member registration is currently not allowed”, even if I disable the buddypress plugin.

I tried the gist you posted https://gist.github.com/imath/c5c34feb5d3c9b3070f7a11bc339f103 in my child theme’s functions.php but the registration page still does not work. Any ideas?

*Update* – I read through the earlier post and found the first workaround – going to Buddypress Settings -> URLs, but did not see any option to change the register slug. I had to briefly turn on wordpress general settings “Anyone can register” so that more options would appear in “URLs”. I was able to set the slug to something else like ‘sign-in’ and that seemed to allow my RCP registration to function again.

Just to check, I disabled “Anyone can register”. Seems like the BP slug change stuck and my RCP registration is operational.

Please follow following thread https://buddypress.org/support/topic/buddypress-12-1-1-maintenance-security-release/#post-332831

@puresaian To mention all group members simultaneously, you must implement a custom solution. This could be a special shortcode or command that automatically translates into individual mentions for all group members when used by the admin.

/**
 * Handles the custom mention "@everyone" within BuddyPress groups.
 * When @everyone is used in a group's post or comment, it replaces it with mentions of all group members.
 */
function wbcom_custom_everyone_mention_handler( $content ) {
    // Check if BuddyPress is loaded and @everyone is used in the content
    if ( function_exists( 'groups_get_current_group' ) && strpos( $content, '@everyone' ) !== false ) {
        // Get the current group details
        $group = groups_get_current_group();

        // Proceed only if we are in a group context
        if ( $group ) {
            // Fetch all members of the group
            $group_members = groups_get_group_members( array( 'group_id' => $group->id ) );
            $mentions = array();

            // Loop through each member to build the mentions array
            foreach ( $group_members['members'] as $member ) {
                $mentions[] = '@' . $member->user_nicename; // Prepares the mention syntax for each member
            }

            // Replace @everyone in the content with the individual member mentions
            $content = str_replace('@everyone', implode(' ', $mentions), $content);
        }
    }

    // Return the modified (or unmodified, if no changes were made) content
    return $content;
}

// Add filters to apply the custom mention handler in different BuddyPress content types
add_filter( 'the_content', 'wbcom_custom_everyone_mention_handler' ); // For regular WordPress content
add_filter( 'bp_activity_new_update_content', 'wbcom_custom_everyone_mention_handler' ); // For new BuddyPress activity updates
add_filter( 'bp_activity_comment_content', 'wbcom_custom_everyone_mention_handler' ); // For comments on BuddyPress activities

It’s not a tested code; it’s just giving implementation directions.

@investbuddy123 Based on your description of issues with BuddyPress on your WordPress site, you’re encountering problems with group updates and public messaging functionalities.

Here is a step-by-step guide to debug the issue:

Check for Plugin Conflicts: Deactivate all plugins except BuddyPress and BP Classic. If the issue is resolved, reactivate each plugin individually to identify the conflicting plugin.

Theme Compatibility: You’ve tried switching to the Twenty-Three theme with no success, which is good. It rules out theme-specific issues.

Inspect JavaScript Errors: Use the browser’s Developer Tools (usually accessible by pressing F12) to check for JavaScript errors in the Console tab. JavaScript issues often cause features like loading updates or activating functions to fail.

Server and PHP Error Logs: Check your server and PHP error logs for any relevant errors. Your hosting provider can assist you in accessing these if you’re unsure how.

Test on a Staging Site: If possible, clone your site to a staging environment. This allows you to test without affecting your live site.

Cache and Optimization Plugins: If you use caching or optimization plugins, clear the cache and temporarily disable them to see if they are causing the issue.

Check for Custom Code: If you have any custom code (like snippets in your theme’s functions.php file or a custom plugin), comment to see if it is causing the issue.

Thank you for creating this topic

I think, if possible, that the system of historiography
Change BuddyPress to the default WordPress system, it’s better
(Things like choosing the date of birth and…)

So that users who use other history systems can also benefit from it

Hi,

You should be able to find a remedy at the following post:

https://buddypress.org/support/topic/buddypress-12-1-1-maintenance-security-release/#post-332831

Hi @portalciencia

Some plugins might not be ready with BuddyPress 12.0 or up. For this case we’ve built a Backwards compatibility Add-on. You can try to download and activate it to see it it’s fixing your issue:

BP Classic

hello @imath

i appreciate your team work.

you have list of plugins which handle by your company or compatible with buddypress. it helps me a lot.

thank you