BuddyPress.org

@xyhavoc

Just a quick follow up to inform you, i’ve read your discussion with @boonebgorges on 5603.
I’ve attached an alternative patch to the ticket, it would be great if you could test it.

Thanks again for your feedback.

@ronia,

Here is the plugin that does that.

https://wordpress.org/plugins/bp-you-are-blocked/

Naijaping

@noizeburger Thank you for sharing this – it’s helped me out greatly.

I might just add to anyone else who’s going to implement this as I’d spent about four hours trying to figure out why it wouldn’t work for me initially.

add_action( 'bp_core_signup_user', 'custom_bp_core_signup_user', 10, 1);

The number 10 states at what point the function should be called. This should work in most instances but I am using a theme with additional buddypress functions built in.

I had to set this to a higher level, meaning it gets executed later on in the process. At least I think that’s right. Anyhow, once I’d changed mine to

add_action( 'bp_core_signup_user', 'custom_bp_core_signup_user', 13, 1);

It worked fine!

It’s worth reading this.

https://codex.wordpress.org/Function_Reference/add_action

Thanks again

Did you ever resolve this? I’ve just activated BP in wordpress site using the weaver II them and am having a similar issue. Everything seems to work but I never see an avatar and continually get this error message: Notice: Undefined property: BP_Groups_Group::$avatar_thumb in /homepages/24/d463872728/htdocs/APP/wp-content/plugins/buddypress/bp-groups/bp-groups-template.php on line 526. I’ve looked at the code and it’s not obvious to me what this means.

Hey @mcpeanut

Hopefully your new server is working well for you! Just thought I’d give an update on how mine is going.

I went for the managed option to try to save a little time but that was a mistake. I should have opted for the root server because 1and1 refuse to make any changes to the config of the managed servers. I should have guessed that before I signed up. An example is Fast CGI isn’t enabled. And their support team has confirmed the advanced settings panel for the managed option doesn’t work. That said, and aside from bad support (the dedicated server support team aren’t interested in helping if you have a non-trivial problem) the server seems to be quite reliable, and fast. Checking via Pingdom Tools, a basic WordPress page load takes ~ 0.2 seconds. Oh and one last thing, their £3.99 per month SSL certificates (minimum 12 month contract) can’t be migrated if you decide to upgrade your package. My mini-review might sound very negative but I’m persevering with them because the hardware is good for the price (as you already know). Hope this helps you!

older downloads:
https://wordpress.org/plugins/buddypress/developers/

open a ticket:
https://buddypress.trac.wordpress.org/

Please see the ticket that r-a-y referenced.

You can patch the file using the changeset:
https://buddypress.trac.wordpress.org/changeset/8305

Or wait for the release of BP.2.0.1

Hi @localiseorg

Socialise (sitewide activity assigned to this)
– Members (members directory assigned to this)
– Groups (groups directory assigned to this)
– Forums (bbPress forum root assigned to this)

Have you tried using a wp_nav_menu instead ?

I think, if i was in your situation, i’d make a wp_nav_menu with your different pages.. It could be “home”, “blog”, “socialise” for instance. And from the wp_nav_menu WordPress UI, i’d attach the Members/Groups and forums as submenus of Socialise.

Then concerning the Socialise title that is “Sitewide Activity”, i’ll begin to edit the activity page changing the title from Activity to Socialise and use a little code like the following:

function change_activity_directory_title() {
	buddypress()->activity->directory_title = buddypress()->pages->activity->title;
}
add_action( 'bp_activity_setup_globals', 'change_activity_directory_title' );

This sort of functionality is something that’s definitely required for BP – there’s no way an admin can go round reading everything on a busy site, abuse monitoring has to be crowdsourced to the members.

The plugin I’ve been testing, which was last updated in 2013, is this one: https://wordpress.org/plugins/bp-moderation/

Interestingly it covers just about everything – from members, private messages & their senders, statuses, activity comments, topics, forums, groups, posts, pages, blog comments, and probably a whole bunch of other things. I have a hunch they are hard-coded though.

It works to an extent, but glitches I’ve found so far include:

* Setting to define what text appears on the ‘Flag’ links don’t get applied to all links
* Flag link text for things like posts (and possibly pages) starts appearing in excerpts
* It’s using images rather than FontAwesome / Fontello via CSS = ugly and slow
* The admin menu icon is broken somewhat (looks ugly) but that’s minor thing

IMHO if the UI could be cleaned up, images replaced with icon fonts, and somewhat improved control over link text implemented, this plugin would be pretty much there and would cover just about all aspects of WP, BP and (with some extra coding) probably even bbPress.

Unfortunately I’m pants when it comes to PHP so can’t help with this task 🙁

That is an old version of BP.

You could try changing the apply_filters to
return apply_filters( 'bp_core_get_users', BP_Core_User::get_users( $type, $per_page, $page, $user_id, $include, $search_terms, $populate_extras ), $params );

That might get you past the fatal error.
You should update BP, but you cannot jump all the way to BP 2.0.
You’ll have to step up thru each version.
You can get older versions here:
https://wordpress.org/plugins/buddypress/developers/

No i thought you were using a specific theme for the administration of WordPress. Because i thought it was a css issue or something like it.

I think i’ll try to see if the button is in the html source of the page using a search for ‘bp-admin-component-submit’. If you are using the Chrome Browser, you can for instance launch the inspector and once done, and on the tab “Element” click on ctrl + F to display the search input.

If you are using another browser simply display the source in a text editor for instance and do the search from there.

I think you’ll find the button meaning it’s a css/browser issue.

If not it may means there’s a “fatal” that avoids the html to be completely output. In this case you can set the WP_DEBUG constant to true in your wp-config.php file, check what’s going wrong in this part and eventually try to fix it. Once done, don’t forget to set back the WP_DEBUG constant to false.