Brad Parbs

Any <code>WPENV_</code> prefixed variables in the <code>.env</code> will be used to override the WordPress options. For example, if you’d like to set a specific environment to “Discourage search engines from indexing this site”, you can add <code>WPENV_BLOG_PUBLIC=0</code> to your <code>.env</code> file.
<ul>
<li>
Any option in the <code>wp_options</code> table or retrieved by <code>get_option()</code> can be set this way.
</li>
<li>
You can define keys either as <code>WPENV_BLOGDESCRIPTION</code> or as <code>WPENV_blogdescription</code>, both will work.
</li>
<li>
If you’d like to define the location of your <code>.env</code> file, rather than the plugin looking for it, you can filter <code>dotenv_location</code> to be a directory path.
</li>
<li>
You can also change the <code>WPENV_</code> prefix by filtering <code>dotev_key_prefix</code> to be a different prefix.
</li>
</ul>

dotenv

A WordPress plugin to set WordPress options from a .env file.

Lukman Nakib

A comprehensive debugging toolkit for WordPress developers and site administrators. This plugin gives you complete control over WordPress debugging without editing wp-config.php files or using FTP.
<h4>Quick Demo</h4>
<iframe loading="lazy" class="youtube-player" width="750" height="422" src="https://www.youtube.com/embed/D4K5zsLnILw?version=3&rel=1&showsearch=0&showinfo=1&iv_load_policy=1&fs=1&hl=en-US&autohide=2&wmode=transparent" allowfullscreen="true" style="border:0;" sandbox="allow-scripts allow-same-origin allow-popups allow-presentation allow-popups-to-escape-sandbox"></iframe>
<h4>Key Features</h4>
<ul>
<li>WP-CLI Style Terminal: Execute WordPress commands directly from your browser with syntax highlighting and auto-completion</li>
<li>Database Tools: Run SQL queries, view table structures, and optimize your database (super admin only)</li>
<li>Debug Constants Manager: Toggle all WordPress debug constants with a single click</li>
<li>Log Viewer: View, filter, and analyze debug logs with syntax highlighting and error categorization</li>
<li>Query Inspector: Examine database queries with SAVEQUERIES support</li>
<li>Email Notifications: Get alerts when new errors appear in your logs</li>
<li>Safe Mode: Quickly disable all plugins except selected ones for troubleshooting</li>
<li>Custom Log Paths: Set custom log file locations with filter support</li>
</ul>
<h4>Debug Constants Available</h4>
<ul>
<li>WP_DEBUG – Default Value: true – Enables WordPress debug mode</li>
<li>WP_DEBUG_LOG – Default Value: true – Saves all errors to a debug.log file</li>
<li>SCRIPT_DEBUG – Default Value: false – Uses development versions of core JS and CSS files</li>
<li>WP_DEBUG_DISPLAY – Default Value: false – Controls whether debug messages display on screen</li>
<li>SAVEQUERIES – Default Value: false – Saves database queries for analysis</li>
</ul>
<h4>Developer Tools</h4>
<ul>
<li>Terminal Commands: Use WP-CLI style commands like <code>wp core version</code> or <code>wp plugin list</code></li>
<li>Database Explorer: Run SELECT queries and view results in a formatted table</li>
<li>Stack Trace Analysis: Visualize error stack traces for easier debugging</li>
<li>Hook Inspector: View all registered hooks and their callbacks</li>
<li>Environment Detection: Development features are automatically hidden in production</li>
</ul>
<blockquote>
Developer API: Apply custom filters like <code>apply_filters('wp_debuglog_log_file_path', $file);</code> to extend functionality
</blockquote>
Please note: Constant values will be restored on plugin deactivation as it was before activating the plugin.

Debug Log – Manager Tool

Awesome!

Helps us a lot with development :)

it's exactly what i am after for. instead of connecting to ftp, opening wp-config.php, editing the constants, saving, uploading, reloading site, opening debug.log and deleting it and so on … you simple enable the toggle and look into the logs right in wordpress with nice styling so you can easily distinguish between warning and errors. 
in the future i would like to see more toggles for instance for WP_DEBUG_DISPLAY. for some reason this is missing?! 

simple but good


My go-to debugging plugin for 500 internal server errors and anything that's trickier to track. Good job.


Super useful


Fantastic plugin with an easy interface for browsing. Thank you so much for making it available for free!


Fantastic & easy to use.


The plugin used to work very well, but with the latest update the debug log cannot be cleaned. This has been reported as a bug 2 months ago with no response and no other update. This is why I'm giving the plugin 2 stars. There are other plugins that work better.



--- EDIT ---



Recently I tested the plugin again and it has improved by a lot. I see new functions and - so far - zero bugs. Well done. I improve my rating. Keep up the good work.


Much improved over time

The "Debug Log Config Tool" simplifies debugging. Toggle logging,queries , view levels, clear logs from dashboard.

dotenv vs Debug Log – Manager Tool