-
Notifications
You must be signed in to change notification settings - Fork 2
/
Copy pathreadme.txt
144 lines (93 loc) · 5 KB
/
readme.txt
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
=== Module Control for Jetpack ===
Contributors: RavanH
Donate link: https://www.paypal.com/cgi-bin/webscr?cmd=_donations&business=ravanhagen%40gmail%2ecom&item_name=Module%20Control%20for%20Jetpack
Tags: Jetpack, jet pack, jetpack light, manual control, blacklist, blacklist jetpack modules, slim jetpack, unplug jetpack
Stable tag: 1.6
Requires at least: 4.0
Tested up to: 6.2
License: GPLv3 or later
License URI: http://www.gnu.org/licenses/gpl-3.0.html
Your Jetpack, Controlled.
== Description ==
[Jetpack](https://wordpress.org/plugins/jetpack/) adds powerful features, but sometimes we don't want them all... This plugin brings additional control over Jetpack.
= Features =
1. Blacklist / remove individual Jetpack modules.
1. Prevent module auto-activation on connection or after an upgrade.
1. Run Jetpack "unplugged", without a WordPress.com connection.
1. Single site and Multisite compatible.
= Examples =
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.
- 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?
- Offer your own backup service and do not care much for VaultPress competition?
- You're running a school network and (some) 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, Jetpack Module Control 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.
For **single site** installations, plugin settings can be locked down by adding `define('JETPACK_MC_LOCKDOWN', true)` to wp-config.php for complete security. This can be useful to prevent other admins being able to reactivate blacklisted modules.
= Development =
The project can be forked and or contributed to on [Github](https://github.com/RavanH/jetpack-module-control).
All contributions -- be it in the form of feature requests, bug reports, translations or code -- are welcome!
== Installation ==
1. Install Jetpack Module Control either via the WordPress.org plugin directory, or by uploading the files to your server.
2. After activating the plugin, go to either Settings > General (on single site) or Network Admin > Settings (on multisite) you can find the new Jetpack Module Control section.
3. Select any module you wish to remove and save settings.
4. If you are on a single site installation and you wish to prevent other admins from reactivating any blacklisted modules, add `define('JETPACK_MC_LOCKDOWN', true);` to your wp-config.php to lock down settings.
5. That's it.
== Screenshots ==
1. Options section with Blacklist.
== Upgrade Notice ==
= 1.6 =
Use jetpack_offline_mode filter, new icons
== Changelog ==
= 1.7 =
Date: 2024/05/21
* Coding standards
* 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 =
Date: 2015/08/01
* Fix "Missing argument 1 for 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