Flip the toggle
Debug mode rewrites the flags for that one sandbox. Nothing to edit by hand.
Flip debug flags per site from the dashboard and read debug.log right next to them. No FTP, no wp-config surgery.
debug.log · live
[09:14:02] PHP Notice: gallery_shortcode…
Fatal error: Uncaught TypeError
in class-gallery-block.php:217
[09:14:02] Stack trace: #0 render()…
Debug mode rewrites the flags for that one sandbox. Nothing to edit by hand.
Click through the broken flow on the live site while the log records everything.
The viewer sits right next to the toggles notices, warnings, fatals, stack traces.
Deploy the fix, confirm the log is clean, turn debug off. Or just reset the site.
WP_DEBUG
Turns on WordPress’s debug machinery for the sandbox the thing you never dare enable on production.
WP_DEBUG_LOG
Notices, deprecations, fatals captured to debug.log and readable in the dashboard or over SSH.
WP_DEBUG_DISPLAY · SCRIPT_DEBUG
Show errors on-page when that’s faster, and switch to unminified core scripts when chasing JS.
A deprecation that only fires on 8.3? Switch the sandbox’s PHP version, reproduce, and read the notice in the log same site, same data.
php version
[09:20:11] switched php 8.1 → 8.3
Deprecated: dynamic property in MyPlugin\Cache
…there it is.
Reset returns the sandbox to a clean slate; flip debug back on with one click when you need it again.
Yes use sandywp ssh <name> and tail -f wp-content/debug.log, or mount the files locally and open it in your editor.
Yes. Toggling debug and reading debug.log are exposed over MCP and the CLI, so an assistant can close the write → deploy → debug loop alone.
You can it’s your sandbox. The toggle is simply faster and reversible without remembering what you changed.
Free account, debug toggle, live log seconds from now.