BuddyPress.org

Well! “SI CAPTCHA Anti-Spam” not really works. Spammers registration keep coming. The number of a day has been reduced but still can’t stop them. I assume the spammer bots may smart enough to OCR the words in CAPTCHA or could listen to the audio assist then they could generate a correct input to pass the registration. So I set CAPTCHA to “high” level and uncheck the audio option. The last 24 hours I got 10 spam registers. I wonder if a plug-in can spell check the field input may help eliminate most of these spammers.

Yeah! I believe they are spam accounts. They are keep coming from all over the world. I have just install plugin “SI CAPTCHA Anti-Spam” on all three wpmu web sites. It should stops the spam bots if you are not “human”….lol. Thanks all you guys!

@r-a-y Thanks for that! Getting some errors.

This shows in the admin

Warning: Invalid argument supplied for foreach() in /home/me/public_html/mysite/wp-content/plugins/cubepoints-buddypress-integration/cubepointsBP.php on line 74

This shows on the front end when I go to the activity page

Warning: Invalid argument supplied for foreach() in /home/me/public_html/mysite/wp-content/plugins/cubepoints-buddypress-integration/cubepointsBP.php on line 74

Line 74 is:
foreach ( $bpcpspamlist as $spammer_id ) {

This is what I put in.

http://pastebin.com/5qDXuCvv

@r-a-y This is what I came up with and the echo prints out this “Banned Users: Array” am I even close? lol

function my_bp_update_post_add_cppoints() {
global $bp;
$bpcpspam = array($bpcpspamlist);

$getspamlist = get_option( ‘bp_spammer_cp_bp’ );
$bpcpspamlist = explode(“,”, $getspamlist);

echo(‘Banned Users: ‘ . $bpcpspamlist . “
“);

if ($bp->loggedin_user->id != get_option( ‘bp_spammer_cp_bp’ ) ) {
foreach ($bpcpspam as $bpcpspamlist) {
if( function_exists(‘cp_alterPoints’) ){
cp_alterPoints($bp->loggedin_user->id, get_option(‘bp_update_post_add_cp_bp’) );
cp_log(‘Comment’, $bp->loggedin_user->id, get_option(‘bp_update_post_add_cp_bp’), BuddyPress);
}
}
}
}
add_action(‘bp_activity_posted_update’,’my_bp_update_post_add_cppoints’);

@thekmen @r-a-y

Tried going about this another way. Still not working correctly. Says user id 59 is not a spammer, but that user is marked as so. Any ideas?

I tried to echo it out. Nothing comes out for the user id ..
echo(‘User ID: ‘ . $bp->loggedin_user->id . “n”);

/* *********************** START Spammmer! ********************************* */
global $bp;
// 59 for testing
// if( $bp->loggedin_user->id == get_option(‘bp_spammer_cp_bp’)){

global $current_user;
global $user_id;

if ($userinfo->ID == 59) {

function my_bp_update_post_add_cppoints() {
if( function_exists(‘cp_alterPoints’) && is_user_logged_in() ){
cp_alterPoints(cp_currentUser(), 0 );
cp_log(‘Comment’, cp_currentUser(), 0, BuddyPress);
echo ‘spammer
‘;
echo(‘User ID: ‘ . $user_info->ID . “n”);
}
}
add_action(‘bp_activity_posted_update’,’my_bp_update_post_add_cppoints’);

} else {

// Add Points for a update
function my_bp_update_post_add_cppoints() {
if( function_exists(‘cp_alterPoints’) && is_user_logged_in() ){
cp_alterPoints(cp_currentUser(), get_option(‘bp_update_post_add_cp_bp’) );
cp_log(‘Comment’, cp_currentUser(), get_option(‘bp_update_post_add_cp_bp’), BuddyPress);
echo ‘spam free
‘;
echo(‘User ID: ‘ . $user_info->ID . “n”);
}
}
add_action(‘bp_activity_posted_update’,’my_bp_update_post_add_cppoints’);

}
/* *********************** END Spammmer! ********************************* */

@r-a-y

I tried this as well. Not the desired outcome.

if ( !$no_grav ) {

Went back to this, because I’m sure I am getting closer .. When I test this with an account has an existing avatar, it still gives me points.

// Avatar Anti-Spam
global $bp;
$avatar_dir = ‘avatars’;
$avatar_dir = apply_filters( ‘bp_core_avatar_dir’, $avatar_dir, $object );
$item_id = $bp->displayed_user->id;
$object = ‘user’;

$avatar_folder_url = apply_filters( ‘bp_core_avatar_folder_url’, str_replace( WP_CONTENT_DIR, BP_AVATAR_URL, BP_AVATAR_UPLOAD_PATH ) . ‘/’ . $avatar_dir . ‘/’ . $item_id, $item_id, $object, $avatar_dir );
$avatar_folder_dir = apply_filters( ‘bp_core_avatar_folder_dir’, BP_AVATAR_UPLOAD_PATH . ‘/’ . $avatar_dir . ‘/’ . $item_id, $item_id, $object, $avatar_dir );

if ( file_exists( $avatar_folder_dir ) ) {
// Avatar has been upload so zero points

// ZERO Points for Avatar Upload if they already uploaded at least 1
function my_bp_avatar_add_cppoints() {
if( function_exists(‘cp_alterPoints’) && is_user_logged_in() ){
cp_alterPoints(cp_currentUser(), 0 );
cp_log(‘Avatar Uploaded’, cp_currentUser(), 0, BuddyPress);
echo ‘zero points’;
}
}
add_action(‘xprofile_avatar_uploaded’,’my_bp_avatar_add_cppoints’);

} else {

// Add Points Avatar Upload
function my_bp_avatar_add_cppoints() {
if( function_exists(‘cp_alterPoints’) && is_user_logged_in() ){
//cp_alterPoints(cp_currentUser(), get_option(‘bp_avatar_spam_add_cp_bp’) );
cp_alterPoints(cp_currentUser(), get_option(‘bp_avatar_add_cp_bp’) );
cp_log(‘Avatar Uploaded’, cp_currentUser(), get_option(‘bp_avatar_add_cp_bp’), BuddyPress);
echo ‘add points’;
}
}
add_action(‘xprofile_avatar_uploaded’,’my_bp_avatar_add_cppoints’);

}

My great worry these days is that the dev community is being compelled to fix problems with usability of core BP, as much or more so than extending what’s there.)

And which is one of my concerns too, and is evident in many posts on this site with developers rushing out fixes to usernames for example as is perceived as being a problem highlighted by one person.

What worries me is that moving forward in this manner is not necessarily the best approach to developing a rock solid core app as you have perceived issues being dealt with in a slightly haphazard manner and the setting up or configuring of BP dependent on finding many and various disparate third party snippets of code.

I’m sure Andy&co are focused too an extent on fixing problems but also it may well be a case that ‘Problems’ are not necessarily perceived as problems- part of the reason I thought that this thread was a necessity; to try and flesh out what were considered existing UI/design flaws and provide that as good solid feedback to work from. I note that in the ‘roadmap’ it states that there are periods of consultation? to garner feedback for version features, I would like to see that process in action and to see developers helping guide these future releases; as I agree that it’s now not simply about adding ‘Features’ but far more importantly on providing a core that works and that developers may extend upon.

It feels as though BP is reaching a momentous milestone or crux point in it’s development, and that perhaps the core dev team ought to take a breather, take time out and review what is right and what is wrong and that needs addressing. Foxly made the point well in his ‘ spammers are coming'(sic) thread discussing his suggested approach to tackling the spam issues surrounding BP where he asserts that BP is reaching this crux point where if it wants to grow from simply a “Science project for hobbyist sites” to a fully mature app that can serve business / enterprise it has to tackle certain issues and is why he considers taking some time to tackle this issue he sees with spam is of paramount importance. I would not disagree with Foxly for one moment and what he has reported on thus far on the issue is commendable but I do not think a developer should be tackling this, taking time out from working on hugely useful ‘Feature’ plugins to work on something that – if is agreed to be an issue that must be dealt with – is essentially a core development issue and really ought to be handled by the core development team not by a third party developer (Obviously this is not to say it won’t be as things are in early stages and speculative at this point)

So, yes extending must slow down for a while and issues of a UI / design nature must be thrust to the fore and I would hope there is a means of collating some of the very apposite and useful comments and suggestions that have appeared so far in this thread.