WP Control
| 开发者 | |
|---|---|
| 更新时间 | 2025年7月21日 16:50 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 6.8.2 |
| 版权: | GPLv3 or later |
| 版权网址: | 版权信息 |
标签
下载
详情介绍:
- Read and analyze error logs even if the error log is gigabytes of size. (Only up to last 100 records are shown) Filtering by type is supported. The limitation is necessary for two reasons - first if there are more errors they are either not relevant or repeating ones, and second - that way your server will continue operate without any interruptions even if your log is few gigs of data.
- Enable or disable error logging directly from the WordPress dashboard.
- Manage large log files without performance degradation.
- Cron manager at the tip of your fingers (edit / delete / run).
- Transient manager - all (stored in the DB) transients (edit / delete).
- SQL tables manager - From here you can see and delete records from all the tables currently present in the Database.
- Environment type - There is the notification in the admin bar which tells you what is the selected type of the current environment you are on (can change it (the env type) from the settings or completely disable it)
- Plugin version switcher - Now you can change the plugin version directly from the admin Plugins page of your WordPress. Shows the path where main plugin file is located.
- Easily see where exactly error is thrown (where detected) Important: Description below does not apply for multisites, as this feature is not implemented by the WordPress core team for multisites! Recovery Mode link (still experimental) in the notification channels (if set) is added along with the fatal error. Wp core not always kicks in on fatality errors and this makes sure that you still have access to your website. 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.
- Handles gigabyte-sized error logs seamlessly.
- Option to enable or disable logging via the admin interface.
- Optimized for high-performance even with large log files.
- Provides insights into logged errors for efficient troubleshooting.
- Built-in fully functional Cron manager.
- Built-in fully functional Transients manager.
- Built-in Table manager.
- Built-in badge that shows you current environment type.
- Option to randomize the name of the error log file (security).
- Easily plugin version switch (the ones from official WP marketstore).
- Built-in dark mode.
安装:
- Download the plugin from the WordPress Plugin Directory.
- Upload the
0-day-analyticsfolder to the/wp-content/plugins/directory. - Activate the plugin through the 'Plugins' menu in WordPress.
- You will see new menu in admin bar (left hand) called
WP Control.
- Designed for both single and multi-site installations
- PHP8 fully compatible
屏幕截图:
常见问题:
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.
更新日志:
- Option to create transient. Option to truncate file but keep selected amount of last records. UI fixes and code optimizations. Late initialize to save resources.
- Silencing warnings coming from \is_file where restrictions / permissions are in place.
- Code optimizations. UI improvements. Bug fixes. Better source reporting.
- Providing editing option for Crons and Transients, code optimizations.
- Bug fixes and code optimizations. Telegram notifications support.
- Fixed problem with init hook called too early.
- Added control for more WP core constants as WP_DEVELOPMENT_MODE, SCRIPT_DEBUG, SAVEQUERIES etc. Added evnironment type show in the Admin bar (WP_ENVIRONMENT_TYPE). Added code viewer optins in the details section of error log. UI fixes and code optimizations.
- Lots of UI fixes and code showing optimizations.
- UI fixes related to the severity colors, added option to enable / disable the Admin bar live notifications, small code optimizations.
- Source view button in error log, PHP 7 problem fix.
- Logic improvements, menu name change, Slack notifications for fatal errors, speed optimizations.
- Lots of UI fixes and dark theme optimizations, small code fixes.
- UI / UX improvements and link fixes.
- Lots of bug fixes and UI / UX improvements.
- Lots of bug fixes and UI / UX improvements.
- Deprecation error fix.
- UI improvements. Fixed class reflection and method extraction in crons.
- Bug fixes and UI improvements. Transients manager added.
- Fixed bugs with error reader and improved memory management.
- Code and memory optimizations, new functionalities, features and UI changes in Cron manager.
- Fatal error on delete crons fixed.
- Lots of code optimizations and improvements. Cron list extending and optimizing. UI changes. Bug and functionality fixes.
- Code optimizations and functionality enhancements. Cron list extending and optimizing
- Code optimizations and functionality enhancements. More of WP deprecated events are now support. First version of Cron manager introduced (multisite is not fully supported yet and functionalities are limited)
- Code optimizations and functionality enhancements. Console now shows lines the way PHP error log stores them (not in reverse order). The new errors (count) is now shown next to the admin menu item. Admin bar size is reduced.
- :) .
- Fixed lots of problems, code optimizations and functionality enhancements.
- Small fixes and improvements.
- Initial release of Error Log Manager.