BuddyPress.org

I’m guessing you have a rogue code snippet that is overriding BuddyPress’ avatar code.

Check your theme’s functions.php file located at /wp-content/YOUR-THEME/functions.php also check /wp-content/plugins/bp-custom.php. Look for any code snippet that references avatars. Can you find any?

Also check any BuddyPress plugins you may have.

testbp.org uses both the BuddyPress and the bbPress plugins.

bbPress has its own built-in forum subscription feature; BuddyPress does not have a group forum subscription feature built-in.

However, there is a BuddyPress plugin that enables members to subscribe to a group – BP Group Email Subscription:
https://wordpress.org/extend/plugins/buddypress-group-email-subscription/

@mentions work the way you intended them to; they leave a notification in the WP Toolbar for the user and concurrently notifies the user via email.

If you want something more immediate and Facebook-like, use Brajesh Singh’s Live Notification plugin:
http://buddydev.com/uncategorized/introducing-buddypress-live-notification-plugin-a-facebook-like-notification-plugin-for-buddypress/

Might need updating.

After much searching by @karmatosed and I, we’ve found it’s the https://wordpress.org/extend/plugins/wangguard/ plugin. You’ll need to contact the author for support.

@james_loudon – I was just re-reading your post and I think I know what you are experiencing.

Login to the WP dashboard and navigate to “Settings > Discussion”.

Scroll down to “Default Avatar” and select the avatar you want to use for members that do not have an uploaded avatar.

@djpaul: If there’s anyone more “The Man” than you, I don’t know who he is.

THANKS A MILLION! I learned something new today. The renaming plugin folder worked.

@kmtrent – you probably have some code in a plugin or a theme that assumes BuddyPress is always loaded. This isn’t always the case, and obviously causes problems like this.

@ezcs – if you read your error line, you see it is coming from from plugins/buddypress-like/. That plugin hasn’t been updated for almost two years. Which version of BuddyPress did you upgrade from? Regardless, go into your site via FTP (or however you normally upload files), go into plugins, and rename the “buddypress-like” folder into something else. This should let you log back in to your site, go to the plugins page and it should display a message about a “broken plugin”.

Read this topic if you want to add more fields to the status update. https://buddypress.org/community/groups/creating-extending/forum/topic/adding-a-second-element-for-posting-with-an-activity/?topic_page=1&num=15

But I think a better approach is to create a component.

OH MY GOD!! I got the same sort of error after the 1.6 update installation. I can’t do anything with the site now.

Fatal error: Call to undefined function is_site_admin() in /home/content/e/z/c/ezcs2009/html/wsnursing/wp-content/plugins/buddypress-like/bp-like.php on line 248

@rodtrent – Disable all 3rd-party plugins you are using except BuddyPress – this includes JetPack, BP Gallery, etc. Next, change your theme to the bp-default theme. Now, retry your BP pages. Does your problem still occur?

@notpoppy – For this line:

`if ( groups_get_groupmeta( $bp->groups->current_group->id, ‘settings_complete’ ) )`

You could probably change that to do your check against group ID

eg.

`if ( bp_get_group_id() == MY_GROUP_ID )
return true;
elseif ( bp_get_group_id() == ANOTHER_GROUP_ID )
return true;
else
return false;
`

etc.

If you want to do your check by group name, try using `bp_get_group_name()` in place of `bp_get_group_id()`.

This is untested, but hopefully this gives you a few ideas to work with.

@bakelady – In BP 1.6, the member count behavior changed to reflect the active users on your site and not total members.

To revert this behavior, can you try this code snippet in /wp-content/plugins/bp-custom.php?

`add_filter( ‘bp_get_total_member_count’, ‘bp_core_get_total_member_count’ );`

If you don’t have a file located at /wp-content/plugins/bp-custom.php, follow the tutorial available here:
https://codex.buddypress.org/extending-buddypress/bp-custom-php/

Let me know if this works for you.

@dacai – It sounds like these shortcodes rely on javascript to work.

There maybe a conflict between your plugin’s javascript, BuddyPress’ javascript and/or your theme’s javascript (assuming you are not using a variant of the bp-default theme).

I would try to find out the culprit by debugging the javascript with your browser’s developer tool.

If you’re using Firefox, try installing Firebug.

Here’s a video tutorial on how to use Firebug:
http://www.dev4press.com/2010/tutorials/wordpress/various/use-firebug-to-track-ajax-requests-and-responses/

Once you have it installed, turn on the Firebug console and reload your page. If there are errors, the Firebug console will tell you which javascript files are failing.

By 2010 install, do you mean BuddyPress v1.2.x or older?

If so, you need to upgrade in stages.

Check out the “Upgrading BuddyPress” codex article for more details:
https://codex.buddypress.org/buddypress-site-administration/upgrading-buddypress/

I should note this is an arduous task that will probably require a lot of troubleshooting and debugging.

As always, you should test this on a development server and not on your live site.

@r-a-y I’ll give it a shot, however, there are others posting here to the forums with the same issue as me — so it *can* be duplicated.

@k12onos – The .zip download for BP 1.5.7 can be found here:
https://downloads.wordpress.org/plugin/buddypress.1.5.7.zip

Do not install this on top of BP 1.6. Please try duplicating your problem on a fresh install.

On my local testing on both BP 1.5.7 and BP 1.6, I was able to duplicate your problem. But I believe, the intention was that you shouldn’t nest a component page within a component page and you should follow the method I suggested by creating a “dummy page” as you say.

Let me know.

@rodtrent – I am unable to duplicate your problem. If you have a backup, I suggest reverting back to that and retry your upgrade by following these instructions:

Upgrading to 1.6