Query Monitor Versions Save

The developer tools panel for WordPress

3.16.3

2 weeks ago
  • Prevents an infinite loop when logging doing it wrong calls and deprecated calls.
  • Removes a global from query-monitor.php

3.16.2

2 weeks ago
  • Fixes another issue with the PHP autoloader in 3.16.0 and 3.16.1 that was crashing some sites

3.16.1

2 weeks ago
  • Fixes an issue with the PHP autoloader in 3.16.0 that was crashing some sites

3.16.0

1 month ago
  • Adds full support for debugging new features in WordPress 6.5: JavaScript modules and PHP translation files

3.15.0

7 months ago

3.14.1

7 months ago
  • Improves compatibility with WordPress Playground

3.14.0

7 months ago
  • Corrects the port number handling when displaying URLs for scripts and styles
  • Improves the db.php handling when activating and deactivating Query Monitor on a single site within a Multisite network, and when DISALLOW_FILE_MODS is in use
  • Improves check for Debug Bar existence
  • Identifies drop-in plugins as a specific component instead of "other"
  • Simplifies some of the data structure used when logging queries
  • Specifies that Query Monitor supports WordPress versions up to three years old

3.13.1

10 months ago
  • Avoids a fatal error if a deprecated warning is triggered early on during the bootstrap process
  • Avoids a PHP warning that can be triggered during certain HTTP API requests when Curl is not in use
  • Skips loading QM during the plugin update process

3.13.0

11 months ago
  • 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

1 year ago
  • 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