| 开发者 | lumiblog |
|---|---|
| 更新时间 | 2026年1月30日 21:50 |
| 捐献地址: | 去捐款 |
| PHP版本: | 7.0 及以上 |
| WordPress版本: | 6.9 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
wp-config.php file:
define( 'WP_DEBUG', true ); define( 'WP_DEBUG_LOG', true );
debug-log-inspector folder to the /wp-content/plugins/ directorywp-config.php fileAdd these lines to your wp-config.php file (before the "That's all, stop editing!" line):
define( 'WP_DEBUG', true ); define( 'WP_DEBUG_LOG', true );
Yes! You can add any WordPress plugin to monitor. Just provide the plugin name, file path, and search terms through the settings page.
Search terms are keywords that the plugin looks for in your debug.log file. For example, if you're monitoring WooCommerce, you might use "woocommerce, wc-" as search terms. These should be unique identifiers that appear in error messages from that plugin.
The plugin file path is usually in the format: folder-name/main-file.php
For example:
woocommerce/woocommerce.phpcontact-form-7/wp-contact-form-7.phpwordpress-seo/wp-seo.php
You can find this in your WordPress admin under Plugins > Installed Plugins (it's shown below each plugin name).By default, the plugin scans the last 300KB of your debug.log file. You can customize this in Settings > Log Inspector > General Settings.
No. The plugin only runs in the WordPress admin area and uses efficient file reading techniques to minimize performance impact.
Yes! In the settings page, you can toggle any plugin on/off without deleting it from your list.
Yes, the plugin works on WordPress Multisite installations.
Absolutely! As long as the plugin generates errors in the debug.log, you can monitor it.
See the "Testing the Plugin" section below for detailed instructions on how to verify everything is working correctly.