When you run a network, managing commenters is handled per-site. That’s normally okay, but sometimes people decide to be trolls and spam your whole network. This plugin allows you to ban, spam or moderate an unregistered commenter network wide. It does not replace the per-site blacklists or moderation lists, but acts as addition.
When a user posts a comment and they’re on the list, they are redirected to the post they just tried to comment on, but their comment has been shunted to the mysterious black hole along with your socks. If you pick ‘blackhole’, no one will ever see the comment. Pick ‘spam’ and they go to spam. Pick ‘moderate’ and the comment is forced into moderation.
A sample email of
email@example.com is included in the plugin for you to experiment with.
Thanks to Jan for the idea of moderating and spamming. Thanks to Joey and Helen for reminding me about
get_permalink() and it’s silly inconsistencies.
- Setting a comment to ‘moderate’ doesn’t always show the ‘your comment is in moderation…’ to the user, which can be confusing.
This plugin does not track any data other than what is submitted by commenters. No additional data is recorded. It compares the input data to the lists, and acts accordingly.
DownloadLatest version: Download Sitewide Comment Control v2.1 [zip]
No special instructions needed. This plugin is only network activate-able.
FAQQ. Installation Instructions A. No special instructions needed. This plugin is only network activate-able. Q. If I change the blacklist using this plugin, will it change the Comment Blacklist? A. No, this is completely separate. Q. Does this list the rejected posters? A. If you set comments to be spammed or moderated, they will show up in the appropriate section of your comments page. If you set comments to be blackhole’d, no one will ever see them. Ever. Q. Will this block user names? A. No, it only blocks by email address. Q. Why don’t you block IPs? A. I don’t find it useful. If you’re blocking IPs, given how dynamic they are, it won’t do you any good in the long run on the app level. This should be done at the server level. Q. Will this block partial emails? A. Yes. If you put
example.comin your list, it will block
firstname.lastname@example.org. Be very careful when you do this! If you put in just the letter
afor example, you will block all email addresses with that letter. I strongly recommend you only use full domains (‘example.com’, not just ‘example’). Q. Will this block wildcards? A. No. You cannot block
email@example.com this time. This is a highly requested feature, but it’s complicated to get right without making your network unbearably slow. It doesn’t scale well in my tests. Pull requests welcome. Q. Will this block existing users? A. This plugin will not block any logged in user, even if their email is on the list. If you don’t want them commenting, delete their accounts. It’s assumed if you let someone on your site, you mean for them to have access. Q. Does this work on MultiSite? A. Yes, it does. Q. Does this work on Single Site installs? A. No. Q. Does this work on BuddyPress? A. I don’t know. Let me know!
- 22 March 2016 by Ipstenu
- Cleaning Internationalization
- Security: Nonces, sanitization, validation
- 30 October 2013 by Ipstenu
- Works with 3.7
- Removing sort to stop sorting