Adiie9

IP Blacklist Cloud

Blacklist IP Addresses from visiting your WordPress website and Usernames from spamming.  View details of all failed login attempts.

Rolf Allard van Hagen

<p><a href="https://wordpress.org/plugins/jetpack/" rel="ugc">Jetpack</a> adds powerful features, but sometimes we don’t want them all… This light-weigth but effective plugin brings additional control over Jetpack.</p>
<h4>Features</h4>
<ol>
<li>Blacklist / remove individual Jetpack modules.</li>
<li>Optionally prevent module auto-activation on connection or after an upgrade.</li>
<li>Optionally run Jetpack “unplugged”, without a WordPress.com connection.</li>
<li>Single site and Multisite compatible.</li>
</ol>
<h4>Examples</h4>
<p>In most use cases, a carefully considered combination of Jetpack modules can be a really good thing. But not always is much consideration being done beforehand. Or site admins just don’t know all the implications…</p>
<ul>
<li>Using Jetpack on a network? Then network incompatible WAF (Web Application Firewall) module should be blacklisted to prevent accidental activation!</li>
<li>Do you already use a light box provided by your theme or another plugin? Then blacklist the Carousel module to prevent accidental activation.</li>
<li>Or you’re running a Multisite and do not want any admins monitoring uptime with the Monitor module just to call you every time their site is briefly inaccessible?</li>
<li>Offer your own backup service? Backlist VaultPress if you do not care for VaultPress competition.</li>
<li>You’re running a school network and sites are managed by minors who are not allowed to sign up for an account at WordPress.com? Then use the Jetpack Offline Mode option to allow usage of modules that do not require a connection.</li>
</ul>
<p>Any one of Jetpack’s modules can bring overlapping or even conflicting functionality. In such cases, being able to prevent (accidental) activation is a good thing.</p>
<h4>Single site and Multisite</h4>
<p>Although the original idea arose on a multisite installation, Module Control for Jetpack is developed for both single and multisite installations.</p>
<p>On <strong>multisite</strong>, it can only be network activated and allows global rules for Jetpack on all sites. At this point it also allows per-site changes by Super Admin only. Jetpack itself can, but does not need to be network activated. In that case, activate Jetpack on the main site and then network-activate Module Control.</p>
<p>For <strong>single site</strong> installations, plugin settings can be locked down by adding <code>define('JETPACK_MC_LOCKDOWN', true)</code> to wp-config.php for complete security. This can be useful to prevent other admins being able to reactivate blacklisted modules.</p>
<h4>Development</h4>
<p>The project can be forked and or contributed to on <a href="https://github.com/RavanH/jetpack-module-control" rel="nofollow ugc">Github</a>.</p>
<p>All contributions — be it in the form of feature requests, bug reports, translations or code — are welcome!</p>


Module Control for Jetpack

This plugin fits perfectly with my needs.  For example when installing the Jetpack's gallery in a client's website I prefer not to setup a wordpress.com account just for that.



Very useful

Tames the beast known as Jetpack. Jetpack just seems to be getting worse all the time... This plugin works pretty good at getting some control back over it.
Thanks, Ravan

Tames the beast

like the fact that you can ban(blacklist) features in jetpack! Very good considering that jetpacks tends to do what it wants on your website.

IP Blacklist Cloud vs Module Control for Jetpack