WPsigner provides two operational screens:
- WPsigner → More → System Status — diagnostics, health checks, and repair actions.
- WPsigner → More → Storage & Retention — storage usage, cloud backup status, retention, purge, and full deletion.
Both screens currently require a WordPress Administrator with manage_options.
System Status
Section titled “System Status”System Status checks:
- WordPress, PHP, and extension requirements
- Plugin compatibility
- Secure storage path, permissions, and size
- WP-Cron configuration and scheduled WPsigner jobs
- Email/SMTP delivery
- Timezone
- PDF engine and the active Signed PDF fonts pack (if installed)
- Database tables
- Webhooks and REST API
- Security-related configuration
Use Copy Debug Info when contacting support. Review the copied text before sharing it because environment reports can include domain, plugin, and server details.
Scheduled jobs
Section titled “Scheduled jobs”WPsigner relies on WP-Cron for background work:
| Hook | Schedule | Purpose |
|---|---|---|
wps_send_automatic_reminders | Hourly | Send due signing reminders |
wps_check_expirations | Hourly | Expire documents whose due date passed |
wps_auto_purge_storage | Daily when configured | Remove eligible local completed PDFs |
wps_ots_check_pending | When OpenTimestamps is enabled | Check pending timestamp proofs |
wps_api_logs_purge | Daily | Purge old API request logs |
Repair missing jobs
Section titled “Repair missing jobs”Click Fix Cron Jobs in System Status. WPsigner recreates the schedules appropriate for the enabled features.
If DISABLE_WP_CRON is enabled, configure a real server cron to call wp-cron.php. Repairing the schedule does not make WordPress cron execute when the hosting environment never triggers it.
Secure storage
Section titled “Secure storage”System Status displays the active secure-storage directory and whether it is writable. WPsigner normally stores files below the WordPress uploads area using protected folders and secure-storage controls.
Do not make the storage folder publicly browsable. Back up both:
- The WordPress database, which contains document, signer, field, audit, and configuration records.
- The WPsigner file storage, which contains document files.
A file-only or database-only backup is not a complete WPsigner recovery plan.
Retention settings
Section titled “Retention settings”Open Storage & Retention to configure:
| Setting | Options |
|---|---|
| Automatic purge | On / Off |
| Retention period | Forever, 30, 60, 90, 180, or 365 days |
Automatic purge removes only local PDFs for completed documents older than the selected period and only when WPsigner has recorded a cloud backup for that document. Audit records, signatures, and document database records remain.
Choosing a retention period does not guarantee deletion of every document file. Files without a confirmed cloud backup are skipped to prevent accidental loss.
Storage actions
Section titled “Storage actions”Purge Completed PDFs
Section titled “Purge Completed PDFs”- Requires typing
DELETE. - Removes eligible local completed PDFs that have a cloud backup.
- Keeps document records, audit data, and cloud copies.
Delete Drafts & Cancelled
Section titled “Delete Drafts & Cancelled”- Requires typing
DELETE. - Removes draft/cancelled records and their local files.
- Use only after confirming those documents are no longer needed.
Push to Cloud
Section titled “Push to Cloud”Scans completed PDFs that lack a recorded cloud backup and uploads them through the configured provider. Check the result before enabling automatic purge.
Delete Everything
Section titled “Delete Everything”The action requires:
- An acknowledgement checkbox.
- The exact phrase
DELETE ALL. - Keeping the browser tab open while chunked file deletion finishes.
It removes documents, signers, fields, audits, templates, campaigns, payments, and related operational records. It preserves WPsigner options and license data. Remote files already stored with a cloud provider are not deleted automatically.
Create and test a full backup before using it. If the browser closes or a timeout interrupts the process, reopen the screen and run the cleanup again after verifying what remains.
Operational checklist
Section titled “Operational checklist”Weekly
Section titled “Weekly”- Review System Status for new warnings.
- Check failed emails, webhook deliveries, and cron events.
- Confirm available disk space.
Monthly
Section titled “Monthly”- Test a document from upload through final PDF.
- Verify a recent database and file backup can be restored.
- Review API keys, webhook endpoints, and inactive integrations.
- Confirm cloud backup counts before purging local PDFs.
Before an upgrade
Section titled “Before an upgrade”- Back up database and WPsigner files.
- Record the current System Status report.
- Update in staging when possible.
- Test PDF generation, signing, email, cron, and integrations.
Troubleshooting
Section titled “Troubleshooting”Cron jobs are missing
Section titled “Cron jobs are missing”Use Fix Cron Jobs. If they disappear again, check object caching, cron-management plugins, DISABLE_WP_CRON, and the hosting control panel’s scheduled task.
Automatic purge does not remove files
Section titled “Automatic purge does not remove files”Confirm automatic purge is on, the period is not Forever, the document is completed and old enough, and a cloud backup is recorded.
Storage is not writable
Section titled “Storage is not writable”Check the exact path shown in System Status, filesystem ownership, hosting quotas, and security rules. Avoid setting globally writable permissions.
Emails fail
Section titled “Emails fail”Use the System Status email test, verify SMTP credentials and DNS, and inspect the mail provider’s logs.
Wordfence blocks WPsigner actions
Section titled “Wordfence blocks WPsigner actions”Use the compatibility information in System Status to allowlist the reported WPsigner AJAX actions, then retest. Do not disable the firewall globally.
Delete Everything stops partway
Section titled “Delete Everything stops partway”Keep the tab open and retry the action. Check PHP execution limits and server logs. Cloud backups remain at the provider until removed there.