Jon Brown

joeguilmette

<p>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.</p>
<p>For support, pull requests, and discussion: https://github.com/joeguilmette/wp-local-toolbox</p>
<h4>Admin Bar</h4>
<p>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.</p>
<ul>
<li>
<p><strong>WPLT_SERVER</strong>: 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.</p>
<p>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.</p>
</li>
<li>
<p><strong>WPLT_COLOR</strong>: Determines the color of the admin bar. You can set this to any CSS color. If left undefined, will use the following defaults:</p>
<ul>
<li>PRODUCTION / LIVE: red</li>
<li>STAGING / TESTING: orange</li>
<li>LOCAL / DEV: green</li>
</ul>
</li>
<li>
<p><strong>WPLT_ADMINBAR</strong>: 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.</p>
</li>
</ul>
<p><strong>In wp-config.php:</strong></p>
<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>
<p>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.</p>
<p>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!</p>
<ul>
<li><strong>WPLT_DISABLED_PLUGINS</strong>: A serialized array of plugins to disable.</li>
</ul>
<p><strong>In wp-config.php</strong>:</p>
<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>
<p>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.</p>
<p>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.</p>
<ul>
<li>
<p><strong>WPLT_NOTIFY</strong>: 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/</p>
</li>
<li>
<p><strong>WPLT_NOTIFY_CHANNEL</strong>: 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.</p>
</li>
<li>
<p><strong>WPLT_DISABLE_ATTACHMENT_NOTIFY</strong>: If set, this will disable notifications for attachments.</p>
</li>
</ul>
<p><strong>In wp-config.php</strong>:</p>
<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>
<p>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.</p>
<p>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.</p>
<ul>
<li><strong>WPLT_AIRPLANE</strong>: Set this to anything to enable the Airpane Mode toggle.</li>
</ul>
<p><strong>In wp-config.php</strong>:</p>
<pre><code>// enable the Airplane Mode toggle
define('WPLT_AIRPLANE', 'true');
</code></pre>
<h4>Modification</h4>
<p>You can add code that will be executed depending on server name by modifying the following in wp-local-toolbox.php.</p>
<p>I’d love a pull request if you come up with something useful.</p>
<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>
<p>As a special thank you, this plugin will remove the ridiculous <code>Howdy,</code> that is prepended to the username in the admin bar.</p>
<p>You’re welcome.</p>
<h4>Credit</h4>
<ul>
<li>
<p>Plugin disabling from <a href="https://twitter.com/markjaquith" rel="nofollow ugc">Mark Jaquith</a>: https://gist.github.com/markjaquith/1044546</p>
<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>
<p>Airplane Mode from <a href="https://twitter.com/norcross" rel="nofollow ugc">Andrew Norcross</a>: https://github.com/norcross/airplane-mode</p>
</li>
<li>
<p>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/</p>
</li>
<li>
<p>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></p>
</li>
</ul>


WP Local Toolbox

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

NSquared

Natalie MacLees

nsquaredteam

<p><strong>Plugin Detective helps you troubleshoot issues on your site quickly and easily to find the cause of a problem.</strong> Once the culprit is found, the problem plugin can be quickly deactivated. You can even fix your site when it has the white screen of death (fatal error). You’ll want to have Plugin Detective installed, so if your site crashes from a conflict or bad plugin update, you can get it back up and running quickly!</p>
<p>Plugin Detective is your best friend when you need to:<br />
– Troubleshoot WordPress plugin conflicts<br />
– Remove stuck .maintenance files<br />
– Recover your site from fatal errors caused by plugins</p>
<p>We’ve all been there–something’s broken on your site. You’ve looked around the web for advice about what to do and have stumbled across the typical wisdom: deactivate all your plugins and then reactivate them one by one, checking your site for the problem after each reactivation.</p>
<p>Ugh.</p>
<p>Sure, it works. But who has <em>time</em> for that?</p>
<div class="embed-vimeo" style="text-align: center;"><iframe loading="lazy" src="https://player.vimeo.com/video/270010645" width="750" height="422" frameborder="0" webkitallowfullscreen mozallowfullscreen allowfullscreen></iframe></div>
<h4>Find Plugin Conflicts with Detective Otto Bot</h4>
<p>Detective Otto Bot walks you through solving your case one step at a time, all from one single screen.</p>
<ol>
<li>Open a case and tell Detective Otto where you’re seeing the problem. If your site requires any plugins to run correctly, tell Otto about those, too.</li>
<li>Then, Otto will interrogate the suspects and track clues, checking in with you from time to time.</li>
<li>All you need to do is answer “Yes, it’s fixed” or “No, it’s still broken” each time. Otto will do the rest and find the culprit in minutes.</li>
</ol>
<p>Best of all – Plugin Detective can work even if you’re seeing the White Screen of Death on your site or if all you can see are PHP errors. Please have a look at the FAQ’s for how to access Plugin Detective and log into WordPress even if you can’t get to your login screen.</p>
<p>Once Otto has identified the culprit, you can quickly deactivate the troublesome plugin and go about your day.</p>
<h4>Remove Stuck .Maintenance File or Scheduled Maintenance</h4>
<p>Have you gotten stuck in maintenance mode on WordPress? The dreaded “Briefly unavailable for scheduled maintenance. Check back in a minute” message haunts you; the minute never ends!</p>
<p>With Plugin Detective installed you can quickly get out of these situations without the hassle of deleting files via your host or FTP. Just tack on this slug to the end of your website URL:</p>
<pre><code>/wp-content/plugins/plugin-detective/troubleshoot/?restore=1
</code></pre>
<p>So that your URL looks like this:</p>
<pre><code>https://yoursite.com/wp-content/plugins/plugin-detective/troubleshoot/?restore=1
</code></pre>
<p>This will prompt you to log in and automatically remove that stuck maintenance file for you.</p>
<h4>Who Can Use This Troubleshooting Tool?</h4>
<p>Plugin Detective is a tool that requires no coding experience or technical knowledge to use. For that reason, Plugin Detective is the ideal troubleshooting and conflict-checking tool for:</p>
<ul>
<li>Any WordPress website owner</li>
<li>Developers and technical support engineers</li>
<li>Plugin and theme owners and their support teams</li>
</ul>
<h4>Debug Tool Features</h4>
<ul>
<li>Strategically activate and deactivate plugins on your site to help you find the plugin causing trouble</li>
<li>Open Plugin Detective for troubleshooting on any page on your site – both in the backend and the frontend!</li>
<li>Choose any subset of your active plugins as the baseline for your testing  </li>
</ul>
<h4>Loved by Plugin Support Teams</h4>
<p>The <a href="https://simplyscheduleappointments.com/guides/plugin-detective-for-plugin-conflicts/" rel="nofollow ugc">Simply Schedule Appointments</a> and <a href="https://wpdrawattention.com/guides/plugin-detective-for-finding-conflicts/" rel="nofollow ugc">Draw Attention</a> support teams love to share this conflict-checking tool with their customers.<br />
Plugin Detective makes it easy for their clients to debug performance issues and figure out plugin conflicts in a jiffy!</p>
<h3>1.2.14 – 2023-06-10</h3>
<h4>Features and Improvements</h4>
<ul>
<li>Fix PHP 8.2 compatibility</li>
</ul>
<h3>1.2.13 – 2023-05-25</h3>
<h4>Features and Improvements</h4>
<ul>
<li>Update required WP version to 6.1</li>
</ul>
<h3>1.2.12 – 2023-05-25</h3>
<h4>Features and Improvements</h4>
<ul>
<li>Update required WP version to 6.1</li>
</ul>
<h3>1.2.11 – 2023-04-27</h3>
<h4>Features and Improvements</h4>
<p>PR:#25 – Compatibility with WordPress 6.2</p>
<h3>1.2.10 – 2023-04-11</h3>
<h4>Fixes</h4>
<p>PR:#19 – Prevent fatal error on WP versions where WP_Textdomain_Registry doesn…</p>
<h4>Features and Improvements</h4>
<h3>1.2.9 – 2023-03-28</h3>
<h4>Fixes</h4>
<h4>Features and Improvements</h4>
<h3>1.2.8 – 2023-03-28</h3>
<h4>Fixes</h4>
<h4>Features and Improvements</h4>
<h3>1.2.7 – 2023-03-28</h3>
<h4>Fixes</h4>
<h4>Features and Improvements</h4>
<h3>1.2.6 – 2023-02-24</h3>
<ul>
<li>no changes</li>
</ul>
<h3>1.2.3</h3>
<ul>
<li>Fixed for WP 6.1 compatibility</li>
</ul>
<h3>1.2.1</h3>
<ul>
<li>Fixed for WP 5.9 compatibility</li>
</ul>
<h3>1.1.8</h3>
<ul>
<li>Fixed for WP 5.8 compatibility</li>
</ul>
<h3>1.1.8</h3>
<p>For older changelog entries, please see the <a href="https://plugins.svn.wordpress.org/plugin-detective/trunk/CHANGELOG.md" rel="nofollow ugc">additional changelog.txt file</a> delivered with the plugin.</p>


Plugin Detective – Troubleshooting Conflicts


I haven't used it for real error hunting yet but I've tested the plugin and it seems awesome.


Seems to work well

Greate Plugin

Plugin Detective helps you troubleshoot issues on your site quickly and easily to find the cause of a problem. Once the culprit is found, the problem  …

WP Local Toolbox vs Plugin Detective – Troubleshooting Conflicts