tjdsneto

Admin Debug Tools makes it easy to manage your site’s logs and debug settings directly from the dashboard, without needing to edit backend files.
<h3>Debug Log</h3>
The Debug Log file is one of the most powerful tools for WordPress site admins and developers to troubleshoot issues on their site. But, accessing the debug log file can be a hassle, requiring backend file edits and SSH or FTP access.
Admin Debug Tools simplifies the process by giving you the power to manage your debug log from the WP Admin area.
With Admin Debug Tools, you can:
<ul>
<li>View a formatted version of the debug log file;</li>
<li>Monitor the latest log entries in near real-time (improvements to come);</li>
<li>Filter log entries by type (<code>Error</code>, <code>Warning</code>, <code>Notices</code>, <code>Deprecations</code>);</li>
<li>Search log entries by keyword with regex operators;</li>
<li>Save and/or clear your debug log file;</li>
<li>Download your debug log file;</li>
<li>Toggle debug mode on and off with a single click;</li>
<li>Edit the WP_DEBUG, WP_DEBUG_LOG, and other debug related constants;</li>
</ul>
<h3>WP Debugging</h3>
Admin Debug Tools makes direct edits to your <code>wp-config.php</code> file to enable and disable debug mode through the <code>WP_DEBUG</code> constant.
You have full control over the WP debug constants through the Config screen.
When you enable debug mode, WordPress will log errors, notices, and warnings to the debug log file. This can be helpful for troubleshooting issues on your site.
When you disable debug mode, WordPress will stop logging errors, notices, and warnings to the debug log file. This can be helpful for reducing server load and improving site performance.
https://developer.wordpress.org/advanced-administration/debug/debug-wordpress/
<h3>Future Features</h3>
Here are some of the features I have on my radar and plan to implement in future versions of Admin Debug Tools:
<ul>
<li>Debug log file rotation;</li>
<li>Option to ignore certain errors and reduce the noise in the log file;</li>
<li>Custom and usefull error pages for debugging;</li>
<li>Screen to debug database queries;</li>
<li>Debug helper functions to use in your code and print debug information to the log file;</li>
<li>Troubleshoot session mode to disable plugins and themes, and separate debugging from the main site;</li>
</ul>
<h3>Development</h3>
Admin Debug Tools is open source and we welcome contributions! You can find the source code and development instructions in our GitHub repository:
https://github.com/tjdsneto/admin-debug-tools
If you’re interested in contributing, please check the repository for development setup instructions, coding standards, and contribution guidelines.

Admin Debug Tools

Admin Debug Tools makes it easy to manage your site's logs and debug settings directly from the dashboard, without needing to edit backend files.

Mikhail Alferov

Error notifications help to immediately identify the causes of failures and quickly fix bugs so that the site runs smoothly and the business does not lose customers due to hidden errors.
If you are a developer, install the plugin to find out about specific errors or all errors in the PHP code, even if the error occurred in an unexpected place that could not be foreseen in advance.
The plugin allows you to configure the types of errors that you want to receive notifications about. Uncaught exceptions won’t break your site — they’re logged and made available for centralized custom handling via the <code>enot_exception_handler_should_exit</code> filter. Only real fatal errors stop the script, but you’ll still get full error details.
The notification will contain the type of error, the file name, and the line number where the error occurred or an uncaught exception was thrown, as well as a callback stack trace.
If you are the site owner, after installing the plugin, specify the email address of the developer who maintains the site in the plugin settings so that the plugin can start detecting and sending messages to the developer about serious errors that cause the business to lose orders or customers.
A notification with detailed information about the causes of the error will indicate to the programmer which plugin or theme caused the failure (which often goes unnoticed for a long time with automatic updates of plugins or themes), and the developer will fix the error before the failure is reported to customers.
It also helps to find out about critical errors even without access to the server logs or WordPress dashboard.
Note: The errors named *_NOTICE or *_WARNING are not too severe, but with others, the site breaks down and the user gets a negative experience.
<h4>Features</h4>
<ul>
<li>Customizable PHP error levels</li>
<li>Catch unhandled exceptions from try-catch blocks</li>
<li>Log stack traces, errors from @ operator, and JavaScript errors (Premium only)</li>
<li>Display user-friendly messages for critical PHP errors</li>
<li>Configurable email address for notifications</li>
<li>Multilingual support: RU, EN</li>
<li>Free updates to new versions (Premium only)</li>
<li>Error notifications via email</li>
<li>Error notifications via Telegram (Premium only)</li>
<li>JavaScript error alerts (Premium only)</li>
<li>Database error alerts (Premium only)</li>
</ul>

Error Monitor & Notifier

Receive notifications with details when PHP errors occur on your WordPress site.

Admin Debug Tools vs Error Monitor & Notifier