BuddyPress.org

But Mathieu for your info, if I put the buddypress-fr_FR.mo file in /wp-content/languages/plugins/ as I did before, it does not work.

Here is what we get

While we should have

I haven’t tried to put the .mo file in /wp-content/languages/plugins/buddypress/

Thanks for your help and reactivity. It now works for me, as I said before, when I simply put the .mo file in /wp-content/languages/
We can close this thread

Hi @capexpe

I believe we’ve improved this part actually in 14.0, see https://buddypress.trac.wordpress.org/changeset/13936.

You shouldn’t put your custom language into /wp-content/languages/plugins because it will be replaced by the official translation after it has been updated by the Polyglots team.

Custom language files for BuddyPress should be in one of the locations we are looking for:
– /wp-content/languages/plugins/buddypress
– /wp-content/languages/buddypress
– /wp-content/languages

More informations are available from this documentation page: https://github.com/buddypress/buddypress/blob/master/docs/user/advanced/texts.md

I’ve just tested renaming “Groupes” with “Expé” in custom fr_FR translation files I’ve included in the /wp-content/languages/plugins/buddypress folder:
– /wp-content/languages/plugins/buddypress/buddypress-fr_FR.po
– /wp-content/languages/plugins/buddypress/buddypress-fr_FR.mo

And it’s behaving the way it should, see screenshot below:

@adjunkten I have no idea how Loco translate deals with translation files, but if you put their generated alternative language files at one of the three locations I listed above making sure they respect the WordPress default way of naming these, it should also fix your issue. Here’s the translated message for the “members-only” login page.

It seems that the /buddypress/v1/members/ endpoint returns only approved and active members displayed on your website. On the other hand, the /buddypress/v1/members/<user_id> endpoint may include all members, regardless of their status, such as pending applications or unapproved members. The extra members you’re seeing could be those who have applied but are not yet approved or are inactive. You may want to add query parameters or filters to refine the results.

Hi there!

Reign BuddyPress Theme I think this theme is helpful for you.
https://wbcomdesigns.com/downloads/reign-buddypress-theme/

Building a site with BuddyPress and the Divi Theme is definitely doable, but there are some compatibility considerations to keep in mind. The Divi Theme Builder is highly versatile, but its compatibility with BuddyPress depends on how BuddyPress structures its pages.

Key Points:

Post Type Compatibility: As the Elegant Themes team mentioned, if BuddyPress uses the default WordPress post type for its pages, you should be able to edit them using the Divi Builder without any issues. BuddyPress typically generates pages using custom post types for specific content like user profiles, activity feeds, etc.

Custom Templates: You might need to create custom templates for BuddyPress pages. Divi allows for a lot of customization, so you can design layouts that suit your needs. However, the integration may require some manual tweaking to ensure everything displays correctly.

Third-Party Plugins: There are third-party plugins that help bridge the gap between BuddyPress and Divi, making it easier to customize BuddyPress pages with the Divi Builder. You might want to explore these if you encounter limitations.

Testing: It would be a good idea to set up a test environment where you can experiment with how BuddyPress and Divi work together, especially when it comes to customizing profile pages and other BuddyPress-specific content.

If anyone in the community has experience with this setup, it would be great to hear your thoughts and any challenges you encountered!

Just started a BuddyPress addon to a Divi site and it looks like a problem. The BuddyPress pages are having issues with header and footer display. All broken.

To assign a custom template to your BuddyPress registration page instead of using the standard blog post template, you can follow these steps:

Install a Page Builder: Consider using a page builder like Elementor along with the BuddyBuilder plugin. This combination allows you to create a custom registration template easily.

Create a New Template: Navigate to Templates > Add New in your WordPress dashboard. Choose “BuddyPress” as the template type and select the “Register page.”

Design Your Template: Add the necessary widgets such as “Account Details,” “Profile Details,” and a “Submit Button.” You can also customize the layout to fit your site’s design better.

Set the Template: Once your template is created, ensure it is set as the default for the registration page in the BuddyPress settings.

Test Your Changes: After saving your changes, visit the registration URL to confirm that the new template is applied correctly.
By following these steps, you should be able to assign a custom template to your BuddyPress registration page successfully. If you have any further questions or need assistance, feel free to ask!
Also, if you’re considering investing in real estate, check out Faisal Town Phase 2 for a prime location with modern amenities.

I seem to remember if you force Buddypress to use wp_mail to send its emails, then those will indeed be logged by the WP Mail Logging plugin.

Try it out.

add_filter( 'bp_email_use_wp_mail', '__return_true' );

I think best practice really depends on your target audience and what features they may expect or desire from their profile.

One of that main profile customisation features provided in BuddyPress is the ability to “overload”, a profile template file, replacing it with your own customised version. This is a simple way to add your own features to the profile pages.

However, overloading a page means any updates to it in future by BuddyPress would need to be manually added to your overloaded page, so this method, although simple, is not the only way to add custom features to profile pages.

If you look in the plugins/buddypress/templates directory, and investigate the templates in, for example bp-nouveau, then you can see there are a lot of action hooks you could use to add further content in specific locations in each page.

This second method allows you to keep the BP provided templates unchanged, but still add the content required.

The most configurable profile I ever created was for a social networking community that wanted the user to effectively create their own theme for their profile pages. So I built the following additional plugins for the site:

1. a theme specific plugin that allowed the user to fully customise their profile colour scheme.
2. A custom header plugin that allowed the user to select their own header image.
3. Similarly, a custom background plugin.
4. My profile home and sidebar user widgets plugins to allow the user to add their own content into their profile pages.
5. Menu customisations to bring all these customisation options into a single location, and remove/simplify them in other places.
6. Integration with the overall blogging platform – providing the user with areas where they can showcase their own blogs, and also allow them a variety of options as to who those blogs are shown to.

Those are just a few main examples as to the possibilities, but most of them do require some form of coding.

For anyone that landed here from a Google search. The pagination is not working for forums set up inside BuddyPress groups. You need to copy those two files from
\plugins\bbpress\templates\default\bbpress
pagination-topics.php
pagination-replies.php

and copy them to
\wp-content\themes\[yourchildtheme]\bbpress

Replace the code inside pagination-topics.php to:

<?php

/**
 * Pagination for pages of topics (when viewing a forum)
 *
 * @package bbPress
 * @subpackage Theme
 */

// Exit if accessed directly
defined( 'ABSPATH' ) || exit;

do_action( 'bbp_template_before_pagination_loop' );

// Use bbPress setting for topics per page
$posts_per_page = bbp_get_topics_per_page();  // Dynamically get the value from bbPress settings

// Get the current page
$paged = (get_query_var('paged')) ? absint(get_query_var('paged')) : 1;

// Set up the custom query
$args = array(
    'post_type'      => bbp_get_topic_post_type(),
    'posts_per_page' => $posts_per_page,
    'paged'          => $paged,
    'meta_query'     => array(
        array(
            'key'   => '_bbp_forum_id',
            'value' => bbp_get_forum_id(),
        ),
    ),
);

// Run the custom query
$forum_query = new WP_Query($args);

if ($forum_query->have_posts()) :
?>
    <div class="bbp-pagination">
        <div class="bbp-pagination-count">
            <?php
            // Display the range of topics being viewed
            $start = ($paged - 1) * $posts_per_page + 1;
            $end = min($paged * $posts_per_page, $forum_query->found_posts);
            echo sprintf(__('Viewing %1$s to %2$s (of %3$s topics)'), $start, $end, $forum_query->found_posts);
            ?>
        </div>
        <div class="bbp-pagination-links">
            <?php
            // Generate the pagination links
            echo paginate_links(array(
                'total'   => $forum_query->max_num_pages,
                'current' => $paged,
                'format'  => '?paged=%#%',
                'add_args' => false,
                'prev_text' => __('« Prev'),
                'next_text' => __('Next »'),
            ));
            ?>
        </div>
    </div>
<?php
else :
    echo '<p>No topics found.</p>';
endif;

// Reset post data
wp_reset_postdata();

do_action('bbp_template_after_pagination_loop');
?>

Replace the code inside pagination-replies.php to:

<?php

/**
 * Pagination for pages of replies (when viewing a topic)
 *
 * @package bbPress
 * @subpackage Theme
 */

// Exit if accessed directly
defined( 'ABSPATH' ) || exit;

do_action( 'bbp_template_before_pagination_loop' );

// Use bbPress setting for replies per page
$posts_per_page = bbp_get_replies_per_page();  // Dynamically get the value from bbPress settings

// Get the current page
$paged = (get_query_var('paged')) ? absint(get_query_var('paged')) : 1;

// Set up the custom query
$args = array(
    'post_type'      => bbp_get_reply_post_type(),
    'posts_per_page' => $posts_per_page,
    'paged'          => $paged,
    'meta_query'     => array(
        array(
            'key'   => '_bbp_topic_id',
            'value' => bbp_get_topic_id(),
        ),
    ),
);

// Run the custom query
$replies_query = new WP_Query($args);

if ($replies_query->have_posts()) :
?>
    <div class="bbp-pagination">
        <div class="bbp-pagination-count">
            <?php
            // Display the range of replies being viewed
            $start = ($paged - 1) * $posts_per_page + 1;
            $end = min($paged * $posts_per_page, $replies_query->found_posts);
            echo sprintf(__('Viewing %1$s to %2$s (of %3$s replies)'), $start, $end, $replies_query->found_posts);
            ?>
        </div>
        <div class="bbp-pagination-links">
            <?php
            // Generate the pagination links
            echo paginate_links(array(
                'total'   => $replies_query->max_num_pages,
                'current' => $paged,
                'format'  => '?paged=%#%',
                'add_args' => false,
                'prev_text' => __('« Prev'),
                'next_text' => __('Next »'),
            ));
            ?>
        </div>
    </div>
<?php
else :
    echo '<p>No replies found.</p>';
endif;

// Reset post data
wp_reset_postdata();

do_action('bbp_template_after_pagination_loop');
?>

Then, resave your permalinks.

Hello Lars

No I haven’t found any workaround yet and haven’t heard from the buddypress team yet. They might be in vacation, so I’m Still waiting.

I’ll keep you and the community posted.

Dom

Hi

1) For my BP community, it would be nice if ‘Buddypress Follow’ was part of core and replaced the ‘friends’ functionality. It should be either/or – both together is confusing for users, IMO.

2) Thanks @venutius, for updating the plugin. I tried it on my staging site. When I clicked ‘follow’, there was a critical error, but refreshing the site fixed it, so that it showed 1 follow on user’s profile.

@mike80222, when composing a message, the “@” applies to the BuddyPress Nouveau template pack, i.e, the label reads “Send @Username” as opposed to the BuddyPress Legacy template pack that reads “Send To (Username or Friend’s Name)” and I’m not sure why it is not the same for both but, that is current behavior. As to the inconsistency for when suggestions appear or not appear is a puzzle, at the moment.

@stephunique, it is possible to filter the suggested usernames by utilizing the bp_core_get_suggestions filter. If you only want to apply this filtering to messages (compose) then your callback needs to be location aware (what/which page/screen is active/loaded), as well.

The create_function() was deprecated as of PHP 7.2.0 and was removed in 8.0.0 (see create_function). Since you are using PHP 8.x then, it would be best to not use this plugin until it has had all compatibility issues resolved. On another note, there seems to be some interest by individuals other than the original developers to provide some sort of future support for this plugin (see Would like to take over this plugin, or help – Support forum for BuddyPress Follow).

The information you provided suggests a caching issue with your CDN setup for the member page activities. Here are some technical suggestions to investigate and potentially fix the problem:

1. Caching Configuration on CDN:

Check your CDN provider’s (CloudFront in this case) caching settings. You likely need to configure it to not cache dynamic content like member activities. Look for options related to “Cache Control” or “Object Caching”. You might need to set a short cache expiry time or disable caching for specific paths (e.g., /members/*).
2. Caching Headers:

Ensure your server sends appropriate caching headers with the member activity data. The server should send headers like Cache-Control: no-cache, no-store, must-revalidate to prevent browsers and the CDN from caching this data.
3. Browser Caching:

Although less likely, there’s a chance the browser is caching the initial response. Try clearing the browser cache and cookies after the first load to see if the issue persists.
4. Anti-Proxy Buddypress Plugin:

While Youzify mentioned the anti-proxy Buddypress plugin, it’s difficult to say definitively if it’s causing the issue without more information. It’s possible the plugin is interfering with the caching mechanism. You can try temporarily disabling the plugin to see if the problem resolves. Be cautious as disabling plugins can have unintended consequences.
5. Debugging Tools:

Use browser developer tools (Network tab) to inspect the network requests when loading activities. Look for any caching headers being sent and received. Additionally, check the status code of the requests – a 304 (Not Modified) might indicate the CDN is serving cached data.