BuddyPress.org

Certainly! If you’re looking to optimize member profiles on a BuddyPress-powered website for search engines (SEO), you might want to consider the following response:

Hello there,

Optimizing member profiles on BuddyPress for SEO is a crucial step to enhance visibility on search engines. Here are some tips to ensure your member profiles are search engine friendly:

Complete and Relevant Profile Information:
Encourage members to fill out their profiles thoroughly. Include key information, such as a brief bio, interests, and any relevant links. Search engines often prioritize pages with comprehensive content.

SEO-Friendly Usernames and Display Names:
Suggest to members that they choose usernames and display names that are relevant to their identity or interests. This can contribute to better search engine visibility.

Enable SEO-friendly Permalinks:
Check your BuddyPress settings and ensure that your permalinks are set up in a way that includes relevant keywords. This helps search engines understand the content of the profile pages.

Utilize BuddyPress Custom Fields:
BuddyPress allows you to add custom fields to member profiles. Use these fields to gather additional information that might be relevant for search engine optimization. This could include skills, locations, or any other pertinent details.

Encourage User-Generated Content:
User-generated content, such as forum posts or activity updates, can contribute to the overall SEO of the website. Encourage members to engage with the community and share valuable content.

Implement OpenGraph and Twitter Card Tags:
Add OpenGraph and Twitter Card meta tags to member profile pages. This enhances how the profile appears when shared on social media platforms, indirectly impacting SEO.

Mobile Optimization:
Ensure that member profiles are optimized for mobile devices. Google considers mobile-friendliness as a ranking factor, and a responsive design is crucial for SEO.

Regularly Update BuddyPress:
Keep your BuddyPress installation up-to-date. Updates often include improvements and bug fixes that can indirectly impact SEO.

Remember, SEO is an ongoing process, and monitoring analytics can provide insights into what is working and what can be improved.

So you’re using BP version 12.0 on a regular site (not a multisite config), you activated, then deactivated BP Classic because it was no more needed. And now when you go into the URLs tab of the BuddyPress settings and tries to customize slugs, it adds a -2 suffix.

Is it happening when these slugs are default BuddyPress ones only (eg: activity, members) or is it happening even with these slugs: ‘activites’, ‘membres’ for example?

If it’s only happening with BuddyPress default slugs: check there are no regular WordPress pages using the BP slugs.

Then try to use the Reset Slugs BuddyPress tools from the WP Admin tools menu.

If it didn’t fixed the issue, try to temporarily add this code to the functions.php of your active theme:
remove_filter( 'wp_unique_post_slug', 'bp_core_set_unique_directory_page_slug', 10, 6 );

Go to the URLs tab of the BuddyPress settings and try to customize slugs again.

Then remove the custom code you added to the functions.php of your active theme.

Hi @shemakeswebsites,

12.0.0 brings URL slugs customization, that’s a big improvement to have meaningful URLs for non English communities.

These communities are using different words for things like Activity, groups etc.. They can do so thanks to the l10n feature of WordPress. So a good way to reach your goal is to use a custom translation file. And I believe it’s the best way to do so, because the page title or labels won’t be enough to really reword all places where we use groups.

You can try to put your custom translation file into wp-content/languages/buddypress/buddypress-xx_XX.mo replacing the xx_XX with your locale maybe it’s even working with en_US.

Mathieu, thanks for the comments , I can see there are many effected by the upgrade, I hope its not overwhelming for you. I don’t write php, but of course can copy and paste. I am not missing any buttons, the buttons just don’t work , they still show, they are edit , delete, created I think with forminator. Since there is a functions.php page in my child theme I tried pasting the add_filter code you posted, with BP 12 it didn’t help. I pasted it in the top section “function my theme area, I posted the functions php code in a gist here

I am looking to see how to share a screenshot of the offending page ,.
Hey also I noticed in the buddypress settings page there is a tab marked “Pages” that is new, I have no idea if I am supposed to set those drop downs to pages, but after touching it now I see a message in red “The following active BuddyPress Components do not have associated BuddyPress Pages: Members, Activity, Groups, Activate, Register.” The guy that wrote these custom code child theme pages died about two years ago, I’ve been maintaining this website and really hope I can keep this working , updates can whack it out , but usually it still functions after the update , not this time

I had the option Allow activity stream commenting on posts and comments disabled I also have some code in custom.php file. I am not sure if it could have any effect

/* Disable comment for all activity but still enable @mention autosuggestion. */
function disable_activity_comments($can_comment, $activity) {
    // Disable comments
    $can_comment = false;
    return $can_comment;
}
add_filter('bp_activity_can_comment', 'disable_activity_comments', 10, 2);

/* Hide comment from activity page */ 
add_action( 'bp_after_has_activities_parse_args', function ( $r ) {
    if ( bp_is_activity_directory() || bp_is_single_activity() ) {
        $r['display_comments'] = false;
    }
    return $r;
} );

// Exclude activity updates from subscribers who are not logged in on the activity directory page.
function hide_new_member_activities_from_unlogged_users( $args ) {
    if ( ! is_user_logged_in() ) {
        $args['action'] = array(
            'activity_comment',
            'activity_update',
            'last_activity',
            'new_avatar',
            'new_blog_comment',
            'new_blog_post',
			'new_classified',
            'updated_profile'
        );
    }
    return $args;
}
add_filter( 'bp_after_has_activities_parse_args', 'hide_new_member_activities_from_unlogged_users' );

@imath,
Thank you for your response and apologies for my tardiness – I had no idea that the Discussion settings had any impact on Buddypress Activity but you are correct, this was what was causing the issue. Is this documented anywhere in the Buddypress docs/codex? I made the mistake of assuming that Buddypress activity was a separate entity to the blog posts and comments but obviously it isn’t, so do all the other Discussion settings impact it as well? I can obviously test myself but if there is any resource on this that would be very useful.

Regarding the BP Classic issue, thank you, although I have now made a significant design change and workaround so I don’t think it will impact me any more, and that also applies to the issue I reported with the nav menu highlighting, although that will impact others. Basically I have created a custom Members directory page on a WP page so that when that is a sub menu item of Activity any visit to a Profile page does not highlight the Activity menu item as was happening with the standard Member directory. Also from my testing I have not encountered any issues that will require BP Classic to be activated, and if I do I will probably devise another workaround.

Good luck with preparing to launch the release of BP 12!

Hi @imath,
I have set up a second staging site to test because of the issues I was having with my first one, to see if any are replicated; the good news is that the Reply button on activity comments is visible on this new stage, so it must be some weird anomaly with the first one which I doubt I will ever be able to figure out, much like my missing post that showed in detail the problem there.

However there is one issue that is still apparent, which is that, in Blocksy I have it set so that the main site menu highlights whichever page you are currently on (a fairly common feature on most sites), and if you are on a page that is a dropdown menu item, it highlights the parent menu item that it drops down from, as well as itself when the dropdown is visible. Unfortunately it seems that the new BP doesn’t play well with this setup (as I tried to explain earlier in this thread), so I had parent menu links to Activity (with Members and Groups as child menu items) and Profile (with several other child menu items such as Friends etc); when I visit the Profile page, the Profile parent item is not highlighted, but Activity is, and when I visit a child menu item of profile, both Profile and Activity are highlighted. If I move the Members child item to be a parent item, this is the one highlighted instead of Activity.
I looked more deeply, and discovered that in my setup, Activity, Members and Groups all have distinct page id numbers when you examine the html body class, while all pages connected to the Profile and associated links have the same page id as Members (logical as they are sub pages of Members in the BP urls), and individual groups have the same page id as Groups etc. Is there any way to have Profile separated from Members so that it has its own page id and distinct url? I think this is probably where my menu issue stems from, and I would assume this would be the case for others as well. There doesn’t seem to be any way (yet?) to create my own Profile pages using blocks which might be another way around this, or even a custom Members page (the blocks currently available don’t have an option to show an alphabetical or sortable list/grid). I’m sure I’m not alone in wanting a main menu link to the registered users individual pages, a dashboard, and having the menu show them where they are.

Secondly, I found that it wasn’t possible to add a main menu link for the currently logged-in user that remains visible at all times. Although I created a custom link, it only appeared in the menu when viewing specific sections (such as Profile, Activity, etc).

Thirdly, I encountered difficulties in adding a sidebar to any of the Buddypress pages, despite my default Blocksy setting for each page to have one. Upon investigation, I discovered that in the Customizer, Buddypress pages were being counted as Blog Posts. Intuitively, I would have expected this setting to be configured in the Buddypress-specific sections. As it stands, without extensive CSS modifications, this means Blog Pages and Buddypress pages will always have to share the same layout.

I’m curious if you’re considering incorporating enhancements or additional features in the Customizer at some point. In my experience, I’ve needed to make a significant number of CSS adjustments to align Buddypress with my desired color scheme and preferences in previous versions. It would be immensely helpful if at least some of this could be achieved through Customizer settings or a dedicated settings page within the plugin. Historically, Buddypress hasn’t adhered to my theme defaults, but I’m uncertain if this is specific to the theme I use or if it’s a widespread experience.

Hi there,

One possibility is to customize the landing page for visitors who are not logged in to your BuddyPress site, you have a few options. One option is to use a plugin like BuddyPress Redirect to Home Page, which lets you set any page as the home page for non-logged-in users. Another option is to use some code snippets in your functions.php file or a custom plugin, which can check the user’s login status and redirect them accordingly. For example, you can use something like this:

function bp_redirect_non_logged_in_users() {
if ( ! is_user_logged_in() && bp_is_component_front_page( ‘activity’ ) ) {
wp_redirect( home_url( ‘/welcome/’ ) ); // change this to your desired page
exit();
}
}
add_action( ‘template_redirect’, ‘bp_redirect_non_logged_in_users’ );

This code will redirect non-logged-in users who try to access the activity page to a welcome page instead. You can modify this code to suit your needs and preferences. You’d need to find the equivalent for the Jumble page in question.

Hi @imath,
I don’t know if one of the below might be related to what @vapvarun posted, but in my early testing of 12.0.0-beta1 (with latest WP and using Blocksy theme and Nouveau) there are a few things cropping up; firstly I don’t seem able to customise the css by duplicating Nouveau’s css in my Blocksy child theme folder, either inside a buddypress folder or just in the child theme folder, and can only achieve changes in my child theme’s style.css (I suspect this is unrelated to the new Buddypress but I haven’t yet tried it with Legacy); secondly, it doesn’t seem possible to add a main menu link to the currently logged in user that is visible at all times – I have created a custom link but it only appears in the menu when viewing the various sections (i.e. Profile, Activity etc); thirdly, I was struggling to add a sidebar to any of the BP pages, even though my default Blocksy setting is for each page to have one, and discovered that (in Blocksy at least) in Customizer it is counting BP pages as Blog Posts, whereas intuitively I would have thought this should be set in the BP specific sections, and without extensive css work means that Blog Pages and BP pages will always have to be the same. Are you considering adding/improving what can be done in the Customizer at some point? I have found I have to make an awful lot of CSS edits anyway to get BP to match my colour scheme and preferences in previous versions of BP and it would be a huge boon if at least some of this can be achieved with the Customizer settings (or a settings page in the plugin). BP has never followed my theme defaults, but I don’t know if that is because of the theme (and the two standard BP templates) I use or if it is like this for everyone.

Hi Naomi,

For the menu item, one option is to create a custom menu option and just insert the URL for the activity page.

For your newsletter sign up, don’t think I can help you as it’s the way it’s been implemented, it’s inserted a third column, making this wider is going to make one of the other columns narrower, which is not desirable. Maybe ask the plugin developer to change it?

Hi, I have similar problem. I want to use my own activity loop on different page. This page is template for my custom post type. I created it php that named as ‘single-{mytype}.php’. I can use my own activity loop inside of this page but there is some wird behaviours. For example comment, favourite or delete buttons not seem properly also I think ajax/js doesnt work properly.
I have used like this:

  <?php if ( bp_has_activities( bp_ajax_querystring( 'activity' ) . '&action=new_quote' ) ) : ?>
    <?php while ( bp_activities() ) : bp_the_activity(); ?>
 
	<?php bp_get_template_part( 'activity/entry' ); ?>
				
    <?php endwhile; ?>
<?php endif; ?>

I have these errors in my site.

Fatal error: Uncaught ArgumentCountError: 3 arguments are required, 2 given in /customers/5/b/d/eldamania.com/httpd.www/wp-content/plugins/buddypress/bp-blogs/bp-blogs-activity.php:230 Stack trace: #0 /customers/5/b/d/eldamania.com/httpd.www/wp-content/plugins/buddypress/bp-blogs/bp-blogs-activity.php(230): sprintf(‘%1$s ha escrito…’, ‘apply_filters(‘__construct(Array) #9 /customers/5/b/d/eldamania.com/httpd.www/wp-content/plugins/buddypress/bp-templates/bp-legacy/buddypress/activity/activity-loop.php(17): bp_has_activities(”) #10 /customers/5/b/d/eldamania.com/httpd.www/wp-includes/template.php(785): require(‘/customers/5/b/…’) #11
/customers/5/b/d/eldamania.com/httpd.www/wp-content/plugins/buddypress/bp-core/bp-core-template-loader.php(222): load_template(‘/customers/5/b/…’, false, Array) #12 /customers/5/b/d/eldamania.com/httpd.www/wp-content/plugins/buddypress/bp-core/bp-core-template-loader.php(67): bp_locate_template(Array, true, false, Array) #13 /customers/5/b/d/eldamania.com/httpd.www/wp-content/plugins/buddypress/bp-templates/bp-legacy/buddypress/activity/index.php(241): bp_get_template_part(‘activity/activi…’) #14 /customers/5/b/d/eldamania.com/httpd.www/wp-includes/template.php(785): require(‘/customers/5/b/…’) #15
/customers/5/b/d/eldamania.com/httpd.www/wp-content/plugins/buddypress/bp-core/bp-core-template-loader.php(222): load_template(‘/customers/5/b/…’, false, Array) #16 /customers/5/b/d/eldamania.com/httpd.www/wp-content/plugins/buddypress/bp-core/bp-core-template-loader.php(67): bp_locate_template(Array, true, false, Array) #17 /customers/5/b/d/eldamania.com/httpd.www/wp-content/plugins/buddypress/bp-core/bp-core-template-loader.php(407): bp_get_template_part(‘activity/index’, NULL, Array) #18 /customers/5/b/d/eldamania.com/httpd.www/wp-content/plugins/buddypress/bp-activity/classes/class-bp-activity-theme-compat.php(118): bp_buffer_template_part(‘activity/index’, NULL, false) #19
/customers/5/b/d/eldamania.com/httpd.www/wp-includes/class-wp-hook.php(308): BP_Activity_Theme_Compat->directory_content(”) #20 /customers/5/b/d/eldamania.com/httpd.www/wp-includes/plugin.php(205): WP_Hook->apply_filters(”, Array) #21 /customers/5/b/d/eldamania.com/httpd.www/wp-content/plugins/buddypress/bp-core/bp-core-theme-compatibility.php(767): apply_filters(‘bp_replace_the_…’, ”) #22 /customers/5/b/d/eldamania.com/httpd.www/wp-includes/class-wp-hook.php(308): bp_replace_the_content(”) #23 /customers/5/b/d/eldamania.com/httpd.www/wp-includes/plugin.php(205): WP_Hook->apply_filters(”, Array) #24 /customers/5/b/d/eldamania.com/httpd.www/wp-includes/post-template.php(255): apply_filters(‘the_content’, ”) #25 /customers/5/b/d/eldamania.com/httpd.www/wp-content/themes/twentyfourteen/content-page.php(20): the_content() #26 /customers/5/b/d/eldamania.com/httpd.www/wp-includes/template.php(785): require(‘/customers/5/b/…’) #27 /customers/5/b/d/eldamania.com/httpd.www/wp-includes/template.php(718): load_template(‘/customers/5/b/…’, false, Array) #28 /customers/5/b/d/eldamania.com/httpd.www/wp-includes/general-template.php(204): locate_template(Array, true, false, Array) #29 /customers/5/b/d/eldamania.com/httpd.www/wp-content/themes/twentyfourteen/page.php(33): get_template_part(‘content’, ‘page’) #30 /customers/5/b/d/eldamania.com/httpd.www/wp-includes/template-loader.php(106): include(‘/customers/5/b/…’) #31 /customers/5/b/d/eldamania.com/httpd.www/wp-blog-header.php(19): require_once(‘/customers/5/b/…’) #32 /customers/5/b/d/eldamania.com/httpd.www/index.php(17): require(‘/customers/5/b/…’) #33 {main} thrown in /customers/5/b/d/eldamania.com/httpd.www/wp-content/plugins/buddypress/bp-blogs/bp-blogs-activity.php on line 230

I haven’t used BuddyBuilder but after looking at their offering I would guess that you are correct that this plugin is the culprit. It looks like they provide some other templating system to replace some of the standard BuddyPress pages and provide an entire authentication process. I think the first course of action should be to work with them to fix the problem. I mean they offer this entire solution so I’m assuming it does work! Also, did you try disabling this plugin?

Anyway, when I go to Settings>BuddyPress>Pages, I have these 4:
Activate, Activity, Members, & Register.

There may be more or less depending on features you’ve enabled. Activate, Activity, and Members are all blank pages, while Register uses the shortcode ‘[bbp-register]‘ (its actually a bbPress page). You should be able to at least create these 3 blank pages and assign them on that settings page.

Here’s another post about missing pages: https://buddypress.org/support/topic/how-to-create-login-and-register-pages/

Moderator shanebp says “BP does not handle a login page.” Here again I have a page with a bbPress shortcode ‘[bbp-login]‘. So basically it looks like login and registration need to be handled by some other plugin or theme.

There are hooks that can be used to modify these pages, but full control over content and styling would probably require a theme, plugin, or custom page templates. I tried Elementor with BuddyPress but quickly found that Elementor was making the process too complicated. TBH I think Elementor gets in they way more than it helps. I ended up using Blocksy and Stackable.