| 开发者 | sanestly |
|---|---|
| 更新时间 | 2026年10月1日 02:29 |
| PHP版本: | 8.1 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
sanestly-payment-reminders folder to /wp-content/plugins/, or install the ZIP via Plugins → Add New → Upload Plugin.No. Automation defaults to off. Activation does not send emails or schedule reminders. Historical orders before the processing cutoff stay excluded until you preview and explicitly backfill.
Future reminder actions for that order are cancelled. Paid orders are not reminded again.
You choose eligible payment methods in Settings. Use “all methods” or a specific allow/deny list of gateway IDs available on your store.
Yes. The order screen includes manual send, pause, resume, and cancel actions. Manual send uses the same eligibility and duplicate-protection pipeline as scheduled sends.
Yes. The Email tab includes Test Email. Test sends never mutate order meta, schedules, or statistics.
Yes. The plugin is written against WooCommerce order CRUD and has been exercised with HPOS on and off.
Yes. Order language can drive reminder copy with Polylang or WPML. Polylang has been live-tested; WPML has automated coverage of the integration path.
Backfill schedules reminders for older unpaid orders that match your rules after you confirm a dry-run preview. It runs in background batches and requires an explicit confirmation checkbox.
Scheduled reminder actions are cleared on deactivation. Plugin settings remain so you can reactivate later. Uninstall removes plugin options and scheduled actions; order meta (_pmrwc_*) is left in place by design.
Plugin settings, event log entries, stats cache, backfill state, temporary send locks, Action Scheduler jobs in group pmrwc, and order meta keys prefixed with _pmrwc_ (reminder state, language markers, and related flags).
No. The free plugin does not phone home, collect telemetry, or call Sanestly servers.