EdwardBock

Palasthotel

<p>Logging system.</p>
<ul>
<li>WP_Post metas</li>
<li>WP_User profiles</li>
<li>Taxonomies</li>
<li>Comments</li>
<li>Content User Relations</li>
</ul>
<h3>Arbitrary section</h3>


Process Log

Golemiq

Stoil Dobreff

<p>0 Day Analytics helps detect, inspect and respond to PHP and WordPress-level<br />
errors before they become production incidents. It is optimized for very<br />
large logs and common debugging/operational workflows.</p>
<p>Core capabilities:<br />
– Efficiently reads very large (GB-sized) error logs without full-file reads.<br />
– Error Log Manager with search, filtering, and code-context viewing.<br />
– Cron Manager: list, edit, run, delete scheduled tasks; advanced filters.<br />
– Transients Manager: safely list, edit, delete DB transients.<br />
– Requests Viewer: inspect outgoing HTTP requests.<br />
– Mail Logger & Composer: record email history, view attachments, compose/send.<br />
– SMTP configuration and test email support.<br />
– DB Table Manager: inspect/delete records across tables.<br />
– Server Info: admin-bar badges and dashboard widget (CPU, memory, disk).<br />
– Plugin Version Switcher, Code Snippets module, code viewer, CSV export and dark mode.<br />
– Recovery Mode: one-time recovery links with Slack/Telegram/other channels.<br />
– Randomize error-log filename for security.<br />
– PHP Snippets: generate and execute your own snippets when you need them. Shortcodes are supported.</p>
<h3>Short Description</h3>
<p>Real-time error insight and recovery for WordPress — lightweight, fast<br />
troubleshooting toolkit with log management, cron/transient/request viewers,<br />
mail logging/composition, SMTP, and a recovery mode.</p>
<h3>Requirements & Compatibility</h3>
<ul>
<li>WordPress 6.0+ (tested up to 6.9)</li>
<li>PHP 7.4+ (compatible with PHP 8+)</li>
<li>Not intended as a multisite recovery tool (see notes below)</li>
</ul>
<h3>Best practices & Security Notes</h3>
<ul>
<li>Keep log files outside the webroot when possible, or restrict access via<br />
server rules (.htaccess / nginx) to avoid public exposure.</li>
<li>Use a randomized or non-obvious filename for error logs if stored in webroot.</li>
<li>Limit plugin capabilities to trusted administrators (capability checks).</li>
<li>Sanitize and escape all output; use nonces for state-changing actions.</li>
<li>Secure SMTP credentials and prefer TLS/STARTTLS.</li>
<li>Set file permissions tightly (e.g., 600/640) and restrict ownership to the<br />
web server user.</li>
<li>Backup database/files before bulk delete or run operations.</li>
<li>Disable or restrict high-frequency background polling in high-load sites.</li>
</ul>
<h3>Usage notes & performance</h3>
<ul>
<li>Default error history stores the last 999 errors (adjustable via Screen<br />
Options) to preserve performance on high-volume logs.</li>
<li>No pagination on error logs by design to avoid repeated full-file reads.</li>
<li>Optional DB-based PHP error logger exists for environments without disk<br />
logging; consider DB size and retention.</li>
</ul>
<h3>Support & Notes</h3>
<ul>
<li>Recommended: secure log paths and consider randomizing filenames.</li>
<li>Disable unused modules to reduce footprint and attack surface.</li>
<li>Recovery mode is limited on multisite installs due to WP core behavior.</li>
<li>For bugs, feature requests or support, open an issue on the plugin page.</li>
</ul>
<p>Live preview and full details:<br />
https://wordpress.org/plugins/0-day-analytics/</p>


0 Day Analytics

0 Day Analytics helps detect, inspect and respond to PHP and WordPress-level

Process Log vs 0 Day Analytics