Skip to main content

Built-In Debug System

Find and fix issues without touching server configs.
ASI’s built-in Debug System gives Tribulant Newsletter users instant visibility — right inside WordPress.
No SSH. No editing php.ini or my.cnf. Toggle on, reproduce the problem, get answers.

🔌 Toggle on. 🔎 Pinpoint. 🛠️ Resolve.

✨ Why ASI Debug Beats Manual Troubleshooting

One-click enable

No server reboots, no php.ini edits.

Purpose-built insights

Focused on sending, exports, cron, and headers.

Guided visibility

Timestamps, request IDs, user actions — the story makes sense.

Self-cleaning

Easy purge and retention to keep storage lean.

Role-aware

Admins by default; optional Editor access.

No vendor lock-in

Standard CSV/TXT logs to archive or share.

🧰 What ASI Debug Captures (Out of the Box)

  • 🐘 PHP errors & notices — file, line, function, stack context.
  • 🗄️ SQL activity snapshots — heavy queries tied to exports/list updates.
  • ⏰ WP-Cron timeline — prove scheduled tasks fired when expected.
  • ✉️ Mail header context — List-Unsubscribe, abuse contacts, sender identity.
  • 📁 Export/Report events — who pulled what, when, and where it saved.
  • 🔌 Plugin signals — feature toggles, capability checks, security nonces.

🔄 No Config Edits — Just Turn It On

Forget SSH. Nothing to tweak in php.ini, my.cnf, or Apache/Nginx. Toggle the debug layer from the ASI admin, reproduce the bug, then review concise logs scoped to your newsletter workflows.

  • 🟢 Enable/Disable instantly — safe for production.
  • 📉 Low overhead — designed for short capture windows.
  • 📂 Clear storage paths — /wp-content/uploads/reports/ and /uploads/reports/export-logs/.

👀 The Viewer Experience

  • 🔎 Keyword search — find by email, list, file, or function.
  • 🧭 Time-range filters — zoom in on the exact failure window.
  • 🧱 Grouped events — errors, SQL, cron, and mail headers.
  • 📤 One-click export — download current view for tickets/support.
  • 🧹 Purge & retention — trim old logs and set retention defaults.

🛡️ Security, Privacy & Access Control

  • 🔒 Role-based access — Admin-only by default; allow Editors if needed.
  • 🙈 Redaction — sensitive tokens/keys masked in exports.
  • 🚪 Non-public storage — upload rules prevent accidental exposure.
  • 🧾 Audit trail — who enabled debug, when, and what was purged.

🚀 Common Wins with ASI Debug

  • 📨 Deliverability checks — confirm List-Unsubscribe and abuse headers.
  • 🧮 Export performance — pinpoint heavy queries slowing CSVs.
  • ⏱️ Cron misses — prove scheduled jobs fired (or didn’t).
  • 🔗 Plugin conflicts — spot third-party hooks interfering with flows.
  • 🧱 Permission errors — identify capability/nonce failures quickly.

📚 Real-World Use Cases

• An agency turns on debug during a send, confirms cron timing & headers, and ships the post-mortem in 10 minutes.
• An eCommerce brand finds a slow meta query during export and fixes it with a simple index.
• A publisher validates unsubscribe behaviour after a template change with live header capture.
• A CRM manager proves a third-party plugin is blocking a save action — conflict resolved.

Open ASI Debug

❓ FAQ: ASI Debug

Do I need SSH or to edit config files?

No. Toggle it on, reproduce the issue, review the logs, then toggle it off. No php.ini, no my.cnf, no restarts.

Where are logs stored?

Under /wp-content/uploads/reports/ and /uploads/reports/export-logs/ with clear retention controls.

Will this slow down my site?

It’s lightweight and designed for short capture windows. Capture the event, then disable it when finished.

Can Editors access the viewer?

Admins by default. Editor access is optional via settings if you want assistance in troubleshooting.

Can I export logs for support?

Yes. Use the export button in the viewer to attach filtered logs to tickets or share with your sysadmin.