Plugin Detective – Troubleshooting Conflicts vs Query Monitor

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 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! Plugin Detective is your best friend when you need to: – Troubleshoot WordPress plugin conflicts – Remove stuck .maintenance files – Recover your site from fatal errors caused by plugins 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. Ugh. Sure, it works. But who has time for that? Find Plugin Conflicts with Detective Otto Bot Detective Otto Bot walks you through solving your case one step at a time, all from one single screen. 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. Then, Otto will interrogate the suspects and track clues, checking in with you from time to time. 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. 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. Once Otto has identified the culprit, you can quickly deactivate the troublesome plugin and go about your day. Remove Stuck .Maintenance File or Scheduled Maintenance 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! 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: /wp-content/plugins/plugin-detective/troubleshoot/?restore=1 So that your URL looks like this: https://yoursite.com/wp-content/plugins/plugin-detective/troubleshoot/?restore=1 This will prompt you to log in and automatically remove that stuck maintenance file for you. Who Can Use This Troubleshooting Tool? 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: Any WordPress website owner Developers and technical support engineers Plugin and theme owners and their support teams Debug Tool Features Strategically activate and deactivate plugins on your site to help you find the plugin causing trouble Open Plugin Detective for troubleshooting on any page on your site – both in the backend and the frontend! Choose any subset of your active plugins as the baseline for your testing Loved by Plugin Support Teams The Simply Schedule Appointments and Draw Attention support teams love to share this conflict-checking tool with their customers. Plugin Detective makes it easy for their clients to debug performance issues and figure out plugin conflicts in a jiffy! 1.2.14 – 2023-06-10 Features and Improvements Fix PHP 8.2 compatibility 1.2.13 – 2023-05-25 Features and Improvements Update required WP version to 6.1 1.2.12 – 2023-05-25 Features and Improvements Update required WP version to 6.1 1.2.11 – 2023-04-27 Features and Improvements PR:#25 – Compatibility with WordPress 6.2 1.2.10 – 2023-04-11 Fixes PR:#19 – Prevent fatal error on WP versions where WP_Textdomain_Registry doesn… Features and Improvements 1.2.9 – 2023-03-28 Fixes Features and Improvements 1.2.8 – 2023-03-28 Fixes Features and Improvements 1.2.7 – 2023-03-28 Fixes Features and Improvements 1.2.6 – 2023-02-24 no changes 1.2.3 Fixed for WP 6.1 compatibility 1.2.1 Fixed for WP 5.9 compatibility 1.1.8 Fixed for WP 5.8 compatibility 1.1.8 For older changelog entries, please see the additional changelog.txt file delivered with the plugin.

Query Monitor is the developer tools panel for WordPress and WooCommerce. It enables debugging of database queries, PHP errors, hooks and actions, block editor blocks, enqueued scripts and stylesheets, HTTP API calls, and more. It includes some advanced features such as debugging of Ajax calls, REST API calls, user capability checks, and full support for block themes and full site editing. It includes the ability to narrow down much of its output by plugin or theme, allowing you to quickly determine poorly performing plugins, themes, or functions. Query Monitor focuses heavily on presenting its information in a useful manner, for example by showing aggregate database queries grouped by the plugins, themes, or functions that are responsible for them. It adds an admin toolbar menu showing an overview of the current page, with complete debugging information shown in panels once you select a menu item. Query Monitor supports versions of WordPress up to three years old, and PHP version 7.4 or higher. For complete information, please see the Query Monitor website. Here’s an overview of what’s shown for each page load: Database queries, including notifications for slow, duplicate, or erroneous queries. Allows filtering by query type (SELECT, UPDATE, DELETE, etc), responsible component (plugin, theme, WordPress core), and calling function, and provides separate aggregate views for each. The template filename, the complete template hierarchy, and names of all template parts that were loaded or not loaded (for block themes and classic themes). PHP errors presented nicely along with their responsible component and call stack, and a visible warning in the admin toolbar. Usage of “Doing it Wrong” or “Deprecated” functionality in the code on your site. Blocks and associated properties within post content and within full site editing (FSE). Matched rewrite rules, associated query strings, and query vars. Enqueued scripts and stylesheets, along with their dependencies, dependents, and alerts for broken dependencies. Language settings and loaded translation files (MO files and JSON files) for each text domain. HTTP API requests, with response code, responsible component, and time taken, with alerts for failed or erroneous requests. User capability checks, along with the result and any parameters passed to the capability check. Environment information, including detailed information about PHP, the database, WordPress, and the web server. The values of all WordPress conditional functions such as is_single(), is_home(), etc. Transients that were updated. Usage of switch_to_blog() and restore_current_blog() on Multisite installations. In addition: Whenever a redirect occurs, Query Monitor adds an HTTP header containing the call stack, so you can use your favourite HTTP inspector or browser developer tools to trace what triggered the redirect. The response from any jQuery-initiated Ajax request on the page will contain various debugging information in its headers. PHP errors also get output to the browser’s developer console. The response from an authenticated WordPress REST API request will contain an overview of performance information and PHP errors in its headers, as long as the authenticated user has permission to view Query Monitor’s output. An an enveloped REST API request will include even more debugging information in the qm property of the response. By default, Query Monitor’s output is only shown to Administrators on single-site installations, and Super Admins on Multisite installations. In addition to this, you can set an authentication cookie which allows you to view Query Monitor output when you’re not logged in (or if you’re logged in as a non-Administrator). See the Settings panel for details. Browser extension Query Monitor is also available as an optional browser dev tools extension. This is an alternative to using the in-page panel that gets output into the admin toolbar. Using the browser extension has some advantages over the in-page panel: The Query Monitor panel doesn’t take up space within the page you are inspecting The panel can be resized, undocked, and moved around like any other developer tools panel Information about the Query Monitor browser extension can be found here. Other Plugins I maintain several other plugins for developers. Check them out: User Switching provides instant switching between user accounts in WordPress. WP Crontrol lets you view and control what’s happening in the WP-Cron system Thanks The time that I spend maintaining this plugin and others is in part sponsored by: Automattic ServMask WP Staging All my kind sponsors on GitHub Privacy Statement Query Monitor is private by default and always will be. It does not persistently store any of the data that it collects. It does not send data to any third party, nor does it include any third party resources. Query Monitor’s full privacy statement can be found here. Accessibility Statement Query Monitor aims to be fully accessible to all of its users. Query Monitor’s full accessibility statement can be found here.