BuddyPress.org

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

@imath FWIW, back in 2021 there was some discussion regarding the ActivityPub and BuddyPress connectivity/integration (for lack of a better term) which can be found at the following:

Buddypress Integration

Hello,
The issue is most likely caused by the Hotsteel theme. To confirm this, temporarily switch to a default WordPress theme such as 2020. If the problem doesn’t persist with the default theme, you should reach out to Hotsteel for assistance with resolving the ajax errors.
Best Regard,
Custom Serum Boxes

The error message you’ve encountered is related to the Elementor plugin in WordPress. It seems like there’s an issue with the plugin’s code, specifically in the Controls_Stack class when trying to sanitize settings. Here’s a breakdown of the error:

Argument 1 passed to Elementor\Controls_Stack::sanitize_settings() indicates that the sanitize_settings method of the Controls_Stack class is expecting an array as its first argument.
must be of the type array, null given means that the function received null instead of an array as the argument.
The error occurred when the code called this method in the file /wp-content/plugins/elementor/includes/base/controls-stack.php on line 1084.
To resolve this issue, you can try the following steps:

Check for Plugin Conflicts: Sometimes, conflicts with other plugins can cause such errors. Deactivate other plugins one by one to see if the issue persists when Elementor is the only active plugin.

Update Elementor: Make sure you’re using the latest version of the Elementor plugin. Outdated versions may contain bugs that have been fixed in newer releases.

Check for Theme Compatibility: Your WordPress theme might not be fully compatible with the version of Elementor you’re using. Try switching to a default WordPress theme (e.g., Twenty Twenty-One) temporarily to see if the error still occurs.

Debugging: If the issue persists, you may need to debug the specific code in the Elementor plugin. This usually requires some knowledge of PHP and WordPress development. You can use debugging tools like Xdebug or enable WordPress debugging to get more information about the error.

Contact Elementor Support: If you can’t resolve the issue on your own, consider reaching out to Elementor’s support or community forums. They may have encountered similar issues and can provide guidance on how to fix it.

Backup and Restore: As a last resort, if none of the above solutions work, you can try restoring a backup of your WordPress site to a point before the error occurred. This should revert your site to a stable state, but you’ll lose any changes made after the backup date.

Remember to take proper precautions, such as backing up your site and data, before making any significant changes to your WordPress installation.