| 开发者 | lukeaxiomflow |
|---|---|
| 更新时间 | 2026年10月23日 09:38 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
wp ofrw status --format=json). Event log history is your setting, defaulting to keep everything - housekeeping, not a tier: no build removes the bound for you.
Read-only by design. The plugin never changes gateway settings, orders, or queue entries. The only thing it ever writes is a webhook's status - when you click "Re-enable", or when you switch on auto-recovery yourself (off by default).
Quiet by design, too. Nothing this plugin has to say appears outside its own screen: no dashboard banners, no cross-admin notices, no nags. Findings reach you by email, in Site Health, on the WP-CLI command, and on the plugin's own page. The one exception is a single notice on the Plugins screen if WooCommerce is not active, which disappears the moment you activate it.
Pro adds Slack/webhook alert channels, a REST status endpoint for agency dashboards, a white-label client report, and a WooCommerce Subscriptions renewals watch (renewal due, no charge attempt). The free version is fully functional and stays that way.
Known limitations (honest ones)
woocommerce_email_sent signal. It verifies emails were generated and handed to your mailer; it cannot see the receiving inbox.No. Checks are scheduled background reads (status columns, counts) on a 15-minute/hourly cadence; nothing runs on your customers' page loads.
Never. The single write it can perform is re-enabling a WooCommerce webhook, and only when you click the button or switch on auto-recovery yourself.
No message content is stored. Email log rows keep the WooCommerce email id, order id, and a masked recipient (j***@example.com). Gateway snapshots exclude anything that looks like a credential.
Yes: drift, stuck orders, queue health and email reconciliation are independent of webhooks.
Fully compatible - orders are read exclusively through the WooCommerce CRUD APIs.