Mail Debug for WooCommerce vs Query Monitor

Mail Debug for WooCommerce allows you to debug WordPress and WooCommerce emails. After installing and activating the plugin, you’ll see a new “Mail Debug” menu, in which you’ll be able to see each email sent by WordPress. Furthermore, you can see additional information about the emails sent; you can view also an email preview. Features: A specific panel to see each email sent by WordPress. Possibility to enable/disable debug. Suggestions If you have suggestions about how to improve Mail Debug for WooCommerce, you can write us so we can bundle them into Mail Debug for WooCommerce. Translators Available Languages English (Default) If you have created your own language pack, or have an update for an existing one, you can send gettext PO and MO file write us so we can bundle it into Mail Debug for WooCommerce

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.