=== DebugZen ===
Contributors: parag44
Tags: debugging, debug log, wp-config, developer tools
Requires at least: 5.8
Tested up to: 7.1
Requires PHP: 7.4
Stable tag: 1.0.0
License: GPLv2 or later
License URI: https://www.gnu.org/licenses/gpl-2.0.html

Debug WordPress without FTP. Safely toggle debug constants in wp-config.php without risking syntax errors, and inspect or clear logs right from your dashboard.

== Description ==

DebugZen gives administrators a focused dashboard screen for managing WordPress debugging settings and inspecting the debug log.

The plugin uses the WP Config Transformer library to read, add, and update these constants in `wp-config.php`:

* `WP_DEBUG`
* `WP_DEBUG_LOG`
* `WP_DEBUG_DISPLAY`

DebugZen does not use string replacement to modify those constants.

The Debug Log viewer reads only the latest 1,000 lines to avoid loading a large log into memory. Administrators can also clear the active debug log from the same screen.

Features include:

* Toggle WordPress debugging settings from Tools > DebugZen.
* Add missing debug constants or update existing values through WP Config Transformer.
* View the latest 1,000 debug-log lines.
* Clear the debug log securely.
* Restrict every action to administrators with the `manage_options` capability.
* Protect setting and log actions with WordPress nonces.
* Display clear errors when `wp-config.php` or the log is not writable.

Debug settings can expose sensitive technical information. Disable on-screen error display on production sites and protect access to log files at the web-server level.

= Third-party libraries =

DebugZen includes WP Config Transformer by the WP-CLI Development Group. It is distributed under the MIT License. Its license is included at `vendor/wp-cli/wp-config-transformer/LICENSE`.

This plugin does not contact external services, collect telemetry, or load remote executable code.

== Installation ==

1. Upload the `debugzen` folder to `/wp-content/plugins/`, or install the plugin ZIP from Plugins > Add New > Upload Plugin.
2. If installing from source without the bundled `vendor` directory, run `composer install --no-dev --optimize-autoloader` inside the plugin directory.
3. Activate DebugZen through the Plugins screen in WordPress.
4. Open Tools > DebugZen.
5. Ensure `wp-config.php` is writable before saving changes. Restore restrictive permissions after configuration if required by your hosting environment.

== Frequently Asked Questions ==

= Does the plugin directly edit debug constants with string replacement? =

No. It uses WP Config Transformer to locate, read, add, and update debug constants safely.

= Why can I not save settings? =

The plugin must be able to read and write `wp-config.php`. File ownership, permissions, or host-level restrictions may prevent changes.

= Where is the debug log? =

By default, WordPress writes the log to `wp-content/debug.log`. If `WP_DEBUG_LOG` contains a custom path, DebugZen uses that path.

= Does DebugZen send data anywhere? =

No. DebugZen has no telemetry, analytics, external API connection, or remote code loading.

== Screenshots ==

1. The DebugZen dashboard screen under Tools > DebugZen showing WP_DEBUG toggle switches and the live debug log viewer.

== Changelog ==

= 1.0.0 =

* Initial release.
* Added secure controls for `WP_DEBUG`, `WP_DEBUG_LOG`, and `WP_DEBUG_DISPLAY`.
* Added a memory-conscious debug-log viewer and secure clear-log action.
* Added WP Config Transformer integration.

== Upgrade Notice ==

= 1.0.0 =

Initial release.
