BuddyPress.org

@matt55 – The php errors still continued so it was not due to using Server Protocol. I am not exactly sure what action the spammers are doing in combination with the .htaccess code that is generating the php errors, but for now I just suppressed them by adding an @ symbol infront of strstr below until I can analyze this some more. /buddypress/bp-core/bp-core-template.php code line 864.

if ( !empty( $page_template ) && @strstr( strtolower( $page_template ), strtolower( $component ) ) ) {

Yep, I downloaded it from github. I have a bunch of customized security things going on so most likely one of the other security measures I have in place is causing the issue/problem. I will figure this out tomorrow when I have some more spare time.

Lately the Spam Registrations were getting way out of control – 1 per minute – so I had to get something in place quick. Yuck.

@aitpro
Are you using the plugin on github?
https://github.com/bphelp/bp-spam-killer
Or Are you using the code on pastebin which I could not get valid users registered either.
http://pastebin.com/kzxCqSb8
On my test server the github plugin allows registration for valid users but I am not really sure how effective this method would be at preventing spam registrations. Any feedback is appreciated!

@bp-help – I tested your plugin and for whatever reason on my site it prevented good registrations. I will isolate exactly why that is on my particular site.

@matt55 – I did some more research and built on your .htaccess code. A php error was occurring due to using Server Protocol so per jdMorgan “the htaccess Master” 😉 the better condition check is The Request.

Special thanks to jdMorgan a true htaccess Master

# BuddyPress Anti-Spam Registration
RewriteCond %{REQUEST_METHOD} ^POST
# only match the register page URI
RewriteCond %{REQUEST_URI} ^/register/$
# domain referer is better than IP - allows for subdomains
RewriteCond %{HTTP_REFERER} !^.*ait-pro.com.* [OR]
# Blank or single hyphen user-agent spoofers or curl
RewriteCond %{HTTP_USER_AGENT} ^(|-?|curl)$ [OR]
# HTTP request header
RewriteCond %{THE_REQUEST} HTTP/1\.0$
RewriteRule ^(.*)$ /spam-prevention [R=301,L]

i’d buy that for a dollar!

😛

@mattt55
Per your request I removed your credit for the plugin.

@mattt55
Well I gave you credit because you was my source, if you ever come across the original author then I will credit them. As for the jQuery method see:
http://pastebin.com/kzxCqSb8
I added a _inc file to the plugin that contained the my.js file. See line 33 as to how I implemented it. Really not sure what I did wrong so have a look and see if you notice any errors.

@mattt55
Hi, I used your 3rd method registration honeypot to create a small plugin. I don’t really know how to test its effectiveness but here is a link for anyone that is adventurous and would like to give feedback to that effect:
https://github.com/bphelp/bp-spam-killer
Credit goes to @mattt55 for the code and idea.
I could not get the 4th method using jQuery to work. It always sends every user to the spam-prevention page. If you can give more detail as to how to get this working I would like to use both methods in one plugin for better spam registration prevention. Thanks!

@mattt55
Good info, thank you for sharing!

those seem like some great tips especially the last two thanks for sharing!

you should be fine, there are a few differences in the way things work, namely network user registration as opposed to single site registration (users are not automatically added to the root site), making sure your plugins are multisite ready/compatible. All in all you should not have any difficulty unless your mods are things that are relating to network functions (not very likely i don’t think). Do be prepared for the spammers and sploggers to step up their game i implemented wangguard at the same time i switched our site from single to multi.

@hnla
Well said Hugo! It also seems to me that if it was checked by default it would make it even easier for spam bots to compromise a site.

You may have already checked but have you looked in your spam folder? Could be in there.

Thanks @bphelp.

Closing this thread and any further that are re-opened @placementmantra

@placementmantra You have already been asked by @hnla to stop opening old threads. Not to be rude but isn’t it ironic that your asking for help with spam yet your kinda being spammy yourself. Anyway try this plugin, it is in beta but it may work for you:
http://geek.ryanhellyer.net/products/spam-destroyer/
Download the beta version that has support for BP and bbPress.

I am daily getting very much spams on http://placementmantra.net/
no idea how.even tried plugin no use

I am daily getting very much spams on http://placementmantra.net/
no idea how.even tried plugin no use

@placementmantra Please stop posting this repeated post immediately. You have now posted approx twelve times to old ‘Spam’ threads in as many minutes virtually. Open A new post or search and ‘Read’ some for methods of dealing with spam issues.

Now closing this old thread as a read only.