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.

Johnnie

<ul>
<li>NOTE: Please read installation instructions. WP Maximum Execution Time Exceeded plugin requires that you complete the website backup process. </li>
</ul>
<p>WP Maximum Execution Time Exceeded is a very simple and effective plugin. If you’re receiving the message “Maximum execution time of 30 seconds exceeded” or “Maximum execution time of 60 seconds exceeded,” this plugin is for you.</p>
<p>A time out means that the process you would like to complete is simply taking longer that the program will allow. The clock needs to be set for a longer time period. To address the problem of maximum execution time exceeded, WordPress Codex offers two solutions. One, edit the .htaccess file and two, edit the php.ini file. This plugin uses the first of the two suggestions. WP Maximum Execution Time Exceeded will add and delete the necessary code to the .htaccess file.</p>
<p>When WP Maximum Execution Time Exceeded is activated after installation, the plugin will write to the .htaccess file. To delete the code, simply deactivate the plugin. There is no administration page.</p>
<p>You do not have to delete the files to remove the code. When you’re ready to rewrite the code to the .htaccess file, simply activate it. This allows you to test your process with a longer timeout. It’s that simple! And of course, this plugin creates no load on your website. It’s so light weight; you’ll never know it’s there.</p>
<ul>
<li>NOTE: All feedback and suggestions are welcome. I am constantly looking for ways to improve and upgrade WP Maximum Execution Time Exceeded. Please contact me with your ideas for a better plugin.</li>
</ul>


WP Maximum Execution Time Exceeded

I know enough to edit .htaccess files but couldn't manage to extend the execution time without creating an Error 500.

One click and this did the job...and taught me how to do it manually in future ;o)

Perfect

Did you receive a message, "Maximum execution time of 30 seconds exceeded?" Not anymore. Just Plug'n-Play. It's that easy!

Admin Debug Tools vs WP Maximum Execution Time Exceeded