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

Matt Calvert

<p>This plugin issues an HTTP <code>410</code> response for URLs corresponding to content that has been permanently removed from your site. Originally created by Samir Shah, now maintained by Matt Calvert. When a post or page is deleted, the plugin logs the old URL and returns 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 Gone</code> response for resources that have been permanently removed. It informs search engines and crawlers that the content will not return, improving crawl efficiency and SEO clarity.</p>
<p>This plugin is actively maintained by Matt Calvert as a personal project, informed by previous professional experience with similar 410-handling logic. No proprietary or employer-owned code has been used.</p>


HTTP 410 (Gone) responses


Still working when tested but an update would be nice to avoid getting hacked or breakdown of site


still working

Sends HTTP 410 (Gone) responses for deleted content, telling search engines the page is permanently removed.

Admin Debug Tools vs HTTP 410 (Gone) responses