Free diagnostics · Health Checks and Logs
Check your installation. Trace recent events. Solve problems with better evidence.
SitePublisher AI brings essential installation checks and structured event logs into one administrator-only workspace. Confirm that the plugin can run correctly, then narrow recent activity by day, severity or source when something needs attention.
Included in Free · Administrator-only access · Recognized sensitive context fields are redacted
A clear technical baseline
See whether the SitePublisher AI foundation is ready
Open the Health tab in Platform Settings for a fresh status overview. Required checks receive a clear Passed or Failed result, while informational findings remain separate from problems that can prevent the plugin from starting completely.
PHP and WordPress versions
Confirm the active PHP and WordPress versions against the minimum requirements of the installed SitePublisher AI release.
Required PHP extensions
Check that cURL, JSON, mbstring and OpenSSL are available—the server components required by the current plugin build.
Core class loading
Verify that the SitePublisher AI autoloader can find the application classes and services included with the installation.
Writable storage
See whether the plugin storage directory exists and is writable. SitePublisher AI attempts to create a missing directory when possible.
Writable log directory
Confirm that structured events can be written to the protected log directory before you need those records for diagnosis.
Versions and legacy detection
Review installed component versions and see an informational notice when a legacy Marketing Hub installation is detected during migration.
Structured evidence, not guesswork
Move from the health summary to the exact events you need
Health and Logs sit beside the OpenAI API, Platform Settings and Prompts tabs. The log viewer loads the newest matching entries first and lets you investigate without opening files on the server.
Use the instant search for messages, sources or structured context. Optional auto refresh can reload the current view every 15, 30 or 60 seconds while you reproduce a problem.
Open Platform Settings → Health
Start with the overall readiness message, then read each check, status and detail in the results table.
Resolve required failures first
A failed PHP, WordPress, extension, autoloader or directory check can prevent SitePublisher AI from starting completely. Administrators also receive a WordPress notice when a required check fails.
Switch to the Logs tab
Select one of the daily log files and filter by Debug, Info, Notice, Warning, Error or Critical.
Choose the right amount of detail
Load the newest 50, 100, 250 or 500 matching entries. Summary cards show loaded entries, warnings, errors and distinct sources.
Inspect structured context
Expand an entry to review its timestamp, source, message, site and limited request context, then use that evidence in the relevant troubleshooting step.
Available in both editions
Keep the diagnostic foundation when your workflow grows
Health Checks and Logs are part of Platform Settings in SitePublisher AI Free. The same administrator tools remain available after upgrading to Pro.
Complete installation diagnostics
Check the current WordPress installation and inspect structured SitePublisher AI events without a subscription.
- All required installation checks
- Component versions and legacy detection
- Daily log-file and severity filters
- Live search and optional auto refresh
The same tools beside Pro workflows
Everything in Free remains available while Pro adds multi-site publishing, automation, scheduling and reporting elsewhere in the workspace.
- No separate diagnostic upgrade required
- The active edition and license state accompany core startup context
- Source labels keep structured events distinguishable
- Use alongside Queue, Analytics and multi-site controls
Protected and deliberately scoped
Useful technical context with sensible safeguards
The logger is designed for operational diagnosis inside WordPress administration. It limits and sanitizes recorded values, masks recognized credential fields and protects its storage directory against direct web access.
Administrators only
- Health and Logs require the manage_options capability
- Entries are reviewed inside WordPress admin
- The log directory receives web-access protection files
Sensitive context is masked
- Recognized API-key, authorization and password fields are redacted
- Secret, token and cookie fields are also masked
- Messages and context strings are sanitized and length-limited
Installation health, not every connection
- Health checks do not validate an OpenAI API key
- They do not test remote WordPress websites
- They do not replace WP-Cron or queue troubleshooting
Turn each signal into the right next step
Know where to look—and who can fix it
Ask your hosting provider about unsupported PHP or WordPress versions, missing extensions and unwritable directories. Reinstall the complete plugin package if core classes cannot load. For API authentication, remote website connections, queues or scheduled publication, use the dedicated configuration and troubleshooting guides.
Frequently asked questions
Health Checks and Logs
Practical answers about access, checks, log files, sensitive information and diagnostic scope.
Are Health Checks and Logs included in Free?
Yes. Both tabs are included in Platform Settings for SitePublisher AI Free and remain available in Pro.
What does the Health tab check?
It checks the PHP and WordPress versions, required PHP extensions, core class loading and whether the storage and log directories exist and are writable. It also lists component versions and reports legacy-installation detection as information.
Does Health test my OpenAI key or connected websites?
No. Use the connection test in OpenAI API configuration for the API key and the dedicated website connection controls for a remote WordPress website. Health focuses on the local installation foundation.
What information can a log entry contain?
A structured entry can contain a timestamp, severity level, source, message, context, site URL and limited request information such as method and whether the request was admin, AJAX or cron.
Can logs contain passwords or API keys?
Recognized sensitive keys in structured context—such as api_key, authorization, password, secret, token and cookie fields—are replaced with a redacted marker before writing. As a general security rule, never place credentials in ordinary messages or URLs.
How are log files retained?
The current version writes one structured log file per UTC day. The viewer does not automatically delete those daily files, so retention should be included in your normal hosting and privacy-maintenance policy.
Give every SitePublisher AI installation a clear diagnostic starting point.
Start free, confirm the technical foundation and use structured logs when a workflow needs closer inspection.