webdevstudios

Michael Beckwith

pluginize

Brian Messenlehner

Prevent users and bots from accessing the BuddyPress or bbPress areas of your website(s) until they are approved.
This BuddyPress extension allows you to enable user moderation for new members, as well as help create a private network for your users. If moderation is enabled, any new members will be denied access to your BuddyPress and bbPress areas on your site, with the exception of their own user profile. They will be allowed to edit and configure that much. They will also not be listed in the members lists on the frontend until approved. Custom messages are available so you can tailor them to the tone of your website and community. When an admin approves or denies a user, email notifications will be sent to let them know of the decision.
Requires BuddyPress version 1.7 or higher and bbPress 2.0 or higher.
<h3>General Data Protection Regulation</h3>
BuddyPress Registration Options temporarily stores user IP addresses as user meta to help validate and vet pending users. Saved IP values are deleted upon both approval and denial of pending user. No other personal data is recorded.

Registration Options for BuddyPress

Moderate new BuddyPress members and fight BuddyPress spam.

Saurabh

francescolaffi

<h4>LATEST VERSION REQUIRE PHP 5.3+</h4>
Site admins can already edit or delete every content in a BP community, but 
analyzing every content posted could be a crazy/impossible work in big communities. 
This plugin use crowdsourcing to help site admins finding contents to moderate.
It adds links/buttons to flag inappropriate user generated content in the site, 
so members can easily flag contents as inappropriate. Admins can then see all the 
reported contents in an organized table in the wp backend, order/filter them and 
take actions (ignore, delete, mark/unmark the content author as spammer, …).
Another table show members, how many posts from them have been reported/moderated, 
how many posts have they reported and moderated from admin. Here find bad/good 
members and take action on them.
Note on private messages: 
* private message sender: reporting this will flag the sender, not the thread, but the admin is not able to see the messages, effective against bulk spammer 
* private message: in this case a sender is reported in a specific thread, the admin can see the messages, more useful for moderation (eg k-12 communities) 
the latter is a bit hackish and could be less solid on future bp upgrades, the first one is based on apis that should be more stable
Use <a href="https://wordpress.org/support/plugin/bp-moderation" rel="ugc">support forum on wordpress.org</a> 
for support and discussion.
The default style uses one icon from http://www.famfamfam.com/lab/icons/silk/ 
(cc-by-2.5) and one from http://damieng.com/creative/icons/silk-companion-1-icons 
(cc-by-3.0), so if you use default style give credit to them somewhere in your site.
<h3>Moderator panel</h3>
You can access the backend panel from the “BP Moderation” link in your 
Wordpress admin menu.
There are three tabs on the top: “contents”, “users”, “settings”.
<h4>Contents view</h4>
In this view you can see the reported contents.
Use the custom query filter/order contents.
The contents table has three columns:
<ol>
<li>info on the content author</li>
<li>info on the content itself ( and link to take actions on it on mouseover )</li>
<li>info on the flags on this content</li>
</ol>
<h4>Users view</h4>
In this view you can see users that reported a content or users whom contents 
have been reported.
Use the custom query filter/order contents.
The contents table has three columns:
<ol>
<li>info on the user itself</li>
<li>info on the contents generated by the user and flagged by others</li>
<li>info on the contents generated by others and flagged by the user</li>
</ol>
<h4>Hotkeys</h4>
You can enable and disable hotkeys with the link displayed under contents and users tables.
I tried to make hotkeys similar wordpress comments table hotkeys, if you never 
used them, give a look to <a href="https://codex.wordpress.org/Keyboard_Shortcuts" rel="nofollow ugc">this codex page</a>.
When a row is selected with hotkeys the possible keys will be shown next to the actions links.
Hotkeys in both tables:
<ul>
<li>j/k: moves down/up</li>
<li>x: check current row for bulk actions</li>
<li>shift+x: invert row selection</li>
<li>c: direct contact selected user (or selected content author)</li>
<li>s/u: mark as spammer selected user (or selected content author) / unmark him</li>
</ul>
Only in contents table:
<ul>
<li>v: view content</li>
<li>a: approve (ignore)</li>
<li>e: edit</li>
<li>m: mark as moderated</li>
<li>d: delete</li>
</ul>
Only in user table:
<ul>
<li>b: see the contents generated by the selected user and flagged by others in the content view</li>
<li>g: see the contents generated by others and flagged by the selected user in the content view</li>
</ul>
Bulk hotkeys:
Some keys can be triggered on all selected rows if pressed with shift. 
Those keys are s,u,a,m,d.
<h3>Integration guide</h3>
= Introduction = 
This guide aims to explain how integrate bp-moderation with custom content types, 
wp/bp core content types are already covered by the plugin, but you can write your 
own custom content type definitions also for them.
It’s important to understand how bp-moderation differentiate/recognize contents: 
each content have to be identified by an internal content type slug (you choose 
it in your custom content type definition) and one or two bigint ids.
Decide a convention with 2 ids for your content type, is not something you can change 
later. You have to call bp-moderation methods using always the same convention and 
bp-moderation will use the same one when referring to your contents. 
If your contents are tied with the activity stream you already have chosen a convention 
for primary and secondary ids, using the same convention you use with activities 
will make things easier. If you only have one id use 0 for the secondary id.
<h4>Register a content type</h4>
The main entry point in bp-moderation is bpModeration::register_content_type(), it 
allows you to register a content type and has to be called at every page load.
You’ll need to provide:
<ul>
<li>a slug: used to differentiate between content types (alfanumeric and underscore only)</li>
<li>a label: human readable name of the content type (used in backend)</li>
<li>some callbacks: called by bp-moderation to request information/operations on your contents</li>
<li>activity types: the activity types that your content are posted on the activity stream with (if any)</li>
</ul>
<h4>Code sample</h4>
<pre><code>examples/bpMod_ContentType_BlogPostExample.php is a code sample that shows
</code></pre>
how to integrate content types with bp-moderation taking blog posts as an example, 
you can also modify and adapt it to your content type.
Other informations are in the doc of <code>bpModeration::register_content_type()</code> and 
 bpModFrontend::get_link(), those are most likely the only two bp-moderation 
methods you need to use.
All core content types are in bpModDefaultContentTypes.php, but they are hardcoded 
for speed reasons, so don’t use them as an example.
<h4>Advanced integration with activities</h4>
If you use the same primary and secondary id convention for activities and bp-moderation 
you only have to tell the activity types of your content when registering, 
bp-moderation is already hooked in the activity loop and will print the links 
for your contents too.
Instead if some reason you cat use the same convention or you want to customize 
the activity loop flag button, you can use the filter
<pre><code> bp_moderation_activity_loop_link_args_{the activity type}
</code></pre>
where <code>{the activity type}</code> is the activity type you’d like to filter. 
Look in <code>bpModFrontend::activity_loop_link()</code> to see what to filter.
<h4>Contents generated by non members</h4>
It’s possible to have contents generated by not members (e.g. blog comments). 
If you have to provide a user id to bp-moderation give 0 for it, but you’ll also 
need to filter author information for displaying them in backend table. Use the filter
<pre><code> bp_moderation_author_details_for_{slug used in content type registration}
</code></pre>
to add missing info, look in <code>bpModBackend::author_details()</code> to see info needed.
<h4>OK I coded my custom content type, and now?</h4>
If you have coded a custom content type and you think that could be widely useful, 
contact me and it could easily get included in the bp-moderation plugin.
If you integrated your plugin and you prefer to keep the custom content type in 
your plugin it’s fine, I guess is more convenient and you can update it together 
with your plugin. 
Remember to check if bp-moderation is active before including unnecessary code 
or calling non-existing functions: safest way is to use the action <code>bp_moderation_init</code> 
for including/registering it.
If none of the above this is the easier way to get a custom content type loaded:
<ul>
<li>place your custom content type php file in <code>wp-content/plugins/bp-moderation-content-types/</code></li>
<li>copy this line in wp-config.php <code>define('BPMOD_LOAD_CUSTOM_CONTENT_TYPES', true);</code></li>
</ul>
<h4>Possible future content type system features</h4>
<ul>
<li>differentiate between trash, untrash and delete, or maybe custom actions on content</li>
<li>methods to be called when a content is edited/trashed/untrashed/deleted so bp-moderation 
can display also what happen outside of it</li>
</ul>

BuddyPress Moderation

Adds links/buttons to flag inappropriate content and gives a convenient way to moderators to view reports and take actions.

Registration Options for BuddyPress vs BuddyPress Moderation