What this page is for #
Debug gives administrators a live, privacy-conscious snapshot of the plugin’s health and automation. At the top you’ll see color badges for API, WP-Cron, Memory, Summaries, and Bots, plus quick links to related areas. Nothing sensitive is exposed.
Head badges (live status at a glance) #
- API — shows OK, Warning, or Missing based on whether a valid OpenAI key is stored and when it was last checked. The key is masked (first 6…last 4) and accompanied by a human-readable “last check” message.
- WP-Cron — indicates if WordPress’ scheduler is On/Off, with a tip to use Sync CRON if schedules look empty.
- Memory — displays current PHP memory usage vs the limit with a color gauge (OK / Warn / Error).
- Summaries — shows how many published items already have an AI summary (and the site-wide coverage %).
- Bots — a running count of recorded bot visits for quick situational awareness.
A small legend under the action buttons clarifies the badge colors (OK, Warning, Error, Info).
Quick Actions (safe utilities) #
Buttons in this panel let you perform non-destructive checks and maintenance:
- 🔌 Test API Connection — verifies your OpenAI connection and updates the status badges accordingly.
- ⏱️ Check WP-Cron — confirms whether WP-Cron is enabled on your site. If it’s disabled in
wp-config.php, you’ll see a clear notice. - 🔄 Sync CRON — registers/refreshes the plugin’s scheduled tasks if they’re missing. A success notice confirms synchronization.
- ⚡ Force Run (summaries + scan) — immediately triggers the daily scan and summary generator (useful after bulk edits).
- 🗑️ Clear Logs — clears last error markers to help you start a fresh diagnostic run.
- 📥 Export CSV — downloads a timestamped CSV of the current diagnostic rows (Check, Status, Timestamp).
- 🧩 Apply wiring now (when available) — instantly re-applies feature wiring so toggled features are live without waiting.
Each button shows an inline notice, so you always know what happened.
Schedules (upcoming runs) #
This block lists the plugin’s scheduled events with both local and GMT timestamps for the next run. If the list is empty, use Sync CRON; you can also rely on a server-side cron if WP-Cron is disabled.
Health Details (table) #
A clean two-column table shows the checks and their current status:
- OpenAI API Key — “Configured” with a masked key, plus last check time and any message if validation failed. When valid, you’ll see a green Key valid note.
- WordPress CRON — Enabled/Disabled with guidance if disabled.
- Memory — usage/limit with the computed percentage and a color badge.
- AI Summaries — with-summary / total and the overall coverage % (with a helpful hint on how it was estimated).
- AI Bot Visits — total entries seen so far (a quick pulse, not a full log).
- Versions — your plugin version and WordPress version for support.
- Last AI Error — if any, displayed with a timestamp; “None” when everything is healthy.
The same data powers the CSV export, so you can archive snapshots or share them with your team.
Info (“i”) buttons & modal #
Each main block (About, Quick Actions, Schedules, Health) has a single “i” button that opens a lightweight modal with plain-English explanations. The copy is designed to be practical (what it checks, when to use it) without surfacing internal code.
Access & privacy #
This page is visible to administrators only. Sensitive data like API keys are masked and checks are shown as badges rather than raw logs.
Typical workflow #
- Scan badges to confirm API, cron, and memory look healthy.
- Open Schedules to ensure your automation runs are planned (or click Sync CRON).
- Use Quick Actions: test API, force a run after big updates, or clear markers before a fresh check.
- Export CSV and keep a weekly record for ops or support.
Good practices (buyer-friendly) #
- Treat Debug as your first stop when something feels off—badges and the Health table will usually point you to the root cause in seconds.
- If WP-Cron is disabled by your host or config, schedule the tasks server-side and use Sync CRON once to register them.
- Keep the API test green before content pushes; it saves time later.
