BuddyPress.org

Apparently ticketed:
https://buddypress.trac.wordpress.org/ticket/7443

We’ll consider a possible solution or ‘hack’ 🙁 to avoid the issue.

Using the buddypress() function avoids the need to declare a global. Try to avoid globals in your code if you can.

I’m not aware of a function. Anyone else here know of one?

You should be able to avoid the global by doing this:

echo buddypress()->bp_nav['foo']['link'];

Try buddypress()->foo->slug where foo is the name of your item. If this doesn’t work then “foo” may need to be a component.

This has nothing to do with BuddyPress, but it has to do with adding HTTPS support to your WordPress website.

You have to either pay to get a SSL certificate or use the Let’s Encrypt service to get a free SSL certificate:
https://letsencrypt.org/

Then, configure WordPress to use SSL and this issue should be fixed.

@anthonylawton

Create a plugin with this. But, if you use BuddyPress Honeypot, this plugin not work.

<?php
/*
Plugin Name: Restricted Email Domains
Description: Restricts registration user email addresses to valid domains.
From: http://old.webit.ca/2011/03/limit-user-email-domains-in-buddypress/
Version: 1.0
*/
add_option('limited_email_domains', array('yahoo.com', 'outlook.com', 'hotmail.com', 'gmail.com', 'aol.com', 'mail.com')); 

Sure, you will need to filter out the $arguments variable in my code for the required by you activity_type.

You can put the resulting code into a separate custom plugin or in https://codex.buddypress.org/themes/bp-custom-php/

Not sure what your issue is, but after going through the removal steps, did you deactivate BuddyPress and reactivate it?

If you have an object cache plugin active, you should purge your entire cache after removing the DB options so BP can reinstall its tables properly when you reactivate BuddyPress.

Super easy solution is to do like this:

1) find or create a buddypress/activity/post-form.php file in your theme
2) find in that file a textarea with id="whats-new" and add maxlength="143" to its attributes so it will become something like this:
<textarea class="bp-suggestions" maxlength="143" name="whats-new" id="whats-new" cols="50" rows="10"....
3) save and done.

It will limit globally, though. If only in groups (not modifiying activity directory and profiles) – wrap it in a p_is_group() like this
<textarea class="bp-suggestions" <?php echo bp_is_group() ? 'maxlength="143"' : '';?> name="whats-new" id="whats-new" cols="50" rows="10"....

Team is a BuddyPress group.
League – is the group type, read about it here: https://codex.buddypress.org/developer/group-types/

This might be helpful for you too: https://codex.buddypress.org/add-custom-tab-to-groups-directory/ (leagues as tabs in groups/teams directory).

I migrated from Ning to Buddypress last year roughly following a very old guide. I had to manually tidy up the json exports and it only imported basic user information, posts and groups. We primarily used ning for events and I moved those in to events-manager myself.

It took a lot of trial and error and if you’re not that technical I’d recommend paying someone to carry out the process, I just wouldn’t expect miracles.

I think, you can’t do that easily.

Reason: BuddyPress activated and is working on subsite 1, where all of its tables created. Subsite 2 is completely independent site with even own list of users.

To fix this: you will need to write quite heavy bridge, that will query the subsite 1 and asks each time whether user has there what you need on subsite 2.

Your task is a compilation of several steps.

1) You need to add a custom field to BuddyPress registration form
See this https://buddypress.org/support/topic/how-to-display-a-custom-field/ or similar (just google).

2) You need to get the list of users by a member type to display in a <select> field created in 1).
See https://codex.buddypress.org/developer/member-types/ and its “Querying by member type” section.

3) In 1) you created and it’s also written how to store that data, I suggest using usermeta (update_user_meta()). You should store not the teachers names, but their ids in metas.

4) Now you need to display this info in user profile.
Investigate wp-content/plugins/buddypress/src/bp-templates/bp-legacy/buddypress/members/single/profile/profile-loop.php file, you will see there several hooks that may be useful for you. There you will just echo what you need.
Example: get_user_by('id', get_user_meta(bp_displayed_user_id(), 'teacher_id'))->display_name; or similar using BuddyPress functions.

Currently there is no such plugin. Introducing this feature is quite heavy for the server, so it’s more like a custom solution, ideally with websockets.

We use heartbeat functionality, that gives ability to show a notification about new activity records, but there are no plans to actually update old records due to lots of technical issues and time availability (all BuddyPress core devs are volunteers).

You can check this plugin: https://premium.wpmudev.org/project/ning-to-buddypress-user-importer/

But before buying it’s better to contact their support and ask about compatibility.

It’s too late for answering this question but will help someone else 🙂

just put this code on your /plugins/buddypress/bp-activity/bp-activity-template.php file within this function bp_get_activity_action()

if($activity_arr->type == 'rtmedia_comment_activity'){
			global $wpdb;
			$query = "SELECT activity_id FROM ".$wpdb->prefix."rt_rtm_media WHERE id='".$activity_arr->item_id."'";
			$activity_id = $wpdb->get_var( $wpdb->prepare($query));
			$activity = bp_activity_get_specific( array( 'activity_ids' => $activity_id ) );
			$activity = $activity['activities'][0];
			$action .= $activity->content;
			
		}

Hope this help

You should activate “Site Tracking” from Settings/Buddypress/. For me, it is working fine.