joeguilmette

Jon Brown

Through constants defined in wp-config, you can disable plugins, disable the loading of external files, set search engine visibility, display or hide the admin bar, display the server name and change the color of the admin bar, or literally anything else you can think of. All without touching the database, so you can push and pull without worrying.
For support, pull requests, and discussion: https://github.com/joeguilmette/wp-local-toolbox
<h4>Admin Bar</h4>
Change the color of your admin bar and display the name of the current server environment. Green for local, orange for staging, and of course, red for production. You can also force the front end admin bar to hide, to display, and can even set it to display when logged out.
<ul>
<li>
WPLT_SERVER: The name of your server environment. It will be displayed in the admin bar at browser widths greater than 1030px. If left undefined, the plugin will make no changes to the admin bar.
If not defined as <code>PRODUCTION</code> or <code>LIVE</code>, the plugin will enable ‘Discourage search engines from indexing this site’ to prevent your development and staging servers from being indexed. This option is not stored in the database, so your production server will still look to the actual setting on the Reading page.
</li>
<li>
WPLT_COLOR: Determines the color of the admin bar. You can set this to any CSS color. If left undefined, will use the following defaults:
<ul>
<li>PRODUCTION / LIVE: red</li>
<li>STAGING / TESTING: orange</li>
<li>LOCAL / DEV: green</li>
</ul>
</li>
<li>
WPLT_ADMINBAR: Show or hide the admin bar on the frontend. <code>FALSE</code> will force it to be hidden, <code>TRUE</code> will force it to display, <code>ALWAYS</code> will display the admin bar even when logged out. These settings will override the ‘Show toolbar’ setting in the ‘Users > Your Profile’ options panel and <code>add_filter('show_admin_bar', '__return_false');</code> in functions.php, but doesn’t attempt to overcome any CSS based hiding of the admin bar.
</li>
</ul>
In wp-config.php:
<pre><code>// set server environment to 'LOCAL'
define('WPLT_SERVER', 'local');

// set admin bar color to #800080
define('WPLT_COLOR', 'purple');

// show the admin bar even when logged out
define('WPLT_ADMINBAR', 'always');
</code></pre>
<h4>Disable Plugins</h4>
Pass a serialized array in this constant to disable plugins. This does not store any data in the database, so plugins that are manually deactivated or activated through the admin panel will stay so.
In order for this feature to function properly, WP Local Toolbox must be installed as an mu-plugin. You can read more about mu-plugins here: https://codex.wordpress.org/Must_Use_Plugins. We’re investigating ways to avoid this requirement; if you have any ideas we’d love to hear it!
<ul>
<li>WPLT_DISABLED_PLUGINS: A serialized array of plugins to disable.</li>
</ul>
In wp-config.php:
<pre><code>// deactivate a set of plugins
define('WPLT_DISABLED_PLUGINS', serialize(
 array(
 'hello-dolly.php',
 'w3-total-cache/w3-total-cache.php',
 'updraftplus/updraftplus.php',
 'wordpress-https/wordpress-https.php'
 )
));
</code></pre>
<h4>Post Update Notifications</h4>
Receive notifications when any page, post, or attachment is added or updated. Notifications can be received via email, or can be sent to a Slack channel via their Incoming WebHook API.
This is helpful in production to see if a client has submitted a new post, or in development to see if data is being added to the staging environment so you don’t accidentally overwrite new posts when pushing databases around.
<ul>
<li>
WPLT_NOTIFY: Define this constant as the email address where you’d like to be notified of post updates. You can specify either an email address or a Slack Incoming WebHook URL. You can set up a Slack Incoming WebHook URL here: https://my.slack.com/services/new/incoming-webhook/
</li>
<li>
WPLT_NOTIFY_CHANNEL: If WPLT_NOTIFY is set to a Slack Incoming WebHook URL, you can specify the channel that the notification will be posted to. If left unset, it will post to the default channel specified in Slack’s Incoming WebHooks settings page.
</li>
<li>
WPLT_DISABLE_ATTACHMENT_NOTIFY: If set, this will disable notifications for attachments.
</li>
</ul>
In wp-config.php:
<pre><code>// send an email to someone@somewhere.com 
// whenever any post or page is updated
define('WPLT_NOTIFY','someone@somewhere.com')

// or, send a notification to a Slack channel
define('WPLT_NOTIFY', 'https://hooks.slack.com/services/etc');
define('WPLT_NOTIFY_CHANNEL','#channel');
</code></pre>
<h4>Airplane Mode</h4>
Control loading of external files when developing locally. WP loads certain external files (fonts, gravatar, etc) and makes external HTTP calls. This isn’t usually an issue, unless you’re working in an evironment without a web connection. This plugin removes / unhooks those actions to reduce load time and avoid errors due to missing files.
On and Off: Can be toggled from the admin bar by clicking ‘Airplane Mode’. In the admin bar a ✗ or ✓ will indicate if Airplane Mode is enabled or disabled.
<ul>
<li>WPLT_AIRPLANE: Set this to anything to enable the Airpane Mode toggle.</li>
</ul>
In wp-config.php:
<pre><code>// enable the Airplane Mode toggle
define('WPLT_AIRPLANE', 'true');
</code></pre>
<h4>Modification</h4>
You can add code that will be executed depending on server name by modifying the following in wp-local-toolbox.php.
I’d love a pull request if you come up with something useful.
<pre><code>if (strtoupper(WPLT_SERVER) != 'LIVE' && strtoupper(WPLT_SERVER) != 'PRODUCTION') {
 // Everything except PRODUCTION/LIVE SERVER

 // Hide from robots
 add_filter( 'pre_option_blog_public', '__return_zero' );

} else {
 // PRODUCTION/LIVE SERVER

}
</code></pre>
<h4>Notes</h4>
As a special thank you, this plugin will remove the ridiculous <code>Howdy,</code> that is prepended to the username in the admin bar.
You’re welcome.
<h4>Credit</h4>
<ul>
<li>
Plugin disabling from <a href="https://twitter.com/markjaquith" rel="nofollow ugc">Mark Jaquith</a>: https://gist.github.com/markjaquith/1044546
<ul>
<li>Using this fork from <a href="https://twitter.com/rarst" rel="nofollow ugc">Andrey Savchenko</a>: https://gist.github.com/Rarst/4402927</li>
</ul>
</li>
<li>
Airplane Mode from <a href="https://twitter.com/norcross" rel="nofollow ugc">Andrew Norcross</a>: https://github.com/norcross/airplane-mode
</li>
<li>
Always showing the admin bar from <a href="https://twitter.com/perishable" rel="nofollow ugc">Jeff Star</a>: http://digwp.com/2011/04/admin-bar-tricks/
</li>
<li>
A healthy refactoring from <a href="https://twitter.com/jb510" rel="nofollow ugc">Jon Brown</a> of <a href="http://9seeds.com/" rel="nofollow ugc">9seeds</a>
</li>
</ul>

WP Local Toolbox

A simple plugin to help manage development over local, staging and production servers.

Will Earnhardt

Depending on your server setup, there may be tests in the WordPress Site Health tool that are not relevant and will never pass. For example, you may have background updates disabled if your entire site is kept under version control.
This plugin adds a simple settings page to exclude those tests from the Site Health Status page.
Note: This should only be used to disable tests with a legitimate and acceptable reason for failing. It should not be used to hide tests which can be fixed.
<h4>Credits</h4>
Icon from the <a href="https://www.iconfinder.com/icons/4174309/geometric_heart_heartbeat_hearts_love_valentine_icon" rel="nofollow ugc">Geometric Hearts Valentine’s Day icon set</a> by <a href="https://www.iconfinder.com/Abstracto-create" rel="nofollow ugc">Katerine Melina (Abstracto Create)</a> and licensed under <a href="https://creativecommons.org/licenses/by/3.0/" rel="nofollow ugc">CC by 3.0</a>.

Site Health Tool Manager

This plugin enables me to somewhat control the site Health, and having the luxury to not explain certain things to my customers...

Thanks.

Really Good !

If you manage a website for someone who maintains administrator privileges on the site, but would be bothered by failing tests in WordPress 5.2's new Site Health dashboard, this plugin is an excellent tool. 

Note: you should NOT use this plugin to ignore problems on the site like woefully out-of-date PHP or other critical security issues. Instead, you should resolve the root issue. 

But (for example) if your server/host is unable to update to PHP 7.3 (at the time of this review, that's the recommended version) but is running 7.2... it may be useful to remove that "recommendation" from the list of checks temporarily. 

Another plus in the plus-column: this plugin can even remove tests that are added by third-party code.  

Excellent plugin for developers and power users.

Thanks for making this plugin, essential tool so that clients do not get in panic!

Must-have tool for WP 5.2+ and clients... :-)

Easily control which tests appear in the the Site Health Tool

WP Local Toolbox vs Site Health Tool Manager