Modulecontrole voor Jetpack

Beschrijving

Jetpack adds powerful features, but sometimes we don’t want them all… This light-weigth but effective plugin brings additional control over Jetpack.

Kenmerken

  1. Blacklist / remove individual Jetpack modules.
  2. Optionally prevent module auto-activation on connection or after an upgrade.
  3. Optionally run Jetpack “unplugged”, without a WordPress.com connection.
  4. 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!

Schermafdrukken

  • Options section with Blacklist.

Installatie

  1. Installeer Module Control voor Jetpack via de WordPress.org plugin directory, of door de bestanden naar je server te uploaden.
  2. Na het activeren van de plugin, ga naar ofwel Instellingen > Algemeen (op enkele site) of Netwerk beheer > Instellingen (op multisite) je kunt de nieuwe Module Control voor Jetpack sectie vinden.
  3. Selecteer een module die je wil verwijderen en sla instellingen op.
  4. Als je een installatie op een enkele site uitvoert en je wil voorkomen dat andere beheerders de blacklist-modules opnieuw activeren, voeg je toe define ('JETPACK_MC_LOCKDOWN', true);aan je wp-config.php om instellingen te vergrendelen.
  5. Dat is het.

Beoordelingen

25 november 2021
The latest version (1.6) requires JetPack >= 8.8.0 for using JetPack without a connected wordpress.com account. I think it would have been (and still could be) better if you test the JetPack version and use the jetpack_development_mode or jetpack_offline_mode filter as appropriate (though I don’t see why Automattic decided to rename it). If already using a plugin such as Unplug JetPack, ‘Use Jetpack modules without a WordPress.com connection’ is checked but greyed out. However, the setting from the other plugin is overwritten by your filter which actually sets it to false (unless it has been previously saved as checked whilst not greyed out). You need to respect the previously set value passed to your Jetpack_Module_Control::development_mode() filter instead of using false as the default (and pass that value to get_option('jetpack_mc_development_mode') as the default). It would also be nice if that setting was initialized on the basis of other installed plugins that affect it, so after deactiviting other plugins it retained its value. I think you’d actually need to invoke the jetpack_offline_mode (or jetpack_development_mode) filter (or perhaps use the Automattic\Jetpack\Status::is_offline_mode()/is_development_mode() method) to find out what other plugins are actually setting. Otherwise looks very good and slimline (just one PHP file with fewer than 1,000 lines).
31 oktober 2019
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.
13 augustus 2018 1 reactie
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
Lees alle 11 beoordelingen

Bijdragers & ontwikkelaars

“Modulecontrole voor Jetpack” is open source software. De volgende personen hebben bijgedragen aan deze plugin.

Bijdragers

“Modulecontrole voor Jetpack” is vertaald in 6 localen. Dank voor de vertalers voor hun bijdragen.

Vertaal “Modulecontrole voor Jetpack” naar jouw taal.

Interesse in ontwikkeling?

Bekijk de code, haal de SVN repository op, of abonneer je op het ontwikkellog via RSS.

Changelog

1.7.2

Date: 2025/06/25
* Remove Search and Social submenus when related module is blacklisted
* FIX: Manual control failing

1.7.1

Date: 2025/06/20
* FIX: Save empty blacklist as empty, not false (relevant for options cache)
* FIX: Allow autoload filter to return null
* Split up admin class

1.7

Date: 2025/06/16
* Updated fallback and icons list
* Namespace and autloading
* Coding standards
* Network settings nonce verification
* NEW: filter jmc_get_available_modules
* FIX: jetpack_offline_mode filter added too late, thanks @jqz

1.6

Date: 2020/08/19
* Replace jetpack_development_mode with jetpack_offline_mode filter
* New module icons
* Shorter list when Offline Mode is activated

1.5

Date: 2016/12/07
* NEW: option to allow site admins override contributed by @harshit_ps https://github.com/RavanH/jetpack-module-control/pull/8

1.4.2

Date: 2016/04/14
* Text domain name change to correspond with plugin slug

1.4.1

Date: 2016/04/01
* Added FR/NL translation files

1.4

Date: 2016/03/29
* Allow per site settings by Super Admin
* Added Sitemaps to known modules

1.3

Date: 2015/09/02
* Module names now translated using jetpack.mo
* BUGFIX options not saving deactivation
* BUGFIX translation files not found

1.2

Datum: 01-08-2015
* Oplossing “Ontbrekend argument 1 voor Jetpack_Module_Control::add_settings_section()” https://github.com/RavanH/jetpack-module-control/issues/2

1.1

Date: 2015/05/11
* Detect the Unplug Jetpack plugin

1.0

Date: 2015/05/05
* Jetpack Debug Mode to allow modules without connection
* Show which modules require a connection

0.4

Date: 2015/05/01
* Settings action link on Network plugins page

0.3

Date: 2015/04/27
* Added dashicons

0.2

Date: 2015/04/26
* Added network options

0.1

Date: 2015/04/25
* Initial release