BuddyPress.org

You could probably use the inbuilt WordPress editor wp_editor() with the message textarea. See here for more info: https://codex.wordpress.org/Function_Reference/wp_editor

https://wordpress.org/plugins/wordpress-ecommerce/ aka MarketPress. You would need multisite BP and this plugin works fine with that.

<!– SEO Ultimate (http://www.seodesignsolutions.com/wordpress-seo/) –>

For that to be a comment, a couple of hyphens are missing. Maybe it should be this?

<!–- SEO Ultimate (http://www.seodesignsolutions.com/wordpress-seo/) –->

You could feed back to the developers of the plugin and maybe they’ll issue an update: https://wordpress.org/support/plugin/seo-ultimate

Hi @moonhopper

1/ Did you make a backup of your database before upgrading to BuddyPress 2.0 and creating the network ?
2/ Is it a live website or a dev one ?
3/ Can you check into the usermeta table of your site if for the problematic users you have a meta_key ‘activation_key’ with a meta value or not ? If so in the users table are these users having a user_status set to 0 ?
4/ What is the name of the theme ? Is it available on WordPress repository ?

Two plugins for blocking users. Agree that if flagging/reporting content it would be nice to have option to block the user at same time.

BuddyBlock

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

@jconti – probably best as a separate plugin rather than bundling too much in to WangGuard.

A modernised version of https://wordpress.org/plugins/bp-moderation/ would be ideal, as that plugin already does most of what’s required – it just needs lots of cleanup.

Admin settings interface:

Choose which content types should get a report/flag link (including things like status updates, comments, groups, forums, members, posts, articles, etc).

Customise link text, eg. “Report %username%” or “Flag %contenttype%” etc.

Decide how many reports something needs before an automatic response is triggered. Eg. if 5 people have flagged a comment as bad, person who made that comment should get a customised message and the message should optionally be forwarded to an admin.

The message I’ve set up in BP Moderation plugin looks like this:

%AUTHORNAME%,

Several users reported your content as inappropriate:
%CONTENTURL%.

A community moderator has been notified and will review the content. If it is found to be in violation of our site terms of use, your account will be removed.

%SITENAME%

Front-end UI:

Make HTML as consistent as possible, but compatible with the UI found for the specific type of content.

Ensure there is a specific class on all flag/report links, eg. class=”abuse-button”

Ensure there is a content type specific class on each flag link, eg. class=”abuse-type-comment”

Ensure there is a state specific class on all links, eg: class=”not-flagged” or class=”is-flagged” as applicable.

Use AJAX when user flags/unflags something to avoid page refresh.

Management Interface:

There should perhaps be two management interfaces, one for site admins in the WP backend, and one for forum/group mods in the front-end.

In the backend, see BP Moderation plugin for an example.

In the front-end, it would be nice if say a group admin/moderator would get messages about problem users in their group and be able to deal with it themselves (via front-end UI, I don’t want normal users of my site going in to WP backend). This would reduce workload of WP site admins.

Spam integration:

I assume this is something native to WP but it might be from a plugin, not sure. Anyway, in admin area when you go in to Comments or Topics, etc., and hover over content items you get a spam link in the links that appear:

It would be nice if when the auto-response message is triggered (as mentioned earlier – for example after 5 people report something) it could be marked as spam. When marked as spam, content is hidden from the front-end and moved to a ‘spam’ folder on the backend. This would mean if several people report something it is temporarily hidden while an admin looks in to it – if the admin thinks it’s ok they can un-spam it, otherwise they can delete it.

I have no idea which content types / reply types support this spam thing. It would also be worth checking with whoever implemented the spam thing to see what their future plans are?

Other Notes:

If the new plugin could provide hooks so that other plugins such as WangGuard could hook in to it, that would be ideal. For example, if WangGuard sees a blacklisted word in a comment it could automatically flag it or something like that.

It would be useful if there was a record kept of how many times a user’s content has been flagged enough times to trigger auto-responses. This would enable admins to spot repeat-offenders who are regularly annoying other end-users and factor that in to any subsequent decision making (eg. should I ban that user?).

It would be nice if there was a way to auto-suspend a member account if lots of their content is getting reported/flagged. This ties in with the count thing mentioned above. So if they’ve spammed groups and forums with spammy adverts, etc., and as a result other members have reported those things several times, the offending user would be auto-suspended if they have more than say 3 items moved to spam at any given time.

@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/