To disable seeing other members’ pages in BuddyPress, you can use the following steps:
Log in to your WordPress admin dashboard.
Navigate to the “Settings” section, then select the “Privacy” tab.
Under the “Members” section, select the option “Only allow site administrators to view member profiles.”
Click “Save Changes” to apply the setting.
With this setting enabled, only site administrators will be able to view member profiles. Regular members will not be able to access other members’ pages.
Note: These instructions are based on BuddyPress version 7.0 and higher. If you are using an older version of BuddyPress, the steps may be different. Also, make sure to take a backup of your site before making any changes.
If anyone wants a filter to fix the case where a given user hasn’t edited their profile yet (and thus doesn’t have the bp_xprofile_visibility_levels user meta), resulting in all of their fields being visible:
// Fix for BuddyPress not respecting the default xProfile field visibility
// if a user has not yet edited their profile (and thus saving the user meta
// <code>bp_xprofile_visibility_levels</code> for that user).
// See: https://buddypress.org/support/topic/only-me-extended-profile-field-visible-to-all-users/
// See: https://buddypress.trac.wordpress.org/ticket/8093
add_filter( 'bp_xprofile_get_hidden_fields_for_user', function ( $hidden_fields, $displayed_user_id, $current_user_id ) {
if ( empty( $hidden_fields ) ) {
// Get the visibilities that should be hidden for the current user pair.
$hidden_field_types_for_user = bp_xprofile_get_hidden_field_types_for_user( $displayed_user_id, $current_user_id );
// Get the visibility defaults for all xProfile fields.
$default_visibility_levels = \BP_XProfile_Group::fetch_default_visibility_levels();
// Create the list of field IDs that should be hidden.
$hidden_fields = array_keys( array_filter(
$default_visibility_levels,
function ( $default_visibility_level ) use ( $hidden_field_types_for_user ) {
return empty( $default_visibility_level['default'] ) || in_array( $default_visibility_level['default'], $hidden_field_types_for_user, true );
}
) );
}
return $hidden_fields;
}, PHP_INT_MAX, 3 );
Thanks for your report, it will be fixed in 12.0 version: https://buddypress.trac.wordpress.org/ticket/8820
Hi @yoshibot
Your error log file says bp_get_deprecated_functions_versions() is not available. This function was introduced in version 11.0.0 of BuddyPress. I’ve just tested BuddyPress 11.0.0 using WordPress regular and multisite configs and I confirm when I try to login everything behaves as expected. I cannot reproduce your error.
When I look at your previous messages in this thread, I thought you decided to roll back to BuddyPress 10.6?
Could you please provide more information about what BuddyPress version you are using, what WordPress config you are using (regular or multisite) and how BuddyPress has been activated on your site if you are using a multisite config (eg: on the network/main site or on a subsite of the network)?
FYI: I have suggested “%s heeft een nieuw bericht geschreven” as a new translation for “%s wrote a new post” at https://translate.wordpress.org/projects/wp-plugins/buddypress/stable/nl/default/
Hi @jakobuz
This is really weird, because:
– sprintf() is not used at line 233 in https://buddypress.trac.wordpress.org/browser/tags/11.0.0/src/bp-blogs/bp-blogs-activity.php#L233. Have you edited this file?
– “3 arguments are required, 2 given”: 3 arguments were required in BuddyPress 10.6.0 and below but only for multisite configs. Are you using multisite?
– It looks like you still had 10.6 code inside 11.0 for the bp_blogs_format_activity_action_new_blog_post() function.
– Have you kept the bp-blogs/bp-blogs-activity.php file you had when you upgraded to 11.0, I’d be curious to see it.
I’ve tested everything into this area for regular and multisite configs and I can’t reproduce.
While it’s still early in the process, there has been some mixed reception around PHP 8.2 and WordPress core, plugin, and theme compatibility. Mylincoln Portal
Buddypress 11.0.0
Wordpress .1.1
PHP 8.1.14
/wp-content/plugins/buddypress/bp-blogs/bp-blogs-activity.php. Foutmelding: Uncaught ArgumentCountError: 3 arguments are required, 2 given in /var/www/vhosts/freya.nl/httpdocs/wp-content/plugins/buddypress/bp-blogs/bp-blogs-activity.php:233
Stack trace:
#0 /var/www/vhosts/freya.nl/httpdocs/wp-content/plugins/buddypress/bp-blogs/bp-blogs-activity.php(233): sprintf()
#1 /var/www/vhosts/freya.nl/httpdocs/wp-content/plugins/buddypress/bp-activity/bp-activity-functions.php(2312): bp_blogs_format_activity_action_new_blog_post()
#2 /var/www/vhosts/freya.nl/httpdocs/wp-content/plugins/buddypress/bp-activity/bp-activity-functions.php(4180): bp_activity_post_type_publish()
#3 /var/www/vhosts/freya.nl/httpdocs/wp-includes/class-wp-hook.php(308): bp_activity_catch_transition_post_type_status()
#4 /var/www/vhosts/freya.nl/httpdocs/wp-includes/class-wp-hook.php(332): WP_Hook->apply_filters()
#5 /var/www/vhosts/freya.nl/httpdocs/wp-includes/plugin.php(517): WP_Hook->do_action()
#6 /var/www/vhosts/freya.nl/httpdocs/wp-includes/post.php(5347): do_action()
#7 /var/www/vhosts/freya.nl/httpdocs/wp-includes/post.php(4607): wp_transition_post_status()
#8 /var/www/vhosts/freya.nl/httpdocs/wp-includes/post.php(4819): wp_insert_post()
#9 /var/www/vhosts/freya.nl/httpdocs/wp-admin/includes/post.php(426): wp_update_post()
#10 /var/www/vhosts/freya.nl/httpdocs/wp-admin/post.php(227): edit_post()
Hello, since the new version I can not update posts anymore. I reverted it back to version 10.6.0 and everything is working fine. It would be nice if someone could help me out. Thank you!
WordPress version 6.1.1
BuddyPress (version 11.0.0)
PHP version 8.0.26
Foutdetails
===========
Een fout van het type E_ERROR werd veroorzaakt op regelnummer 233 van het bestand /home/deb74155/domains/rugzaklopers.nl/public_html/wordpress/wp-content/plugins/buddypress/bp-blogs/bp-blogs-activity.php. Foutmelding: Uncaught ArgumentCountError: 3 arguments are required, 2 given in /home/deb74155/domains/rugzaklopers.nl/public_html/wordpress/wp-content/plugins/buddypress/bp-blogs/bp-blogs-activity.php:233
Stack trace:
#0 /home/deb74155/domains/rugzaklopers.nl/public_html/wordpress/wp-content/plugins/buddypress/bp-blogs/bp-blogs-activity.php(233): sprintf()
#1 /home/deb74155/domains/rugzaklopers.nl/public_html/wordpress/wp-includes/class-wp-hook.php(308): bp_blogs_format_activity_action_new_blog_post()
#2 /home/deb74155/domains/rugzaklopers.nl/public_html/wordpress/wp-includes/plugin.php(205): WP_Hook->apply_filters()
#3 /home/deb74155/domains/rugzaklopers.nl/public_html/wordpress/wp-content/plugins/buddypress/bp-activity/bp-activity-functions.php(1633): apply_filters()
#4 /home/deb74155/domains/rugzaklopers.nl/public_html/wordpress/wp-content/plugins/buddypress/bp-activity/classes/class-bp-activity-activity.php(209): bp_activity_generate_action_string()
#5 /home/deb74155/domains/rugzaklopers.nl/public_html/wordpress/wp-content/plugins/buddypress/bp-activity/classes/class-bp-activity-activity.php(167): BP_Activity_Activity->populate()
#6 /home/deb74155/domains/rugzaklopers.nl/public_html/wordpress/wp-content/plugins/buddypress/bp-activity/bp-activity-functions.php(2379): BP_Activity_Activity->__construct()
#7 /home/deb74155/domains/rugzaklopers.nl/public_html/wordpress/wp-content/plugins/buddypress/bp-activity/bp-activity-functions.php(4176): bp_activity_post_type_update()
#8 /home/deb74155/domains/rugzaklopers.nl/public_html/wordpress/wp-includes/class-wp-hook.php(308): bp_activity_catch_transition_post_type_status()
#9 /home/deb74155/domains/rugzaklopers.nl/public_html/wordpress/wp-includes/class-wp-hook.php(332): WP_Hook->apply_filters()
#10 /home/deb74155/domains/rugzaklopers.nl/public_html/wordpress/wp-includes/plugin.php(517): WP_Hook->do_action()
#11 /home/deb74155/domains/rugzaklopers.nl/public_html/wordpress/wp-includes/post.php(5347): do_action()
#12 /home/deb74155/domains/rugzaklopers.nl/public_html/wordpress/wp-includes/post.php(4607): wp_transition_post_status()
#13 /home/deb74155/domains/rugzaklopers.nl/public_html/wordpress/wp-includes/post.php(4819): wp_insert_post()
#14 /home/deb74155/domains/rugzaklopers.nl/public_html/wordpress/wp-admin/includes/post.php(426): wp_update_post()
#15 /home/deb74155/domains/rugzaklopers.nl/public_html/wordpress/wp-admin/post.php(227): edit_post()
#16 {main}
thrown
I’m using the latest WordPress and Buddypress. From the Dashboard, If I click Settings and then Buddypress, there are 3 tabs to change settings: Components, Options, and Pages. When I select Components or Options, I don’t see the “Save Changes” button below the tables with the settings. On the Pages tab, the button apprears.
I’m using the Phlox theme. When I change to the Twenty-Twenty-Three theme, the buttons do show.
When I examine the elements in my browser, I can see that the button is in the HTML for Components and Options, but is wrapped by a <p> tag with a class of Submit and Clear. On the Pages tab, the button is wrapped by a <p>tag with only a class of Submit.
The Phlox Theme is using a class Clear which includes overflow: hidden and visibility: hidden. The Twenty-Twenty-Three theme is using a class Clear without the overflow or visibility attributes.
Is the “Clear” class in the <p> for the Components and Options tabs a mistake or does Phlox need to change the way it defines Clear?
It’s frustrating to have to inspect elements and change the overflow and visibility every time I want to change any of these settings.
Advice on this would be greatly appreciated.
Hi,
I noticed one strange thing when I checked BuddyPress Emails section on WordPress Dashboard. Many of the “situations” are missing. So it looks like the emails are not connected to any situation. That would explain why the system is not sending them. What about you?
I wonder also if this has something to do with my multilingual setup: I’m using Polylang and Multilanguage BuddyPress with Polylang plugin (https://github.com/awsmug/multilanguage-buddyPress-with-polylang). It used to work perfectly…
Anonymous User 18187419Inactive
Storml, recently a similar issue was caused by a custom theme, try testing with a default WordPress theme.
I use BuddyPress And Paid Memberships Pro on my website. So, My Problem is, When Members post anything in BuddyPress. Then non-members can’t see their posts. I want when any member posts anything then this post can see any user. Please give me a solution. How to make this. My website link is: https://nachbarschaftshilfe-ostholstein.de/
My WordPress version: 6.0.3
BuddyPress Plugin Version: 10.3.0
Paid memberships pro version: 2.9.8
Paid Memberships Pro – BuddyPress & BuddyBoss Add On: 1.3.1
Hi @fantamily
Thanks a lot for your feedback. The issue is actually caused by some custom code wrongly using the bp_get_send_message_button_args filter. Instead of returning an empty array to disable the private button on members profile header, this custom code retuns false.
That being said. We should be more cautious about this potential wrong usage, so we’ll have it fixed asap (next minor version 11.1.0).
See https://buddypress.trac.wordpress.org/ticket/8800 to follow our progress about it.
Hi @yoshibot,
Here’s the link to download previous version of BuddyPress: https://downloads.wordpress.org/plugin/buddypress.10.6.0.zip
FWIW, I can’t reproduce the issue you shared about notifications. For me everything works as expected, see:
Hello, I immediately apologize for my language. In general, the versions are all the latest and wordpress and buddypress. website https://withoutbadhabbits.ru / The problem is that if you log in via social networks, then it is not possible to change the avatar, and if you register through the standard form, everything works (login via social networks via the socializer) . Tell me what’s wrong I’m new to this business
Hello,
I’m using WordPress 6.1.1 running Twenty Twenty-Three theme, BuddyPress Version 11.0.
https://math.cwelms.org/
I’ve seen similar topics to mine here, which is this:
BuddyPress Forum works fine, but I cannot create any BuddyDocs, linked to a BuddyGroup. When I try to create on the frontend, I end up on a page that says, “Archives: Doc, Create a Doc” but when I click on the Create a Doc link, nothing happens.
I can create BuddyDocs on the Dashboard, but can’t connect them to a group.
I created an open ‘beta’ group if you want to try yourself.
when i drop back to the Twenty Twenty theme, I can create docs, which makes me think that the issue is somewhere with the WordPress editor.
When I revert to the Twenty Twentythree theme, the docs I created when using the TwentyTwenty theme are still there and editable.
What do I need to do with the TwentyTwenty-Three theme to create BuddyDocs?
robert lewis
@officialmymilestonecard
I think you have a different issue – this is just an error appearing in debug logs, and certainly in my case it is not visually affecting anything I am aware of, maybe slowing the site down though. I would start a new thread if you haven’t already, and include any extra information you can to help others diagnose the problem, such as any errors in the console, debug logs, or any other info like which version of wordpress, theme etc. You might also want to try deactivating then reactivating Buddypress before all that to see if it helps.
Hello, my WP version is 6.1.1 my BuddyPress version is 11.0.0
I used the Theme https://themeforest.net/item/armadon-gaming-community-wordpress-theme/27957394?gclid=Cj0KCQiAiJSeBhCCARIsAHnAzT_68l6iD7qmpDX1_KFM-VnNqRGmsOrPpQ1dfq7xAjjg6jMI0PdAUDkaAlK0EALw_wcB
I get this issue when users attempt to log in into my website they get the message “Method not Allowed” and I can’t seem to be able to fix it
I would like to add my name to this list but I am only getting the line 1577 error. I am wondering if it might be related to either or both of the following things – I have Better Messages plugin installed and I am running PHP version 8.1. Can the other two who have posted say if they have one or both of these things? There might be a common denominator. I am running the most recent updates of WordPress and of course Buddypress.
I am using the following:
WP Version: 6.1.1
Permalink: /%postname%/
Active Theme: BuddyX 4.4.5
Platform: Windows
Browser Name Chrome
PHP Version: 8.0.7
MySQL Version: 5.5.5
The plugins I have are these:
Activity Plus Reloaded for BuddyPress 1.0.8
Akismet Anti-Spam 5.0.2
BP Friends Suggestions Widget 1.1.0
BP Profile Search 5.4.7
BuddyPress 11.0.0
BuddyPress Activity ShortCode 1.1.8
BuddyPress Extended Friendship Request 1.2.1
BuddyPress Global Search 1.2.1
BuddyPress Login Redirect to Profile 1.2.3
BuddyPress Profile Completion 1.0.8
BuddyPress Simple Terms And Conditions 1.3
BuddyPress Xprofile Custom Field Types 1.2.5
Classic Editor 1.6.2
Classic Widgets 0.3
Colorlib Login Customizer 1.3.1
CookieYes | GDPR Cookie Consent 3.0.8
Custom Font Uploader 2.0.0
Duplicator 1.5.1
Easy Registration Forms 2.1.1
Force Login 5.6.3
GEO my WP 3.7.2.1
Kirki Customizer Framework 4.0.24
Quick and Easy FAQs 1.3.6
Shared Counts 1.4.1
Verified Member for BuddyPress 1.2.6
Wbcom Designs – BuddyPress Member Reviews 2.8.3
WordPress Username Availability Checker 1.1.8
I have configured a new Register page using ERForms. I’ve created just a wordpress page which has only a shortcode to the ERform.
I’ve set it at buddypress settings-> Pages -> register. Buddypress is redirecting to the wordpress regitration page instead of my page.
I’ve also changed the redirection at buddypress setting to whatever page (for example my FAQ page) and always redirects to the wordpress registration page.
I’ve tried also deactivating all plugin but buddypress and ERforms and no, buddypress is always redriecting to the standard wordpress registration page instead of what I am setting.
Any hint / idea what to cope this problem?
Thnks in advance
Anonymous User 18187419Inactive
Hi, I’m not sure about that, reach out to your theme developer for advice.
Meantime, easiest & safest way for you to add code snippets to your site would be to use the free plugin Code Snippets, get it from the wordpress.org plugins page.
Hi @philippklaschka
Thanks for your report, this issue seems to be caused by this plugin https://github.com/projectestac/wordpress-invite-anyone/ It hooks to bp_core_install_emails to run the function ass_install_emails that does not exist see: https://github.com/projectestac/wordpress-invite-anyone/blob/master/by-email/by-email.php#L1710
I advise you to deactivate this plugin, update BuddyPress and then reactivate this plugin once done. The bp_core_install_emails hook is only fired by BuddyPress when you install/upgrade and use the tool to reinstall emails, so it should be ok. But I strongly advise you to contact the plugin author so that he fixes this issue.
Hi @netmanuth
Thanks for your report, I’ll check BuddyX, but I doubt issue is with this theme.
tried 3 times to update and every time it blows up my backend with this fatal error. Have to roll back all plugins via database and reactivate all just to roll back this patch.
Can someone decipher whats going on here?
Fatal error: Uncaught TypeError: call_user_func_array(): Argument #1 ($callback) must be a valid callback, function “ass_install_emails” not found or invalid function name in /homepages/17/d4296816486/htdocs/wordpress/wp-includes/class-wp-hook.php:308 Stack trace: #0 /homepages/17/d4296816486/htdocs/wordpress/wp-includes/class-wp-hook.php(332): WP_Hook->apply_filters(”, Array) #1 /homepages/17/d4296816486/htdocs/wordpress/wp-includes/plugin.php(517): WP_Hook->do_action(Array) #2 /homepages/17/d4296816486/htdocs/wordpress/wp-content/plugins/buddypress/bp-core/admin/bp-core-admin-schema.php(555): do_action(‘bp_core_install…’) #3 /homepages/17/d4296816486/htdocs/wordpress/wp-content/plugins/buddypress/bp-core/bp-core-update.php(770): bp_core_install_emails() #4 /homepages/17/d4296816486/htdocs/wordpress/wp-content/plugins/buddypress/bp-core/bp-core-update.php(291): bp_update_to_11_0() #5 /homepages/17/d4296816486/htdocs/wordpress/wp-content/plugins/buddypress/bp-core/bp-core-update.php(159): bp_version_updater() #6 /homepages/17/d4296816486/htdocs/wordpress/wp-includes/class-wp-hook.php(308): bp_setup_updater(”) #7 /homepages/17/d4296816486/htdocs/wordpress/wp-includes/class-wp-hook.php(332): WP_Hook->apply_filters(NULL, Array) #8 /homepages/17/d4296816486/htdocs/wordpress/wp-includes/plugin.php(517): WP_Hook->do_action(Array) #9 /homepages/17/d4296816486/htdocs/wordpress/wp-content/plugins/buddypress/bp-core/admin/bp-core-admin-actions.php(120): do_action(‘bp_admin_init’) #10 /homepages/17/d4296816486/htdocs/wordpress/wp-includes/class-wp-hook.php(308): bp_admin_init(”) #11 /homepages/17/d4296816486/htdocs/wordpress/wp-includes/class-wp-hook.php(332): WP_Hook->apply_filters(NULL, Array) #12 /homepages/17/d4296816486/htdocs/wordpress/wp-includes/plugin.php(517): WP_Hook->do_action(Array) #13 /homepages/17/d4296816486/htdocs/wordpress/wp-admin/admin.php(175): do_action(‘admin_init’) #14 /homepages/17/d4296816486/htdocs/wordpress/wp-admin/plugins.php(10): require_once(‘/homepages/17/d…’) #15 {main} thrown in /homepages/17/d4296816486/htdocs/wordpress/wp-includes/class-wp-hook.php on line 308
