Sverigedemokraterna IT

Prevents comment spam using various, admin-selectable techniques.
Available in:
<ul>
<li>English</li>
<li>Swedish</li>
</ul>
Logging is handled by <a href="https://wordpress.org/extend/plugins/threewp-activity-monitor/" rel="ugc">ThreeWP Activity Monitor</a>. See the list of logged activities to enable logging of caught spam.
Most spam is caught using “extra fields”. Rarely will spam require the use of “no author website” also. Extremely rarely will a spam bot be smart enough to include the hidden fields, leave them empty and leave the author URL empty.
Catching that last kind of spambot will require other measures.
<h4>Extra fields</h4>
Two extra fields are inserted into the comment form and hidden from view using CSS. They are to be left empty, and say as much, in order for the comment to pass.
Bots that spam by inserting fake POSTs will not have the required, invisible fields in the POST – rejecting the comment.
Bots that fill in all form fields will automatically fill in these extra fields – the comment will be rejected.
<h4>No author website</h4>
Comment authors are usually allowed to fill in their URLs. Selecting this technique will only allow comments that have an empty author URL field.
Bots that fill in all form fields will fail this test.
Note that you will need to edit your template to hide the author url input from view using <code>display: none</code>.

SD Simple Antispam

scribu

Ron Rennick

Curtiss Grymala

This plugin adds 2 privacy options in a single install and 3 in a network install. In a network install the network administrators (Super admins) have the option to set the privacy setting for the entire network. When the privacy is set for the entire network, the extra privacy options are not shown on individual site’s Settings -> Privacy.
Features
In a single site WordPress install adds the following privacy options:
<ul>
<li>I would like my site to be visible only to Site subscribers.</li>
<li>I would like my site to be visible only to Site administrators. </li>
</ul>
In a WordPress network activated on an individual site adds the following privacy options:
<ul>
<li>I would like my site to be visible only to Registered network users.</li>
<li>I would like my site to be visible only to Site subscribers.</li>
<li>I would like my site to be visible only to Site administrators. </li>
<li>I would like my site to be visible only to Site contributors (and above)</li>
</ul>
When Network Activated or in the mu-plugins folder in a WordPress network adds the following:
<ul>
<li>A privacy selector in the Network Admin -> Settings page to allow individual site privacy or the 3 above across to network.</li>
</ul>
Support can be obtained through:
<a href="https://wordpress.org/support/plugin/network-privacy" rel="ugc">Try the WordPress Forums first</a>
<a href="http://twitter.com/wpmuguru" rel="nofollow ugc">Twitter</a>
<a href="http://ronandandrea.com/contact/" rel="nofollow ugc">Ron & Andrea</a>
<h3>To Do</h3>
<ul>
<li>Update the robots.txt process to use the constants/functions for wp-content, wp-includes and wp-admin directories (in case those items are in a non-standard location, or the install is in a subdirectory)</li>
</ul>

Network Privacy

Golden oldie that I use on all my staging sites. Although originally developed for Multisite, it works brilliant on standalone sites too, for which I mostly use the plugin.



Every staging site should have this

Adds more privacy options to both single Wordpress sites and WordPress networks.

SD Simple Antispam vs Network Privacy