Query Monitor

更新日志

3.13.1

• Avoid a fatal error if a deprecated warning is triggered early on during the bootstrap process
• Avoid a PHP warning that can be triggered during certain HTTP API requests when Curl is not in use
• Don’t load QM during the plugin update process

3.13.0

• Adds a dedicated panel for “Doing it Wrong” and deprecated functionality usage
• Allows data in the HTTP API requests panel to be filtered by host name
• Adds a “Type” column wherever a list of hooks can show both actions and filters
• Improves various aspects of the “Editor” setting
• Increases the minimum supported version of PHP to 7.4
• Many thanks to @crstauf for the majority of the new features in this release

3.12.3

• Improves theme template part data collection when the Gutenberg plugin is in use with a block theme
• Skips attempting to resolve a block template if the theme doesn’t support block templates
• Removes the fallback to $EZSQL_ERROR for database query errors as it’s not possible to determine if the error should be ignored

3.12.2

• Adds the total count to the table footer of the PHP Errors panel
• Improves the destination URL for links that point to the site editor
• Implements some minor visual improvements
• Removes unreliable information about the transport for HTTP API requests
• Removes Query Monitor output from the interim login modal

3.12.1

• Corrects some inter-panel links that point to the Queries panel and sub-panels
• Switches to sessionStorage for the selected table column filters so they don’t persist across tabs or sessions
• Removes the “Debug Bar:” prefix on the menus for panels inherited from the Debug Bar plugin

3.12.0

• Clarifies and improves information in the Template panel when a block theme or full site editing (FSE) is in use
• Avoids PHP warnings if a third party plugin makes unexpected changes to language file paths
• Implements some minor performance improvements
• Removes misleading information about WordPress memory limits
• Removes support for multiple instances of wpdb (see the FAQ for more information)

3.11.2

• Implements various accessibility improvements
• Fixes an issue where not all admin area footer scripts were shown in the Scripts panel
• Improves output when the SQLite feature in the Performance Labs plugin is in use
• Removes QM output altogether from the Customizer
• Ensures wp-content/db.php from another plugin doesn’t get removed when deactivating QM

3.11.1

• Avoids a fatal error in PHP 8 when posix_getpwuid() or posix_getgrgid() doesn’t return an expected value.

3.11.0

• Adds a new “Multisite” panel that shows usage of switch_to_blog() and restore_current_blog() on Multisite installations
• Improves the output shown for blocks and template parts when block themes or full site editing is in use
• Introduces new QM_Data and QM_Component classes to make the data collection more structured and reliable
• Increases the minimum supported version of PHP to 7.2
• Improves the performance of SVG icons
• Removes the ability to completely hide silenced PHP errors
• Avoids some deprecated notices in PHP 8.2
• Improves the performance of the PHP class autoloader

3.10.1

• Prevents logging duplicate entries for multiple calls to load the same translation file
• Brings the dispatcher priority back down to 9 for maximum compatibility with other plugins that use a shutdown handler

3.10.0

• Adds information about the current language on the Languages panel
• Reduces the chance that Query Monitor blames itself for PHP errors that don’t have a stack trace
• Replaces the use of Dashicons with inline SVGs and removes the dashicons dependency
• Switches to class autoloading via Composer for reduced memory usage
• Changes the priority of the shutdown dispatcher from 0 to PHP_INT_MAX to ensure as much data as possible is collected
• Improves the styling of Debug Bar add-ons
• Fixes some erroneous localisation of float values in REST API output
• Bumps the minimum supported PHP version to 5.6
• Improves various other bits and bobs

3.9.0

• Introduces a dark mode toggle on the Settings panel, which replaces the QM_DARK_MODE constant
• Prevents errors with undefined constants being reported in db.php
• Adds more comprehensive handling of unexpected values in stack traces
• Fixes PHP Warning ‘Header may not contain NUL bytes’ when outputting headers

3.8.2

• Fixes some deprecated notices with PHP 8.1
• Improves the handling of SQL queries that consist only of MySQL comments

3.8.1

• Fixes an incompatibility with PHP versions prior to 7.2
• Fixes a warning that was being triggered within the PHP header dispatcher
• Introduces the qm/component_type/{$type} filter
• Introduces a QM_VERSION constant

3.8.0

• Introduces the ability for a third party to cease all further data collection and output at any point by calling do_action( 'qm/cease' ), for example to prevent memory exhaustion during long-running operations
• Reduces the width of the admin toolbar menu item by using lower decimal precision
• Improves the Template panel information when a block theme is in use (for Full Site Editing)
• Improves the performance and accuracy of stack traces and calling function information
• Corrects some formatting of numbers and error messages in the REST API output
• Adds more useful information when a persistent object cache or opcode cache isn’t in use
• Improves clarity in the Scripts and Styles panels when any of the URLs include a port number
• Introduces the qm/component_context/{$type} filter to complement qm/component_name/{$type} and qm/component_dirs
• Improves internal code quality, internationalisation, and further reduces overall memory usage

3.7.1

• Add a fallback for timing processing during Ajax requests that are dispatched before the shutdown hook.

3.7.0

• Introduce debugging output in a qm property in enveloped REST API responses
• Add HTTP API call information to the overview panel
• Don’t show QM output inside WordPress embeds as nobody uses this
• Don’t try to access the QM_HIDE_SELF constant before it’s defined
• Process the timing and memory related stats as early as possible so the data isn’t too skewed

3.6.8

• Add WordPress memory usage statistic to Overview panel
• Add block context information to the Blocks panel
• Fix row highlighting of TH cells
• Fix some panel resizing bugs

3.6.7

• Implement a QM_DB_SYMLINK constant to prevent the db.php symlink being put into place.
• Remove a dependency on SAVEQUERIES in the query collector.
• Remove invalid scope attributes on table cells.

3.6.6

• PHP 8 fix.
• Improve the display for various empty values when logging.
• Don’t display child menus until the parent menu is active. Makes the menu clearer.
• Detect local host names in HTTP API requests and don’t mark them as ignoring certificate verification.
• Prevent the text in toggle buttons from being selected when selecting data in tables.
• Remove support for the Dark Mode plugin which isn’t Dark Mode any more.

3.6.5

• Always show the Logs panel, with a link to help docs.
• Whole bunch of improvements to QM’s “broken” state handling.
• Remove usage of deprecated jQuery methods.
• Add support for Altis dependencies as components.
• Add innodb_buffer_pool_size variable to the mysql environment list.
• Preformat the Logger output
• Fix the PHP version check.

3.6.4

• Correct an error introduced in 3.6.2 with the extra early error handling (ironic).

3.6.3

• Correct the size of the close icon.

3.6.2

• Capture and display the most recent PHP error that occurred before QM loaded.
• Add support for the environment type added in WP 5.5.
• Avoid a potentially blank translation for some plural forms.
• Increase some contrast in dark mode.
• Combine the response-related sections of the Request panel.
• Add extra sanity checking when attempting to fetch the posix user information.

3.6.1

• Adjust the bottom margin when the QM panel is open so QM doesn’t cover the bottom of the page. Works more often than not.
• Prevent QM from triggering a fatal itself if a fatal occurs before the HTML dispatcher is loaded.
• Add an informational message to the template output when template hooks are in use.
• Fix errors caused by missing user or group IDs when collecting environment data.
• Add TextMate to list of supported editors.
• Demote some cache warnings to informational messages.
• Support passing backtrace to QM_Backtrace.

3.6.0

• Improvements to the UI when a fatal error occurs, including an admin toolbar warning.
• Improvements to the UI when QM is running in “broken” mode due to missing jQuery or an unrecoverable JavaScript error.
• Don’t display fatal errors if error display is off and the user cannot view QM.
• Improvements to the visual appearance of the wp_die() output.
• Simplify re-throwing a caught exception so QM doesn’t get the blame for fatal errors, eg. in the WordPress core fatal error handler.
• Add support for logging a variable of any type in the logger, as a replacement for var dumping.
• Don’t show a message for errors in Ajax calls that have already occurred on the main page load.
• Don’t dispatch QM during an iframed request, eg the plugin info modal or an upgrader action.
• Hide QM itself from various panels by default to remove noise. Can be controlled via the existing QM_HIDE_SELF configuration constant.
• Support for the new is_favicon() conditional added in WP 5.4.
• Fix the side panel resizing functionality.
• Add a WP-CLI command for creating the symlink to the db file.
• Add filters to QM_Util::get_file_dirs() and get_file_component() to allow support for non-standard plugin and theme locations.
• Add an action that fires when QM enqueues its assets, so add-on plugins can enqueue theirs only when necessary.

3.5.2

• Add support for exposing Full Site Editing blocks in the Block Editor panel.

3.5.1

• Defer population of the found_formatted property because this can fire before WPML has initialised its locale proxy. Fixes #485.
• Ensure all error types are accounted for when populating the panel menu error count. Fixes #486.

3.5.0

• Add an editor selection UI on the Settings panel.
• Improve the output of missing asset dependencies.
• Improve the output of unsuccessful template parts.
• Handle non-boolean constants such as WP_DEBUG_LOG, which now accepts a path too.
• Add support for touch devices when resizing the panel. (Works alright-ish, probably needs some animation frame work.)
• Apply the same styles to notices, deprecated, and strict errors.
• Some more style resets for compatibility with popular themes.
• Style changes to bring QM inline with WP 5.3’s improved button and focus styles.
• More colour contrast and dark mode tweaks.
• Add permalink-related filters to the concerned filters for the Request panel.
• Fix and improve the admin toolbar menu hover colours.
• Add the error count to the panel menu.
• Remove unnecessary use of plural forms added in 3.4.0.
• More CSS resets to avoid overly tall filters in Firefox.
• Improved styling for warning rows.
• Display the log count in the menu item.

3.4.0

• Introduce an exception handler so a stack trace can be shown for fatal errors in PHP >= 7.
• Add separate persistence of QM window for front-end and admin area.
• Add the request and response HTTP headers to the Request panel.
• Introduce Started and Stopped columns in the Timings panel.
• By popular demand, revert back to closest first ordering of stack traces so they’re inline with most other dev tools out there.
• Show the script handle in addition to the text domain in the Languages panel.
• Improve the panel menu highlighting colours.
• Better presentation of the default and current values for the settings constants.
• Truncate long host names in the Scripts and Styles panels.
• Add some more of the admin screen globals to the admin collector.
• Switch back to using a monospace font in numeric data cells.
• Allow dark mode to be enabled with QM_DARK_MODE.
• Display the total query count even when SAVEQUERIES is defined as false.
• Allow proper plural forms to be used wherever a phrase includes a numeric value.
• More style resetting for compatibility with Twenty Twenty.
• Avoid a division by zero when cache hits is 0.
• Switch to (mostly) CSS for the child menu item marker.