WordPress.org

Plugin Directory

Query Monitor – це панель інструментів розробника для WordPress.

Query Monitor – це панель інструментів розробника для WordPress.

Опис

Query Monitor is the developer tools panel for WordPress. 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 підтримує версії WordPress до трьох років і PHP версії 7.4 або вище.

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.
  • Використання функції “Зробити це неправильно” або “Застаріле” в коді на вашому сайті.
  • 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.
  • Використання switch_to_blog() і restore_current_blog() у багатосайтових інсталяціях.

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.

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

Privacy Statement

Монітор запитів є приватним за замовчуванням і завжди буде таким. Він не зберігає постійно жодних даних, які збирає. Він не надсилає дані третім особам і не містить сторонніх ресурсів. Повну заяву про конфіденційність Query Monitor можна знайти тут.

Accessibility Statement

Монітор запитів прагне бути повністю доступним для всіх своїх користувачів. Повну заяву про доступність Query Monitor можна знайти тут.

Скріншоти

  • Admin Toolbar Menu
  • Aggregate Database Queries by Component
  • Capability Checks
  • Database Queries
  • Hooks and Actions
  • HTTP API Requests
  • Aggregate Database Queries by Calling Function

Часті питання

Does this plugin work with PHP 8?

Yes, it’s actively tested and working up to PHP 8.4.

Who can see Query Monitor’s output?

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 when you’re logged in as a user who cannot usually see Query Monitor’s output. See the Settings panel for details.

Does Query Monitor itself impact the page generation time or memory usage?

Short answer: Yes, but only a little.

Long answer: Query Monitor has a small impact on page generation time because it hooks into a few places in WordPress in the same way that other plugins do. The impact is negligible.

On pages that have an especially high number of database queries (in the hundreds), Query Monitor currently uses more memory than I would like it to. This is due to the amount of data that is captured in the stack trace for each query. I have been and will be working to continually reduce this.

Can I prevent Query Monitor from collecting data during long-running requests?

Yes, you can call do_action( 'qm/cease' ) to instruct Query Monitor to cease operating for the remainder of the page generation. It will detach itself from further data collection, discard any data it’s collected so far, and skip the output of its information.

This is useful for long-running operations that perform a very high number of database queries, consume a lot of memory, or otherwise are of no concern to Query Monitor, for example:

  • Backing up or restoring your site
  • Імпорт або експорт великої кількості даних
  • Running security scans

Are there any add-on plugins for Query Monitor?

Список додаткових плагінів для Query Monitor можна знайти тут.

In addition, Query Monitor transparently supports add-ons for the Debug Bar plugin. If you have any Debug Bar add-ons installed, deactivate Debug Bar and the add-ons will show up in Query Monitor’s menu.

Where can I suggest a new feature or report a bug?

Please use the issue tracker on Query Monitor’s GitHub repo as it’s easier to keep track of issues there, rather than on the wordpress.org support forums.

Чи Query Monitor уже включено до мого хостингу?

Деякі хостинги WordPress включають Query Monitor як частину своєї платформи хостингу, що означає, що вам не потрібно встановлювати його самостійно. Ось деякі з них, про які я знаю:

Can I click on stack traces to open the file in my editor?

Yes. You can enable this on the Settings panel.

Як я можу повідомити про помилку безпеки?

Ви можете повідомити про помилки безпеки за допомогою офіційної програми розкриття вразливостей Query Monitor на Patchstack. Команда Patchstack допомагає перевірити, сортувати та усунути будь-які вразливості безпеки.

Do you accept donations?

I am accepting sponsorships via the GitHub Sponsors program. If you work at an agency that develops with WordPress, ask your company to provide sponsorship in order to invest in its supply chain. The tools that I maintain probably save your company time and money, and GitHub sponsorship can now be done at the organisation level.

In addition, if you like the plugin then I’d love for you to leave a review. Tell all your friends about it too!

Відгуки

04.02.2025
This plugin totally crashed the Admin area of our website. We had to contact our hosting provider and ask them to delete the plugin’s files.
Query Monitor is an incredibly useful tool for developers and site administrators. It provides detailed insights into database queries, page load times, and resource consumption, making it a must-have for debugging and performance optimization. I particularly appreciate how it highlights potential errors in the code and plugins during development, saving time and effort in troubleshooting. Its intuitive interface and in-depth reports make identifying issues straightforward. Overall, it’s a fantastic plugin that I highly recommend to anyone building or maintaining WordPress websites.
26.11.2024
I installed it in seconds and immediately knew what was causing my backend to be so sluggish. I definitely recommend checking out their site to understand what it all means.
Прочитати всі 454 відгуки

Учасники та розробники

“Query Monitor – це панель інструментів розробника для WordPress.” — проект з відкритим вихідним кодом. В розвиток плагіну внесли свій вклад наступні учасники:

Учасники

“Query Monitor – це панель інструментів розробника для WordPress.” було перекладено на 25 локалізацій. Дякуємо перекладачам за їх роботу.

Перекладіть “Query Monitor – це панель інструментів розробника для WordPress.” на вашу мову.

Цікавитесь розробкою?

Перегляньте код, перегляньте сховище SVN або підпишіться на журнал розробки за допомогою RSS.

Журнал змін

3.17.2 (4 February 2025)

  • Reinstates the “Blocks” panel

3.17.1 (2 February 2025)

  • Prevents use of the deprecated E_STRICT constant in PHP 8.4.
  • Avoids use of the deprecated setted_transient and setted_site_transient actions in WordPress 6.8.
  • Skips showing the _load_textdomain_just_in_time notices when they’re caused by Query Monitor itself.
  • Uses more appropriate formatting for a fatal error in REST API and Ajax contexts.

3.17.0 (27 November 2024)

  • Support for WordPress 6.7.
  • Support for PHP 8.4.
  • Inline scripts are now output using wp_print_inline_script_tag() so a Content Security Policy can be fully implemented.
  • Various improvements and fixes.

3.16.4 (25 July 2024)

  • Confirms support for WordPress 6.6.

3.16.3 (22 May 2024)

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

3.16.2 (22 May 2024)

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

3.16.1 (22 May 2024)

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

3.16.0 (22 April 2024)

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

3.15.0 (10 November 2023)

3.14.1 (21 October 2023)

  • Improves compatibility with WordPress Playground

Earlier versions

For the changelog of earlier versions, refer to the releases page on GitHub.