AnyWareX Debug Switch

AnyWareX Debug Switch provides an administrator interface for enabling and disabling WordPress debugging, viewing debug.log, downloading or clearing the log, and reviewing a severity summary.

Usage and safety

1. Run Preflight to verify three existing single-line literal debug definitions before the WordPress bootstrap.
2. Choose Enable Debug or Disable Debug to preview the current and proposed values.
3. Explicitly confirm the displayed changes. The configuration is reread, its hash compared, and definitions revalidated before one write attempt.
4. If the file changed, the preview expired, or the configuration is unsupported, create a new preview after reviewing the issue.

Only the three debug boolean tokens are edited. Missing definitions are never inserted. Additional ordinary constants and independent plugin settings are supported; uncertain PHP constructs are rejected. Configuration editing requires the local direct WordPress filesystem and a regular non-symlink file.

Direct writes are not atomic. A partial write can damage wp-config.php and stop WordPress. There is no automatic retry or rollback. Keep an independent protected backup outside the web root and inspect write errors externally. The plugin lock serializes plugin requests, but cannot prevent external file changes. A crashed request may leave an editor lock; see README.md for administrator recovery.

Previews expire after ten minutes, are user/session/blog-bound, and contain metadata only. A new preview replaces that user’s previous preview. No passwords, salts or configuration source are displayed or stored in preview metadata. Existing debug values and logs are not reverted by deactivation or uninstall.

Log Viewer, Summary, Download, Clear and Refresh remain available even when configuration editing is disabled. The managed log path is WP_CONTENT_DIR/debug.log. Protect logs at server level and disable debugging after use. WordPress.org review acceptance is not established by these changes.