BuddyPress.org

Hi Zoe-

My memory is that users need to have usermeta with the key last_activity and a value like 2015-06-16 13:29:04 to reliably appear in the members directory. You can “repair” this value once the users are imported by visiting (from wp-admin) Tools > BuddyPress then select Repair user "last activity" data. In fact, it probably wouldn’t hurt to run all of those repair tools one at a time since you’ve got a bunch of untracked users.

Read here for a posible solution:
https://buddypress.org/support/topic/disable-html-in-activity-updates/#post-130454

@danbp
Thanks for your suggestion Dan.
I already tried that. There are two problems with that snippent. The first being that the is_bbpress() is returning false when i access bbpress forums in a buddypress group (theme: firmasite). Thats easy to solve through eliminating that check.
The second problem is that currently the @mentions system isn’t working for the visual tab in tinyMCE, it works only for the text tab. Also discussed briefly between Paul Gibbs and Unsal Korkmaz here: https://buddypress.org/support/topic/buddypress-2-1-patsy/ (see comments)

One of the requirements for our platform is that users can use those fancy buttons in the visual tab, but having the mentions autocomplete only in the text tab is a little bit ..you know…unexpected for users 😉
Thus i hoped i can somehow manage to reproduce the approach of OakCreative, but I havent been successful.
Maybe also updating the at.js is a way to go, but the jump from the used version (0.5.2) to the current (1.3.0) seems to be to big to work just with replacing the script.
So this is my current knowledge about this topic. Does anyone know how to proceed? Or should i create a ticket for this, so that the devs can have a look into this in future releases? I havent found any ticket dealing with exactly this.

Hello All,

I am also facing the same problem with bp_verify_nonce_request() function.

It proper works on my Localhost but on my live server its not working properly

In File : bp-members-screen.php file
} elseif ( isset( $_POST[‘signup_submit’] ) && bp_verify_nonce_request( ‘bp_new_signup’ ) ) {

this will not work.. but if i will replace the above code with the below code then it will work

Below code will work properly
} elseif ( isset( $_POST[‘signup_submit’] ) || bp_verify_nonce_request( ‘bp_new_signup’ ) ) {

I know that if i will make changes in Buddypress core files then after update my changes will be lost.

Is any Hook are available so that i can use in my functions.php file.
Please help me someone. Its urgent and i want to complete my project as soon as possible.

Thanks

@oliver_rub,

to get @mention in bbpress topics, try this snippet
https://buddypress.org/support/topic/mention-autolink-to-profile/#post-237202

@drraven0

read here: https://buddypress.org/support/topic/groups-function-is-broken/

Yes. You can use bp_parse_args() for that. See the Using bp_parse_args() to filter BuddyPress template loops article for more info.

I can view anyones messages when logged out.

And you’re definitely talking about what BuddyPress refers to as private messages?

Can you try again after disabling all plugins, reverting to TwentyFifteen and removing all custom code? If you still get to see private messages when logged out then that shouldn’t be happening.

I can view anyones messages when logged out. If I log in I think it shows me my own messages, not sure, the main issue is that someone could easily harvest every single message from a buddypress site. Users are not tech savy and will presume that correspondence is relatively secure so there may be sensitive data stored. Or at worst it would give enough information for an attacker to social engineer the additional data they need.

With standard buddypress (no modifications) you can freely view anyone’s messages without even logging in

That shouldn’t be the case for all users. Only users with admin capabilities should be able to do that. Are you able to see people’s private messages when logged in as a subscriber? If so, that’s a bug

With standard buddypress (no modifications) you can freely view anyone’s messages without even logging in. Personally I think that is not very good security/privacy, whatever you want to call it.

I made a ticket as I don’t think that “private messages” should be publicly viewable
(https://buddypress.trac.wordpress.org/ticket/6504#ticket)

What privacy/security checks would you recommend for people who don’t want users private data publicly viewable?

@henrywright How would you do the security check? If I follow current way buddypress does things with loading the template part for the tab any logged out user can just modify the javascript and get into any profile page they like. It’s first time I’ve done this so appreciate the advice.

what harm could come from a visit to a simple profile tab?

You could see hidden data that user did not want displayed. I believe if you hold data and say it is private then you should attempt to secure it. You could also view their messages and private groups.

The thing I am struggling to understand is how buddypress functions work on the post request. I wrote some test code and data is correctly populated from displayed user. Does buddypress read a referrer value somewhere on every ajax post?

May not be the best way, but try:

function add_group_tab() {

	if ( class_exists( 'BP_Group_Extension' ) ) :
	
		class members_nav_tab_in_group extends BP_Group_Extension {
			
			function __construct() {
			
				if( bp_is_group_single() ) {
					
					$bp = buddypress();
					
					$group_id = $bp->groups->current_group->id;
					
					if( $group_id == 1 ) {
					
						$args = array(
						'slug'              => '../../members',
						'name'              => 'Members Directory',
						'nav_item_position' => 105,
						);
						
						parent::init( $args );
					}
				}
			}
		}
	
	bp_register_group_extension( 'members_nav_tab_in_group' );
	
	endif;

}
add_action( 'bp_loaded', 'add_group_tab' );

The following active BuddyPress Components do not have associated WordPress Pages: Activate, Register. Repair

Those pages are not created automatically. When you get this error message, you have to create the pages manually first.

Go back to bp settings > pages tab and allocate the new pages to the respective component. Save.

You have also to set pretty permalinks to something other thant “by default”. Save.

Now BP has his page assigned and should work.

About the missing button.
Clear your browser cache.
If you use a cache plugin, clear it.
Go to wp-config.php and activate debug mode at the end of the file.

Deactivate all plugins except BP and activate one of WP’s theme (2015, 2014 or 2013…)

See if you get some error message and correct the errors (if exist).

If after tracking/repairing errors, the button is still not showing, deactivate buddypress, delete it and upload a fresh copy of BuddyPress to your site. Sometimes files can be corrupted and need to be replaced. No worry, this will not affect any data in your DB.

If still nothing, check that your host plan has the required php version to be used with WP and BP: at least 5.2.4

Hi @manakio2k,

you could try to just modify the template to get alphabetical as first sort option, instead of the default Last active.

Create a child-theme first, add a folder called buddypress. In this folder add members folder and in that folder add a copy of index.php which is in bp-templates/bp-legacy/buddypress/members/index.php

Around line 78, change the options order to get this:

<select id="members-order-by">
	<?php if ( bp_is_active( 'xprofile' ) ) : ?>
		<option value="alphabetical"><?php _e( 'Alphabetical', 'buddypress' ); ?></option>
	<?php endif; ?>
		<option value="active"><?php _e( 'Last Active', 'buddypress' ); ?></option>
		<option value="newest"><?php _e( 'Newest Registered', 'buddypress' ); ?></option>

Now, members directory is sorted alphabetically by default.