tjdsneto

<p>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.</p>
<h3>Debug Log</h3>
<p>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.</p>
<p>Admin Debug Tools simplifies the process by giving you the power to manage your debug log from the WP Admin area.</p>
<p>With Admin Debug Tools, you can:</p>
<ul>
<li>View a formatted version of the debug log file;</li>
<li>Monitor the latest log entries in near real-time <em>(improvements to come)</em>;</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>
<p>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.</p>
<p>You have full control over the WP debug constants through the Config screen.</p>
<p>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.</p>
<p>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.</p>
<p>https://developer.wordpress.org/advanced-administration/debug/debug-wordpress/</p>
<h3>Future Features</h3>
<p>Here are some of the features I have on my radar and plan to implement in future versions of Admin Debug Tools:</p>
<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>
<p>Admin Debug Tools is open source and we welcome contributions! You can find the source code and development instructions in our GitHub repository:</p>
<p>https://github.com/tjdsneto/admin-debug-tools</p>
<p>If you’re interested in contributing, please check the repository for development setup instructions, coding standards, and contribution guidelines.</p>


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.

Samir Shah

<p>This plugin will issue a HTTP <code>410</code> response to requests for articles that no longer exist on your blog. When you delete a post or page, it records the URL for that page and issues a <code>410</code> response when that URL is requested. You can also manually manage the list of obsolete URLs.</p>
<p>The <a href="http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.4.11" rel="nofollow ugc">HTTP Specification</a> defines the <code>410</code> response header for use when a resource has been permanently removed. It informs robots visiting your site that the requested content has gone, and that they should stop trying to access it.</p>
<p>If you come across any bugs or have suggestions, please use the plugin support forum. I can’t fix it if I don’t know it’s broken! Please check the <a href="https://wordpress.org/extend/plugins/wp-410/faq/" rel="ugc">FAQ</a> for common issues.</p>


410 for WordPress

A plugin that sends HTTP 410 (Gone) responses to requests for articles that no longer exist on your blog.

Admin Debug Tools vs 410 for WordPress