BuddyPress.org

Two ways to use your BP profile pic as your WordPress avatar:
1. Plugins:
Install and activate a plugin like “BuddyPress Default Avatar” or “BuddyPress Avatar Sync.”
These plugins automatically sync your BP profile photo with your WordPress avatar, making it a simple and hands-off solution.

2. Custom code:
If you prefer a more technical approach, you can add code to your theme’s functions.php file.
This code snippet will enable syncing of the two avatars:

PHP
function bp_avatar_sync($user_id) {
// Get BP profile picture URL
$bp_avatar_url = bp_core_fetch_avatar(array(‘item_id’ => $user_id, ‘type’ => ‘full’));

// Update WordPress avatar URL
update_user_meta($user_id, ‘user_avatar’, $bp_avatar_url);
}
add_action(‘bp_core_avatar_uploaded’, ‘bp_avatar_sync’);

Remember, both methods achieve the same result. Choose the method that best suits your technical skills and preferences.

@sbanner26, my apologies for not posting this sooner, I was contemplating various scenarios based on the limited information provided and not having access to the BP Member Export Import plugin (it doesn’t reside in the official WordPress plugin repository). That stated, let’s see what you think about the proposed:

This solution is an attempt to mitigate risk for updating a user’s registration date by utilizing a WP plugin known as Edit Registration Date. This plugin adds an editable text box to each user’s profile page, as can be seen in the following screenshot:

This plugin is located in the WP plugin repository at the following URL:

Edit Registration Date

The author of this plugin has only tested up to WP 6.2.3; meaning, I’m not sure why the author hasn’t tested, as of yet, to the current version of WP. As an aside, I tested it with WP 6.4.1 and it works as advertised. The plan would be to install stated plugin on both sites, perform a copy & paste and then update profile for each user. After completion, you can discard this plugin,, if you choose to do so. Albeit, this is a manual effort but, to reiterate, it presents the least amount of risk for updating a user’s registration date.

Having stated the previous, this now brings up the subject as to where the fault lies with the BP Member Export Import plugin by Wbcom Designs, if any. Was it a setting that needed to be set, i.e., use original registration date or make the dates all the same? Or, is it an actual bug? If it is a bug then, this bug should be reported, as such, to Wbcom Designs by someone who has actually witnessed this anomaly.

Furthermore, you may be able to determine in which process the fault, if any, may exist since there is, apparently, a 2 (two) step process, e.g., export and import: meaning, if you import the CSV file into a spreadsheet (MS Excel, OpenOffice/LibreOffice Calc or Google Sheets) the column that represents “registration_date” (the actual DB column name is “user_registered”) will indicate whether the dates are correct or not. If the dates are correct then the export process is not at fault and if the dates are not correct, you can infer that a fault may exist with the “export” process.

If by chance and assuming the dates are incorrect as indicated by the spreadsheet, the dates can be manually corrected in the spreadsheet and then save/export the corrections as a CSV file then, utilize the import feature of BP Member Export Import plugin. Note: The video for this plugin shows that there is a checkbox “Enable checkbox to update existing users data” thus, you should enable the checkbox since you have existing users.

Last but not least, there are other solutions that are applicable but, I’m not sure they are worth the effort (that is, my effort) to convey at a practical level given that your situation isn’t one that occurs on a regular basis, at least I would hope not, however, if this proposed solution is not practical, I may reconsider my position on this. Additionally, if this is truly a fault that lies with the BP Member Export Import plugin by Wbcom Designs then, reporting this fault to the developers of stated plugin would allow them to fix this fault and then you could use the new version to repeat the export/import process but this time it would work, given that no new bugs/faults were introduced.

To allow any logged-in user to post in your bbPress forum within a specific BuddyPress group, go to your WordPress dashboard, navigate to Forums > [Your Forum], and adjust the forum’s settings. Look for permissions or access settings and set them to “Logged In Users” rather than restricting it to group members only.

There is a very long running issue about that, it seems, on bbpress trac here https://bbpress.trac.wordpress.org/ticket/3355#comment:4
if you have any more info on that, please share.

Either wait for a bbPress update (it seems that it is in a slow pace lately), or maybe include a function hooking to bbp_get_replies_pagination_base filter (for replies as an example) to fix it on buddyPress side? (or on theme/plugins dev side but then it would probably be a good thing to include it in the docs somewhere?)

@imath, then that was implemented between 10.3 and 11.4 😉 I will read more about this new Block Themes feature, thanks for the hint.
Can I ask you (around) when version 12.0 will be live on WordPress ? No hurry, just for information.

Hello,

I just updated wordpress to version 6.4.1 and buddypress buddypress 12.0 beta 4 and this error no longer occurs.

I updated to wordpress 6.4 while using buddypress beta 3. Accessing a members profile while I was logged out triggerd a fatal error. This is the info in my debug log below

2023-11-08T16:55:16+00:00 CRITICAL Uncaught TypeError: Illegal offset type in /var/www/wptbox/wp-content/plugins/buddypress/bp-activity/bp-activity-functions.php:800
Stack trace:
#0 /var/www/wptbox/wp-content/plugins/buddypress/bp-blogs/bp-blogs-activity.php(1038): bp_activity_post_type_get_tracking_arg()
#1 /var/www/wptbox/wp-includes/class-wp-hook.php(324): bp_blogs_new_blog_comment_query_backpat()
#2 /var/www/wptbox/wp-includes/plugin.php(205): WP_Hook->apply_filters()
#3 /var/www/wptbox/wp-content/plugins/buddypress/bp-core/bp-core-functions.php(401): apply_filters()
#4 /var/www/wptbox/wp-content/plugins/buddypress/bp-activity/bp-activity-template.php(291): bp_parse_args()
#5 /var/www/wptbox/wp-content/themes/klein-child/buddypress/activity/activity-loop.php(3): bp_has_activities()
#6 /var/www/wptbox/wp-includes/template.php(792): require('...')
#7 /var/www/wptbox/wp-content/plugins/buddypress/bp-core/bp-core-template-loader.php(222): load_template()
#8 /var/www/wptbox/wp-content/plugins/buddypress/bp-core/bp-core-template-loader.php(67): bp_locate_template()
#9 /var/www/wptbox/wp-content/themes/klein-child/buddypress/members/single/activity.php(41): bp_get_template_part()
#10 /var/www/wptbox/wp-includes/template.php(792): require('...')
#11 /var/www/wptbox/wp-content/plugins/buddypress/bp-core/bp-core-template-loader.php(222): load_template()
#12 /var/www/wptbox/wp-content/plugins/buddypress/bp-core/bp-core-template-loader.php(67): bp_locate_template()
#13 /var/www/wptbox/wp-content/themes/klein-child/buddypress/members/single/home.php(34): bp_get_template_part()
#14 /var/www/wptbox/wp-includes/template.php(792): require('...')
#15 /var/www/wptbox/wp-content/plugins/buddypress/bp-core/bp-core-template-loader.php(222): load_template()
#16 /var/www/wptbox/wp-content/plugins/buddypress/bp-core/bp-core-template-loader.php(67): bp_locate_template()
#17 /var/www/wptbox/wp-content/plugins/buddypress/bp-core/bp-core-template-loader.php(407): bp_get_template_part()
#18 /var/www/wptbox/wp-content/plugins/buddypress/bp-members/classes/class-bp-members-theme-compat.php(212): bp_buffer_template_part()
#19 /var/www/wptbox/wp-includes/class-wp-hook.php(324): BP_Members_Theme_Compat->single_dummy_content()
#20 /var/www/wptbox/wp-includes/plugin.php(205): WP_Hook->apply_filters()
#21 /var/www/wptbox/wp-content/plugins/buddypress/bp-core/bp-core-theme-compatibility.php(767): apply_filters()
#22 /var/www/wptbox/wp-includes/class-wp-hook.php(324): bp_replace_the_content()
#23 /var/www/wptbox/wp-includes/plugin.php(205): WP_Hook->apply_filters()
#24 /var/www/wptbox/wp-includes/post-template.php(256): apply_filters()
#25 /var/www/wptbox/wp-content/themes/klein/buddypress-full-content.php(20): the_content()
#26 /var/www/wptbox/wp-includes/template.php(792): require('...')
#27 /var/www/wptbox/wp-includes/template.php(725): load_template()
#28 /var/www/wptbox/wp-includes/general-template.php(206): locate_template()
#29 /var/www/wptbox/wp-content/themes/klein-child/buddypress.php(90): get_template_part()
#30 /var/www/wptbox/wp-includes/template-loader.php(106): include('...')
#31 /var/www/wptbox/wp-blog-header.php(19): require_once('...')
#32 /var/www/wptbox/index.php(17): require('...')
#33 {main}
  thrown in /var/www/wptbox/wp-content/plugins/buddypress/bp-activity/bp-activity-functions.php on line 800

To achieve the functionality you described, you can add the following PHP code snippet to your WordPress plugin or theme’s functions.php file. This code will hide the activity form from all users except admins:

php
Copy code
function hide_activity_form_for_non_admins() {
if ( ! current_user_can( ‘administrator’ ) ) {
?>
<style type=”text/css”>
.activity-form-class {
display: none;
}
</style>
<?php
}
}
add_action( ‘admin_head’, ‘hide_activity_form_for_non_admins’ );
In this code snippet:

current_user_can(‘administrator’) checks if the current user is an administrator.
If the current user is not an administrator, it adds a <style> block to the <head> of the admin pages, setting the CSS property display: none; for the element with the class activity-form-class. Make sure to replace activity-form-class with the actual class name or ID of the activity form element in your HTML markup.
EXP3RTS ensures you have a backup of your site or are comfortable with making changes to your theme/plugin files before adding this code. Additionally, modify the class name in the code to match the actual class or ID of your activity form for it to work correctly.
I HOPE THIS IS BENEFICIAL FOR YOU