Modulecontrole voor Jetpack
Jetpack adds powerful features, but sometimes we don’t want them all… This light-weigth but effective plugin brings additional control over Jetpack.
Kenmerken
- Blacklist / remove individual Jetpack modules.
- Optionally prevent module auto-activation on connection or after an upgrade.
- Optionally run Jetpack “unplugged”, without a WordPress.com connection.
- Single site and Multisite compatible.
Voorbeelden
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…
- Using Jetpack on a network? Then network incompatible WAF (Web Application Firewall) module should be blacklisted to prevent accidental activation!
- Do you already use a light box provided by your theme or another plugin? Then blacklist the Carousel module to prevent accidental activation.
- Of je beheert een multisite en wil niet dat beheerders je bedrijfstijd controleren met de monitormodule om je te bellen telkens wanneer hun site kort ontoegankelijk is?
- Offer your own backup service? Backlist VaultPress if you do not care for VaultPress competition.
- 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.
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.
Single site and Multisite
Although the original idea arose on a multisite installation, Module Control for Jetpack is developed for both single and multisite installations.
On multisite, 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.
Voor enkele siteinstallaties, plugin- instellingen kunnen worden vergrendeld door ze toe te voegen define ('JETPACK_MC_LOCKDOWN', waar)naar wp-config.php voor volledige beveiliging. Dit kan handig zijn om te voorkomen dat andere beheerders Blacklist modules opnieuw kunnen activeren .
Ontwikkelaars-modus
Het project kan worden gevorkt en / of worden bijgedragen Github.
Alle bijdragen — zij het in de vorm van functie verzoeken, bug reports, vertalingen of code — zijn van harte welkom!