| 开发者 | digitaldot |
|---|---|
| 更新时间 | 2026年10月14日 20:06 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
wp-config.php:
define( 'QMDD_PRIVATE_STORAGE_DIR', '/private/server/path' );
The plugin will refuse to write diagnostic logs if it cannot find a writable non-public directory. It will display a warning on its own Tools screen instead of falling back to a web-accessible path. Files are protected in depth with restrictive directory permissions and web server denial files; these are not a replacement for storage outside the web root.
Dependencies
Requires Query Monitor, distributed separately from WordPress.org. WordPress 6.5+ supports dependency installation via the Requires Plugins header. This plugin is an independent extension made by digitalDot, and is not affiliated with or endorsed by the Query Monitor maintainers.
No. All processing is performed on your server. ZIP files are only downloaded when an authorised administrator requests them. You decide if and where to upload an archive.
No. It only captures the requests of the logged-in administrator who explicitly enabled recording. Other users' requests are not profiled by this plugin.
No. RAW means the captured JSON Lines records are not deduplicated or summarised. Sensitive SQL literals and known URL credential parameters are redacted at collection time for both export types.
Ensure Query Monitor is activated, you are browsing with the same administrator account that activated capture, and the server allows a writable directory outside the public web root. Administrative requests are excluded unless you enable the corresponding checkbox.
The PHP ZipArchive extension must be enabled to produce downloadable ZIP archives. Without it, the plugin displays an administrator-only error.
Usually, if the host provides a private temporary directory writable by PHP. Otherwise, ask your hosting provider for a safe location and set QMDD_PRIVATE_STORAGE_DIR.
The plugin attaches its own observation hooks for the active administrator, without wrapping or replacing third-party callbacks. It can add overhead, so use it for short debugging sessions and turn it off afterwards. It is not a background performance-monitoring service.
No. WordPress does not provide a public API for precise timings of arbitrary callbacks. The plugin measures individual callbacks only when they are isolated at a priority with free adjacent priorities. Other callbacks are omitted from the component-time ranking rather than estimating a misleading cost. Total action durations are recorded separately; timing is wall-clock, not an exact CPU profile.
No. They are heuristic estimates for comparison only, using an illustrative USD rate rather than any current provider price.