Linux 软件免费装
Banner图

WP Control

开发者
更新时间 2025年8月21日 12:47
PHP版本: 7.4 及以上
WordPress版本: 6.8.2
版权: GPLv3 or later
版权网址: 版权信息

标签

debug cron error log transients requests mail log

下载

3.0.0 3.0.1 3.1.0 3.1.1 1.6.1 1.9.8 2.7.1 1.9.6 2.7.2 1.4.0 2.4.2 2.1.3 2.2.2 1.8.2 1.9.5.1 2.1.2 2.8.1 1.9.7 1.5.0 1.6.0 1.0.1 1.8.3 1.8.4 1.8.1 2.5.0 2.4.0 1.8.4.1 1.9.4.1 1.9.5 1.3.0 1.0.0 1.1.0 1.1.1 1.2.0 1.5.1 1.7.0 1.7.1 1.7.2 1.7.3 1.7.4 1.7.5 1.8.0 1.8.6 1.9.0 1.8.5 1.9.1 1.9.2 1.9.2.1 1.9.3 1.9.4 1.9.8.1 1.9.8.2 2.0.0 2.3.0 2.4.2.1 2.6.0 2.1.0 2.1.1 2.2.0 2.4.1 2.6.2 2.2.1 2.6.1 2.7.0 2.8.0 2.8.2 2.9.0

详情介绍:

WP Control is a powerful plugin designed for WordPress sites with extensive error logs. It allows administrators to: How this feature works: If fatal error is detected from the plugin, it sends notifications to Slack or Telegram channels (if set), and provides recovery link along with the error message. When used, that link allows admin to login and suppresses all the plugins and active theme (except the WP Control plugin). You can observe the error log using the plugin screen and see where, when and what caused the error and take measures. You can completely disable the errored plugin or theme, switch to another version or just fix the error (if possible). Once done - just exit recovery mode and everything should continue working normally. Note: Every time fatal is thrown, for security reasons new link is generated, every single one of them should work, but on busy sites that could lead to 10s of generated links. This plugin is ideal for developers and administrators who need robust tools for troubleshooting and maintenance. You can completely disable individual modules (if you are not using them) or enable them only when needed. You can see it in action here or use the "Live Preview" button on the WordPress plugin page. Key Features:

安装:

  1. Download the plugin from the WordPress Plugin Directory.
  2. Upload the 0-day-analytics folder to the /wp-content/plugins/ directory.
  3. Activate the plugin through the 'Plugins' menu in WordPress.
  4. You will see new menu in admin bar (left hand) called WP Control.
Voila! It's ready to go. Technical specification...

屏幕截图:

  • **Settings Page** - Toggle logging options and configure advanced settings.
  • **Setting reset / import / export** - You can upload or reset plugin settings from here.
  • **Cron manager** - Built-in is very powerful cron manager.
  • **Transients manager** - Built-in is very powerful transients manager.
  • **Plugin Version Switcher** - Built-in plugin version switcher.
  • **Table manager** - Built-in is very powerful SQL table manager.
  • **Table manager operations** - Current table more detailed information and truncate and delete operations.
  • **Requests operations** - All the request made from the given WP install.

常见问题:

Why only last 100 error logs?

Plugin is designed to be as fast as possible and work with enormously large log files, consuming as less resources as possible, no other plugin could provide something even close to that, thats why it comes with this limitation. And one single error could contain more than 30K sub-rows. But 100 is more than enough - errors before that are either too old, no longer related or repeating ones, in fact is best to regularly truncate your log file and check for only the last error. And last but not least - this are 100 errors not 100 lines of the error log. You can increase that up-to 999 using screen options menu but do that on your wn risk.

Why there is no pagination for error logs?

That is once again related to the nature of the error log - one single reload could generate tens of new errors, so paginating this would probably never come handy, and in order to paginate, the entire log must be read every time - which is extremely bad idea resource-wise.

Why I see 2 records for errors which look the same but one is with "Details" button?

Usually deprecated errors in WP and next to useless when it comes to guess what is causing them - WP Control captures deprecated WP errors as early as possible and even before the check if they should or not trigger error. That means the plugin will log deprecated error even if that given error is set (usually by other plugins) not to trigger error (silenced) and then will return the execution to the WordPress. That is done because this way plugin can provide very detailed information of what caused the error and when (in code) hence - the "Details" button. If the given error is not silenced, it will then trigger normal error which comes after the plugin check - that is the reason for 2 almost the same errors. = How do I enable or disable error logging? =\ Go to "WP Control > Settings" in your WordPress dashboard and toggle the logging option as needed. = Can this plugin handle large error logs? =\ Yes, Error Log Manager is optimized for gigabyte-sized log files, ensuring smooth performance even with extensive logs. = Where are the error logs are stored? =\ The plugin autodetects default error log location, usually WordPress defines that in wp-config.php. You can customize this path if needed - this is strongly recommended for security reasons, and don't worry - you can do it with one click from plugin settings.

Note

Because of its extremely poor implementation and interfering with the proper WordPress workflow (debug log set, constant pollution of the log file, improper JS implementation etc.), Log-IQ plugin is automatically deactivated.

更新日志:

3.1.0 Added "From" in Mail logger module. 3.0.0 Mail logger introduced. 2.9.0 Option to disable browser notifications from settings (in plugin not in the browser). Implemented different sorting options for crons viewer. Code improvements and bug fixes. 2.8.2 As of this version you can disable individual modules (if you are not using them) or enable them only when needed. Cron job introduced for auto clearing the requests table. Switched cron execution from AJAX to REST API. Filter error log results by Plugin (if there are results). Cron job introduced for auto clearing the error log file (leaving last records based on the selected value from settings). 2.8.1 Option to copy and share Request / Response from the request details. Code optimizations. Error log filtering enhancements. 2.8.0 REST API calls monitoring in the request viewer, logic improvements. Plugin own REST API name endpoint change. 2.7.2 Solves problem with fatal error "Call to undefined function is_user_logged_in" very thanks to @lucianwpwhite on this one. Fixed problem with bulk actions not working on plugins.php page. 2.7.1 Small maintenance update - mostly UI problems addressed. 2.7.0 Introduced Request viewer log. Bug fixes and UI improvements. Code optimizations. Multisite optimizations. 2.6.2 Multisite improvements and transient edit functionality fixes. 2.6.1 Recovery mode improvements - Fixes problem with Slack notifications - by default Slack follows links. Added checks for multisite and suppresses logic if one is detected. 2.6.0 Code logic improvements. Added option to disable all external requests. Added error capturing for when API requests trow WP_Error. Extended error reporting feature. Implemented recovery mode if fatal error occurs and WP Core does not catch it. 2.5.0 Multisite fixes, trigger_error filter introduction. 2.4.2.1 Bug fix when database name contains '-'. 2.4.2 Bug fix with missing variable in error class - special thanks to @lucianwpwhite. 2.4.1 Removed messages when WP_DEBUG_DISPLAY is enabled as it produces "headers already sent" notification. Tables view now supports Truncate operation (for all tables) and Drop operation (for non wp core tables). Deprecation WP functions improvements and better handling. Code optimizations. 2.4.0 Code and UI improvements. JS fixes. 2.3.0 Bug fixes. Added single rows delete confirmation. Table information included. 2.2.2 Bug fixes. Added confirmation dialog when delete DB table record from the quick menu. Logic improvements. 2.2.1 Fixed "doing_it_wrong" error. 2.2.0 Now supporting all tables in the give DataBase. Bug fixes and optimizations. 2.1.3 PHP Warnings fix. 2.1.2 Warnings fix removed and added table size. 2.1.1 WP Screen not set error fix. 2.1.0 Code optimizations and SQL Table Viewer. 2.0.0 Code improvements - mostly JS responses and better interaction with UI. Errors coming from mail function (WP_Error) catching. Text selected in the console-like window (bottom of the error log viewer) is automatically copied into the clipboard. 1.9.8.2 Very small code updates and proper version settings. 1.9.8.1 'Headers already sent' in settings error fix. 1.9.8 Automatically deactivates Log-IQ plugin. Lots of code optimizations, added Cron add functionality, fixed errors. 1.9.7 Extended default admin Plugins page - gives thee option to switch to older version directly from the page and shows information about the plugin main file location. 1.9.6 Lots of UI changes both light and dark skin. Filtering the severities directly from the error log list view. 1.9.5.1 Fixed warning message about missing setting. Small code optimizations. 1.9.5 Added option to monitor wp_die when it is called with parameters - enabled by default. 1.9.4.1 Bug fixes and UI changes. 1.9.4 Code and UI improvements. Added push notifications option. 1.9.3 Added option for logging errors from REST API (can be disabled from the settings). Code improvements and bug fixes. 1.9.2.1 Bug fix when plugin is activated WP Screen is not set 1.9.2 1.9.1 1.9.0 1.8.6 1.8.5 1.8.4.1 1.8.4 1.8.3 1.8.2 1.8.1 1.8.0 1.7.5 1.7.4 1.7.3 1.7.3 1.7.2 1.7.1 1.7.0 1.6.1 1.6.0 1.5.1 1.5.0 1.4.0 1.3.0 1.2.0 1.1.1 1.1.0 1.0.1 1.0.0