Brandon Allen

WP Fail2Ban Redux records various WordPress events to your server’s system log for integration with <a href="http://www.fail2ban.org/" rel="nofollow ugc">Fail2Ban</a>.
This plugin is (mostly) a drop-in replacement for <a href="https://wordpress.org/plugins/wp-fail2ban/" rel="ugc">WP fail2ban</a> by <a href="https://charles.lecklider.org/" rel="nofollow ugc">Charles Lecklider</a>.
While WP fail2ban is a great plugin, there are a number of improvements that could be made. In order to facilitate these improvements, a major refactoring of the codebase was necessary.
The core functionality between WP Fail2Ban Redux and WP fail2ban remains the same. WP Fail2Ban Redux is considered to be mostly a drop-in replacement, because all constants have been replaced with filters, and will, possibly, require some upgrade work. Don’t work it’s as simple as implementing the constants.
The following events are recorded by default:
<ul>
<li>Failed XML-RPC authentication attempts.</li>
<li>Successful authentication attempts.</li>
<li>Failed authentication attempts — differentiated by a user’s existence.</li>
<li>Pingback errors.</li>
</ul>
The following events can be enabled via filter:
<ul>
<li>Pingback requests.</li>
<li>Blocked user enumeration attempts.</li>
<li>Authentication attempts for blocked usernames.</li>
<li>Spammed comments.</li>
</ul>
Extra documentation is available on the <a href="https://github.com/thebrandonallen/wp-fail2ban-redux/wiki" rel="nofollow ugc">WP Fail2Ban Redux GitHub Wiki</a>.

WP Fail2Ban Redux

Tiny, Simple and Effective. Works Well.Thanks to developer.

Simple and Effective, Works Well.

Easy, effective, no unnecessary control panel, no premium parts, no boring messages, it just do the work!

Having fail2ban already configured in the server, I installed it on a bunch of WP sites.

Locking repetitive attackers, it saves some server resources peaks.

Really thanks for the plugin.

If you already have fail2ban, this is a must

Records various WordPress events to your server's system log for integration with Fail2Ban.

niknetniko

NextCellent Simple History logs events related to NextCellent in the <a href="https://wordpress.org/plugins/simple-history/" rel="ugc">Simple History</a> plugin.
Currently, it logs following events:
<ul>
<li>Adding galleries</li>
<li>Updating galleries</li>
<li>Deleting galleries</li>
<li>Adding pages for galleries</li>
<li>Adding images to galleries</li>
<li>Adding albums</li>
<li>Editing albums</li>
<li>Deleting albums</li>
<li>Updating the NextCellent options</li>
<li>Deleting images</li>
<li>Updating images</li>
</ul>
Note: this only works with NextCellent Gallery, not with NextGEN Gallery.
<h4>Requirements</h4>
NextCellent Simple History has some requirements to be able to run:
<ul>
<li><a href="https://wordpress.org/plugins/nextcellent-gallery-nextgen-legacy/" rel="ugc">NextCellent</a> 1.9.27 or higher</li>
<li>PHP 5.4 or higher (5.5 or higher is recommended, since 5.4 is no longer supported by PHP)</li>
<li>WordPress 4.0 or higher</li>
</ul>
<h4>Languages</h4>
So far NextCellent Simple History is available to:
<ul>
<li>Dutch</li>
<li>English</li>
<li>Polish (thanks to <a href="http://fw2s.com/" rel="nofollow ugc">Frank P. Walentynowicz</a>)</li>
<li>Danish (<a href="https://profiles.wordpress.org/ThomasDK81" rel="nofollow ugc">thomasdk81</a>)</li>
</ul>
If you want to help, please contact me.
<h4>Source code</h4>
The source code is available on <a href="https://bitbucket.org/niknetniko/ngg-simplehistory" rel="nofollow ugc">BitBucket</a>.
Feel free to contribute.
<h4>Credits</h4>
The plugin icon was adapted from an icon made by <a href="http://www.freepik.com" rel="nofollow ugc">Freepik</a> from <a href="http://www.flaticon.com" rel="nofollow ugc">www.flaticon.com</a> is licensed under <a href="http://creativecommons.org/licenses/by/3.0/" rel="nofollow ugc">Creative Commons BY 3.0</a>.

NextCellent Simple History

Add Simple History integration for NextCellent.

WP Fail2Ban Redux vs NextCellent Simple History