Ok, I didn’t know that. Thanks!
How/where do I get the API key? From here? : http://akismet.com/wordpress/
What should I add to the wp-config.php file?
We have a new BP/Multisite site.
Everday I see new members register and show up in the following sections:
WP-Admin
Activity on the site
But the problem is if you go to site.com/members it only shows the ones that have actually activated their accounts by clicking the link in the email they received after registering new account.
These members who have actually activated their accounts are way less than who have registered and never activated their accounts.
It makes me think that many of the new registrations are coming from spammers who just want to register and spam your site but once they find out that they have to activate their accounts etc then they just don’t bother any more.
I am wondering if it is a good idea to discourage spammers by putting a text note on the account creation page such as:
—————————————————————–
You will get a link in email to activate your account.
—————————————————————–
Currently a message similar to the above shows up after people register for the new account.
But I think it is also a good idea if they know before account creation so that they don’t bother if they are spammers.
Just a thought.
Thanks.
akismet needs to be activated with api key and if you are using it on a multisite network the wp config file needs to be modified in order for it give your entire network blanket protection. akismet is a built in plugin for all wordpress sites.
My WP-admin admin section shows that aksimet plugin is already installed because it asked me to update it with the new version yesterday which I did.
Funny thing is I never installed it.
Q: Does it mean that aksimet is a part of the buddypress install already?
Well I don’t think traceroute will help as it is a logged in vs. logged out problem, but here you go anyway:
$ tcptraceroute codex.buddypress.org
Selected device ppp0, address 114.41.23.209, port 50340 for outgoing packets
Tracing the path to codex.buddypress.org (72.233.56.139) on TCP port 80 (http), 30 hops max
1 168.95.98.254 (168.95.98.254) 33.760 ms 38.454 ms 33.979 ms
2 fyfy-3301.hinet.net (168.95.150.6) 39.644 ms 36.723 ms 35.416 ms
3 CHCH-3111.hinet.net (220.128.18.18) 46.183 ms 50.956 ms 43.635 ms
4 220-128-18-34.HINET-IP.hinet.net (220.128.18.34) 44.443 ms 40.464 ms 43.420 ms
5 r4101-s2.tp.hinet.net (220.128.7.1) 40.937 ms 43.177 ms 42.678 ms
6 r4001-s2.tp.hinet.net (220.128.7.213) 42.175 ms 44.737 ms 43.021 ms
7 r11-pa.us.hinet.net (211.72.108.217) 167.351 ms 175.713 ms 162.387 ms
8 TenGigE0-0-4-0.GW5.SCL2.ALTER.NET (152.179.112.69) 181.372 ms 170.692 ms 173.893 ms
9 0.xe-2-0-2.XT1.SCL2.ALTER.NET (152.63.56.21) 196.219 ms 173.055 ms 172.949 ms
10 0.xe-5-1-0.XL3.DFW7.ALTER.NET (152.63.101.86) 216.396 ms 216.984 ms 301.883 ms
11 TenGigE0-6-0-0.GW4.DFW13.ALTER.NET (152.63.101.5) 221.692 ms 227.942 ms 224.156 ms
12 internapGIGE1-gw.customer.alter.net (65.208.15.230) 218.617 ms 223.888 ms 222.930 ms
13 border1.pc1-bbnet1.dal004.pnap.net (216.52.191.19) 220.379 ms 224.200 ms 220.880 ms
14 layered-11.border1.dal004.pnap.net (63.251.44.74) 221.068 ms 213.366 ms 213.383 ms
15 * * *
16 wordpress.org (72.233.56.139) [open] 218.273 ms 216.009 ms 223.296 ms
I bet it is some kind of anti-spam thing against smaller countries like Taiwan. But I am able to use http://codex.wordpress.org just fine when logged in or not.
still wondering about legitimate users and wether they would caught by the mass deletions if their only activity was buddypress activity.
Interesting how compatible with buddypress is User Spam Remover? It mentions some stuff about bbpress in the faq but not buddypress. i could see mass deleting completely inactive users but maybe they just created some activity updates or joined a group or something would hate to catch those kind of users in my net.
EDIT: i just saw your other post will comment further there.
Here is an update on how I’m dealing with the spam user registrations on my Battle City site.
At some point I realized, I will never defeat the spam user registrations. My efforts helped to limit them, but not eliminate the problem. So I decided, maybe what I need to do is limit the impact. The spam user registrations are still there, but now I barely see them. This is what I do:
To limit the spam user registrations, I use “Buddypress Humanity” and “SI CAPTCHA Anti-Spam“. “Askimet” then picks up on most of the spam comments posted by those who still manage to register.
Next, I use “BuddyPress Block Activity Stream Types“. With this plugin I hide all new user registration messages from the Activity stream.
Finally, I use “User Spam Remover” plugin to go in once every couple of weeks to mass delete 95% of all spam users.
This doesn’t eliminate the problem, but makes life more manageable and keeps most of the spam users out of sight unless they manage to get past Askimet and post some messages.
My site for Battle City was getting hit hard with spam user registrations. I wrote a post about it in the forums here.
At some point I realized, I will never defeat the spam user registrations. My efforts helped to limit them, but not eliminate the problem. So I decided, maybe what I need to do is limit the impact. The spam user registrations are still there, but now I barely see them. This is what I do:
To limit the spam user registrations, I use “Buddypress Humanity” and “SI CAPTCHA Anti-Spam”. “Askimet” then picks up on most of the spam comments posted by those who still manage to register.
Next, I use “BuddyPress Block Activity Stream Types”. With this plugin I hide all new user registration messages from the Activity stream.
Finally, I use “User Spam Remover” plugin to go in once every couple of weeks to mass delete 95% of all spam users.
This doesn’t eliminate the problem, but makes life more manageable and keeps most of the spam users out of sight unless they manage to get past Askimet and post some messages.
Ok just had them installed. Thanks 🙂
i believe it is (applies to both questions)
1. Is aksimet compatible with sites using BuddyPress with Multisite?
2. Which is the best plugin for spam control on sites using BuddyPress with Multisite?
Thank you.
@zachary-dubois – All three of the plugins I mention are Multi-site and BuddyPress-compatible. I also recommend SI CAPTCHA Anti-Spam.
@themightymo,
Before I install any of these are they verified for a BuddyPress Multi site install? I’m liking the look of those plugins.
@dcavins,
That first plugin hasn’t been updated in a very long time. Not sure if I should trust it. Also, its kind of annoying to manually approve users. I need something more automated.
If WordPress had reCaptcha integrated that would be sweet.
Hi Guys,
I am also using Salutation theme for my website http://fitnessblogger.net
although I agree the learning curve is quite steep for this theme… it does have some great features.. and I am slowly making sense of some of them…
The forums were a pain to setup but now we have simplified them and we are only using the group forums for our site it seems to work better?? http://fitnessblogger.net/groups/
This may help with the BuddyBar http://wpmu.org/daily-tip-how-to-disable-the-buddypress-admin-buddy-bar/
There are a few options for spam / splogger protection… we are using WangGuard.. again this takes a little bit of use to understand and get set up but does seem to help us..
Hope this helps a bit.. and happy to chat more if you would like
PS. I am not an expert just learning as I go along 🙂
Kind Regards
James
#1 yes they can only choose from the theme you enable and you can edit that theme to include whatever information you want i think you may need to do something to prevent them from editing the css though or they might be able to change stuff.
#2 that really depends on your situation/desires sometimes giving people too many options will cause them to not make any decision, other times choices equals freedom to create. If your value proposition is based on end user control and differentiation then you probably want to leave things as open as possible if your focus is on content and not presentation then you might want to restrict things. it is always better to give people new options rather then take them away so if your on the fence start out restricted and open things up according to your comfort.
#3 yes you can spam sites but you are also super admin meaning you can admin anything on any site.
Hi,
We are in the process of launching a BuddyPress social networking site with “Multisite” enabled… site is socialwikileaks dot com
Now when people register, they have the option to get their own site (subsite on subdomain of the main site) and they “automatically” get the following:
– the theme of the main site theme
– the option to edit the looks of their blog/site from the theme backend
– they also have the same footer advertising the name of the company that sold the theme to us.
I want to make sure that all the people who select the site option during registration get almost the same site appearance to maintain the looks and feel of the main (BP/MS) site. I also want to get rid of the footer and replace with a new footer.
Q1: How can we make sure that every new site has same looks/appearance/settings/footer etc?Is there something we can adjust in the backend or is there a plugin that does this?
Q2: Is it a good idea to do the above or should we let people do whatever they want with the appearance/looks/settings etc of their subsites?
Q3: When people post on their subsites/blogs, do we get to edit or delete any posts or comments that are in-appropriate or spam?
Please advise.
Thank you very much for your help.
@ubernaut,
You can also use the following plugins for higher-level ip blocking and behavior blocking:
– Bad Behavior
– WordFence
– Better WP Security
Ok, I will try this. Also, how are users registering and not setting up their profile. They are shown in the backend off my site but not the front end. Is there a way to stop this too?
It looks like WangGuard will do the job. It can detect spam users that has already been registered, it can report them and delete them from the system. It also prevents from registering at least those who has been reported before.
interesting gonna check that out could be a huge time saver thanks for the info!
What about changing the register slug? Is this still something that should be done?
