Hi,
When ever I try and mark someone as a spammer or when I try and delete their account, it sends me to a “page not found” error.
It used to work very well and now all of a sudden it doesn’t.
I hope you can help me!
Thanks!
@Metric: Thanks so much for replying! I feel and I hope you would agree that more plugins = more conflicts and troubles. I am at this moment trying to use the least amount of plugins as possible and only the popular and well rated ones. I hope to resolve this without using another plugin and hopefully that Buddypress plugin itself comes up with a solution. Ideally it should because a successful and trouble free registration of a genuine user is the starting point and all the activity starts later! Just like a car gets a trouble free start and then a great ride!
does anyone know if this plugin works well with current versions of bp or if there’s an alternative? i swear i read something about 1.5 having throttle settings but i couldn’t find anything looking around.
Try using. A plugin named “Buddypress Pending Activations” it lets you check for accounts that have not yet activated their account, resend activation keys, manually activate accounts, and even delete inactivated accounts in bulk.
Hi!
I have had several spam registrations on my site (in spite of SI Captcha Anti Spam plugin) which is OK but earlier versions of Buddypress had an option under “Admin Options” called “Mark as Spammer”. But now I don’t see that in 1.6.1.
Now in 1.6.x we have “Edit Member” for admins and there’s a link called “User Capabilities” which when clicked takes me to a page saying “Oops! This link appears to be broken.” Now I have to delete the spam accounts and don’t have any option to mark spam or having registrations auto-detected as spam which used to happen earlier. Though many genuine registrations were being detected as spam also in ver 1.5.x.
One of my members is now not able to login because she is being asked for an activation number and I don’t know how to help her
. I have changed her password and I am able to login from my computer to her account though but she is still facing the same problem. We just get a link in the email to activate and I don’t know what exactly is the activation number.
Thanks in advance to all those who reply
!!
Before I updated to buddyPress 1.6.1, there was an “Admin” drop down item on my site pages that let me mark a member as a “Spammer.” How do I get that function back?
Hello I have same problem, how to fix it ?
I have the same issue, @hkcharlie and am looking for suggestions on solutions or preventatives, as well. We find that even after we delete a spammy user or block them, it doesn’t deter them from creating a new profile the next day. Once every few months, a bot of some sort will even send spam mail to all of our users, even though we don’t have a “send to all” function in our Buddypress messages.
So i’m looking for a good way to auto delete spam accounts. Long story short, I found this:
`function spammersdeletion() {
global $wpdb;
$from = strtotime(‘-30 day’, time());
$wpdb->query(‘DELETE FROM wp_users WHERE DATE(user_registered) < "'.date('Y-m-d', $from).'"AND user_status = "2"');
}
add_action(‘init’,’spammersdeletion’);`
Source:http://stackoverflow.com/questions/6212636/how-to-delete-unverified-users-in-buddypress
Is this ok to do? I remember reading somewhere that you shouldn’t directly query to wordpress database. I also took a look at the wp_users database in phpMyAdmin, and I noticed a list of user_id values with 1, all those accounts being accounts I marked as spammers from buddypress frontend. If the above function is ok, can I create another function to handle user_id = 1? I’m just a bit scared of writing a function that deletes legitimate accounts…
OMG @neononcon please tell me how I could be forgiven for my silly delay? Chaos ‘s reigned in my world for a couple of months and I forgot about Buddypress until it turns to wonderful 1.6.
– Yeah, Theme paid.
– Too bad I did not notice about the confused users when both Sidewide and Group’s forums are enabled and now I do not know how to do. But I wonder why Buddypress team does not make this better blending the use of them.
– No spam! Wangward, Akismet and WordPress Hashcash have destroyed them while I was having coffee.
PS: For anyone who wants to ask me questions, mention me, otherwise I may miss you.
I’d still like to know whether SSL would help, but I’m going to work through this blog post at the moment : http://wp.tutsplus.com/tutorials/security/best-practices-for-preventing-buddypress-spam-user-registrations/
9087877Inactive
@presence-films Try using my approach to registration, see it here: http://www.snaplist.net23.net/register/ I have 0 spammers and the sites been live for a year. @modemlooper Sounds like a great idea. Could you make the conditional so that the admin can decide which condition is applied and if the user does not meet the criteria the plugin prevents them from posting?
We’ve had a problem for some time where we can’t delete users from the front-end. Previously there was the Delete User option in the top toolbar that was a direct delete link, now the link goes to the delete part of the user profile, both produce the same error:
Fatal error: Cannot redeclare add_user() (previously declared in /home/***/public_html/wp-admin/includes/user.php:17) in /home/***/public_html/wp-admin/includes/user.php on line 18
We can delete users from the backend, but it is a lot more effort to look at the front end to find a spammer’s username, copy it, search for it on the backend and then delete, when we’re supposed to be able to do it from the front.
Thanks for any suggestions anyone can give.
So far so good. I installed a captcha. Got some legacy spam from some of the users that are spammers but I am slowly removing them. Great advice. Thanks to all. That said, the journey is far from over.
Also, I am running WP Version 3.4.1 and couple of more things that causes the same error. When in Front End neither one of the Admin Options: “Mark user as spammer” or “Delete user’s account” work from front end. They give you a 404 page. Again, it works fine from back end.
Also, When logged as admin in front end I click on “My Account” ->”Settings”->”Capabilities” I am getting a message highlighted in red:”You do not have access to this page.”
I installed new Buddypress 1.6
When I mark user from wp admin as spammer everything works fine but when I am trying to do the same thing from front end I am getting 404 error
On a related note… It would be nice if the Site Admin was notified when someone is banned by a Group Admin. In large site that allows member group creation this could help combat spam and other problem users.
@valuser: thanks for this idea (.htaccess). I’m going to look into this.
@4ella: so here’s the official answer from Login Ninja: “Unfortunately Login Ninja doesn’t support BuddyPress forms.” So how are you using it in BuddyPress???
I have no idea how to attribute success (if any) to various methods employed.
In addition to the numerous plugins and captchas some sites have also added lines to the .htaccess file
Some have added (in addition to the various plugins).
The plugin Cookies-for-comments and the lines as suggested at https://wordpress.org/extend/plugins/cookies-for-comments/
> using register instead of wp-sign-up
`RewriteCond %{HTTP_COOKIE} !^.*XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX.*$`
`RewriteRule ^register – [F,L]`
and also
`RewriteCond %{REQUEST_METHOD} POST
RewriteCond %{REQUEST_URI} .register*
RewriteCond %{HTTP_REFERER} !.*yoursite.com.* [OR]
RewriteCond %{HTTP_USER_AGENT} ^$
RewriteRule (.*) http://lmgtfy.com/?q=spammer [R=301,L]`
So the .htaccess file begins like this
`# BEGIN ANTISPAMBLOG REGISTRATION
RewriteEngine On
RewriteCond %{HTTP_COOKIE} !^.*xxxxxxxxxxxxxxxxxxxxxxxx.*$
RewriteRule ^register – [F,L]
RewriteCond %{REQUEST_METHOD} POST
RewriteCond %{REQUEST_URI} .register*
RewriteCond %{HTTP_REFERER} !.*yoursite.com.* [OR]
RewriteCond %{HTTP_USER_AGENT} ^$
RewriteRule (.*) http://lmgtfy.com/?q=spammer [R=301,L]
# END ANTISPAMBLOG REGISTRATION`
Frankly I have no idea how and whether any of this works. The best that can be said is that spam has been reduced considerably. Fingers crossed.
@4ella: I see now that Login Ninja is a paid ($15) Envato/WebFactory plugin. Only sold 135 copies. But when I tested the Captcha on the WebFactory site, it showed a standard WordPress login screen. But I’m using BuddyPress with its Registration screen (and currently using SI Captcha on that). Will it work on BuddyPress? Is that what you’re doing? Thanks.
@valuser: Spam-Destroyer: doesn’t support my version and seems pretty experimental.
@pantone: email verification is already there. They just verify it.
I also have SI Captcha for additional verification on registration form, but they’re able to get around that somehow (do not know how).
They keep coming! (the registration spammers)
– @4ella: there is no WP plugin called “Login Ninja”. I see it on CodeCanyon, but what is it?
– I found and installed two plugins: “Stop Spammer Registrations” and “Custom Registration Link”. No benefit I can see.
– But I did discover the “Whassup” plugin which is pretty cool and shows the IPs that can then be banned. But doing it manually takes way too much time.
I’m going nuts trying to deal with these registration spammers (~30/day). Help! THANKS.
I am currently running WordPress 3.4.1 and 1.6 BuddyPress and I recently upgraded from 1.5.7 BuddyPress. I have not made any modifications to the files since installation.
I am running 2.1.2 bbPress with 1.6 BuddyPress, but I am not able to activate any other plugins (Akismet, User Spam Remover, etc.). I receive fatal errors stating “Out of memory” when I try to activate any other plugin.
It seems obvious that I need to call for more memory via .htaccess file. Any alternatives?
I use Akismet to filter comments on the homepage, and I used User Spam Remover to disable “New User Registration” emails. Any alternatives to these? I noticed that 1.6 has Akismet integration, but I could not find it in the 1.6 Codex directory.
Any help is greatly appreciated!
I have not yet launched my buddypress site, but this is definitely one of my concerns.
If I required new users to verify their account with an e-mail activation link, would this help prevent spammers?