BuddyPress.org

I’m also on

WordPress 3.6
BuddyPress 1.8

And I get:

http://[website]/members/%5Buser%5D/profile/edit/group/1/

And get a 404

I get the same issue when I install Current Version of Buddy Press 1.8 on a custom domain.

think you covered that in your other thread!

@intimez I’m not using that plugin, but I did have the same issue.
I hope you’ve fixed yours by now, but if not, here’s what I did:

In the bp-activity-template.php file, edit this function

function bp_get_activity_comment_name() {
		global $activities_template;

		if ( isset( $activities_template->activity->current_comment->user_nicename ) )
			$name = apply_filters( 'bp_acomment_name', $activities_template->activity->current_comment->user_nicename, $activities_template->activity->current_comment );  // backward compatibility
		else
			$name = $activities_template->activity->current_comment->display_name;

		return apply_filters( 'bp_activity_comment_name', $name );
	}

The last line is all you need to change. Basically, you’re changing “user_fullname” to “user_nicename”.
I know it’s not ideal to edit bp files, but this is currently the only way I know how to display usernames in comments. Hope this helps someone!

it’s more about how many people will be using your site at any given time if you have buddypress and especially if your theme is displaying buddypress info on most of your pages then you will almost certainly need vps to be happy with your load times.

So a member has to make a separate donation to see each new message trail?

This will require the hiring of a buddypress developer to create a custom plugin.
You can contact me via my profile info.

@whiteeagle1985 check out http://buddydev.com/buddypress/introducing-buddyblog-allow-users-to-blog-from-their-buddypress-profile/

@barronlau
– localhost is XAMPP, WAMP, MAMP?
– As for avatar in localhost, choose something other than the default mystery man for those without Gravatars.
– If you installed BP subsite, did you follow instructions at https://codex.buddypress.org/user/install-buddypress-on-a-secondary-blog/ ?
– I suggest that you test BP install first using BP Default or Twenty Twelve/Thirteen theme.

The problem is, in essence, this: You are filtering for member type/role at the template level, *after* the query has already taken place. So: you run bp_has_members(). It returns 10 users that match the current params, which include the current page, the per_page number, and the dropdown filter (last active, alphabetical, etc). Then, inside of your template loop, you are only displaying a subset of those ten returned members – ie, those that match your s2member role.

In order to make a custom directory *and* have your pagination work, you’ll need to modify the query *before* it happens. One relatively simple way to do this is to pass an include parameter to bp_has_members(), which would limit the query to users that meet your s2member criteria.

Because we’re talking about custom user roles as assigned by s2member (and because user roles are stored in a way by WP that doesn’t allow this kind of query to be very efficient), this is going to be pretty tricky. This is totally untested, and probably not very fast at very large scale, but you could try something like the following:

<?php 
global $wpdb;
$level3_user_ids = $wpdb->get_col( "SELECT user_id FROM {$wpdb->usermeta} WHERE meta_key = 'wp_capabilities' AND meta_value LIKE '%s2member_level3%'" );
$level3_user_ids_param = implode( ',', $level3_user_ids );

if ( bp_has_members( bp_ajax_querystring( 'members' ) . '&page_arg=bapage&per_page=10&include=' . $level3_user_ids_param ) ) : ?>

Then you will *not* need to do the level3 check inside the loop, because the 10 items returned will already be limited properly.

Like I said, this is off the top of my head and may not work without further modification. You may have to do some more experimentation to get an accurate whitelist of user ids for each directory type. But, no matter how you do it, the above example should show you a good technique for limiting the bp_has_members() query to a subset of all users (which is the BuddyPress-related part of this puzzle – the other problem is related to s2member).

@parmkals
As @ubernaut stated I would FTP BuddyPress because if you do not have access to the php.ini then you can not change it and it may hang when downloading and installing BP. If that is the case then just download BP to your hard drive extract it and FTP it to: your-site/wp-content/plugins on your server. You will need the credentials from the server to do this and that is something only you can acquire. I supplied a link that will hopefully help you get started if your not familiar with this process. Good luck!
https://codex.wordpress.org/Using_FileZilla

@mercime

@faramarz thanks for posting the error, see https://bbpress.org/forums/topic/fatal-error-unable-to-create-forum-from-buddypress-group/#post-135487

EDIT – Trac Ticket at https://bbpress.trac.wordpress.org/ticket/2374

However as this post suggests and others this issue is perhaps not bbPress specific but BP and needs a trac entry on bp rather than bbPress.

https://buddypress.org/support/topic/error-when-using-it-for-groups/

you can download the zip file extract it then upload via ftp to your plugins folder.

@zanora

https://wordpress.org/plugins/debug-bar-bbpress/ will show you what bbpress templates are used.

This works as an add-on to https://wordpress.org/plugins/debug-bar/ which is in itself useful when editing stuff…

@megainfo Those are historical groups before the changeover to bbPress, then groups were automagically created from WP repo submissions as long as something or other was in the plugin header, but since that change those groups no longer function as support avenues.

@hnla,I dont remember from where i was past this part of text, but sure from an old buddypress readme.txt plugin and i was used since long time as template file for all my plugins.
You can check the readme.txt for all my others plugins too.
https://github.com/dzmounir

I want ask you a question , why some old plugins have a forum support in the buddypress forum
i mean ?

Plugin Forums

@megainfo do correct me if I’m wrong but is this not another re-hash of an older plugin?

You have this line in the readme.txt https://buddypress.org/community/groups/buddypress-wall/forum/
Why it points nowhere, why are you saying the WP support forum for plugin is really checked and to post here with support issues? BP support does not offer support for third party plugins the correct place to offer/deal with support is on the provided WP plugin support.

All we can advise is to change to twentytwelve theme if issue corrects itself as it will then it’s a theme issue and it will be down to the author to provide some solution really. BP theme compatibility is a simple process requiring just that a regular WP conforming page.php exists.