=== 0 Day Analytics ===
Contributors: sdobreff
Tags: error log, debug, cron, transients, mail log
Requires at least: 6.0
Tested up to: 6.9
Requires PHP: 7.4
Stable tag: 4.5.0
License: GPLv3 or later
License URI: https://www.gnu.org/licenses/gpl-3.0.txt

== Short Description ==
Real-time error insight and recovery for WordPress — lightweight, fast
troubleshooting toolkit with log management, cron/transient/request viewers,
mail logging/composition, SMTP, and a recovery mode.

== Description ==
0 Day Analytics helps detect, inspect and respond to PHP and WordPress-level
errors before they become production incidents. It is optimized for very
large logs and common debugging/operational workflows.

Core capabilities:
- Efficiently reads very large (GB-sized) error logs without full-file reads.
- Error Log Manager with search, filtering, and code-context viewing.
- Cron Manager: list, edit, run, delete scheduled tasks; advanced filters.
- Transients Manager: safely list, edit, delete DB transients.
- Requests Viewer: inspect outgoing HTTP requests.
- Mail Logger & Composer: record email history, view attachments, compose/send.
- SMTP configuration and test email support.
- DB Table Manager: inspect/delete records across tables.
- Server Info: admin-bar badges and dashboard widget (CPU, memory, disk).
- Plugin Version Switcher, Code Snippets module, code viewer, CSV export and dark mode.
- Recovery Mode: one-time recovery links with Slack/Telegram/other channels.
- Randomize error-log filename for security.
- PHP Snippets: generate and execute your own snippets when you need them. Shortcodes are supported.
- WP Hooks capturing / monitoring - very powerful tool to capture and monitor different (defined or custom) WP hooks (actions and filters). You can see selected or added hook output (result of triggering).

== Installation ==
1. Place the `0-day-analytics` folder into `/wp-content/plugins/` (or install via
    the Plugins screen / WP CLI).
2. Activate on the WordPress Plugins screen.
3. Visit "0 Day" in the admin menu and configure settings.
4. Recommended: test on staging before enabling on production.

== Requirements & Compatibility ==
- WordPress 6.0+ (tested up to 6.9)
- PHP 7.4+ (compatible with PHP 8+)
- Not intended as a multisite recovery tool (see notes below)

== Best practices & Security Notes ==
- Keep log files outside the webroot when possible, or restrict access via
  server rules (.htaccess / nginx) to avoid public exposure.
- Use a randomized or non-obvious filename for error logs if stored in webroot.
- Limit plugin capabilities to trusted administrators (capability checks).
- Sanitize and escape all output; use nonces for state-changing actions.
- Secure SMTP credentials and prefer TLS/STARTTLS.
- Set file permissions tightly (e.g., 600/640) and restrict ownership to the
  web server user.
- Backup database/files before bulk delete or run operations.
- Disable or restrict high-frequency background polling in high-load sites.

== Usage notes & performance ==
- Default error history stores the last 999 errors (adjustable via Screen
  Options) to preserve performance on high-volume logs.
- No pagination on error logs by design to avoid repeated full-file reads.
- Optional DB-based PHP error logger exists for environments without disk
  logging; consider DB size and retention.

== Screenshots ==
1. Error Log Overview
2. Settings Page
3. Import / Export Settings
4. Cron Manager
5. Transients Manager
6. Plugin Version Switcher
7. Table Manager
8. Table Operations View
9. Request Details

== FAQ ==
Q: Why only the last 999 errors?
A: Balances useful context against expensive full-file reads. Adjustable.

Q: Why no pagination for errors?
A: Pagination would require full-file reads repeatedly and is inefficient
    for very large logs.

Q: How do I enable/disable logging?
A: 0 Day → Settings → toggle logging. Prefer toggling on staging first.

Q: Is this safe to run on multisite?
A: Recovery mode has core multisite limitations — use caution and test.

== Changelog ==

= 4.5.0 =
* Bug fixes and code improvements. Hooks module introduced.

= 4.4.1 =
* Small bug fixes and File Manager improvements.

= 4.4.0 =
* Now the Table module has the option to insert records.

= 4.3.1 =
* Maintenance update - fixes problem with saving snippet for the first time.

= 4.3.0 =
* Maintenance, WP 6.9 compatibility, performance tweaks, added Code Snippets
  module.

= 4.2.1 =
* Minor fixes and environment compatibility improvements.

= 4.2.0 =
* New filters and editor/file tools.

= 4.1.1 =
Very small maintenance update - optimizations and bug fixes.

= 4.1.0 =
Small maintenance update - code optimizations and bug fixes.

= 4.0.0 =
Addresses different kinds of problems. Code optimizations. DB table edit introduced. File editor (still experimental) introduced.

= Earlier versions =
* Progressive additions: mail logger, DB error table, cron/transient managers,
  CSV export, recovery mode, plugin version switcher, UI/dark mode
  improvements.

== Support & Notes ==
- Recommended: secure log paths and consider randomizing filenames.
- Disable unused modules to reduce footprint and attack surface.
- Recovery mode is limited on multisite installs due to WP core behavior.
- For bugs, feature requests or support, open an issue on the plugin page.

Live preview and full details:
https://wordpress.org/plugins/0-day-analytics/