| 开发者 | magesentinel |
|---|---|
| 更新时间 | 2026年11月13日 01:41 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
magesentinel+ address, under an hour old and unpaid.Not for the health page or the email alerts — they read your own store and report to you. The connector needs an account, because it is one half of a link to the service.
Only stores with at least 14 orders in the last week get this check. It compares the quiet spell with the same hours of the week over the last four weeks, and fires when your store would normally have taken five or more orders in that time, never before six hours of quiet. A Sunday night with no orders is normal; a Monday noon is not. If nothing is wrong, it clears itself with the next order.
They are sent by WP-Cron, which runs when your site gets visits, and through your site's own mail. If other WordPress emails do not arrive either, set up an SMTP plugin. The overview shows when the last self-check ran.
Read the diagnostics listed in the description, read one order by id, and cancel one order — and the cancel path refuses anything that is not a MageSentinel test order: the billing address must match magesentinel+…, the order must be under an hour old and unpaid, and you must have switched "Test orders" on. A real customer order cannot be touched.
No. The plugin filters WooCommerce's order emails for its own orders before they are addressed.
They are real WooCommerce orders while they exist, so they are visible — which is why the overview lists the last 15 of them, and why cancelling them is offered. They are placed with a synthetic magesentinel+ billing address, which makes them easy to filter anywhere you report.
Usually because something between the cart and the payment broke: a payment method switched off, the checkout page unpublished, maintenance mode left on, or a plugin update that broke the checkout. The health page checks each of these, and the "orders stopped" alert fires when a store with a steady flow goes quiet for much longer than usual. The full list of causes and fixes: WooCommerce checkout not working.
WooCommerce hides an enabled payment method when its own conditions fail: wrong currency, a minimum amount, a missing API key, a shipping method it does not allow. The health page shows which methods are enabled, and connected stores see the one WooCommerce refuses to offer. More: why payment methods disappear.
The shopper reached the payment provider but the store never heard back, usually a blocked webhook or callback. The failed payments check counts pending and failed orders, and names a payment method that fails while the others take money. More: orders stuck in Pending payment.
The plugin's own alerts go through the same wp_mail as WooCommerce's order emails, so if neither arrives the problem is the site's mail, not WooCommerce. An SMTP plugin usually fixes both. More: WooCommerce order emails not sending.
That pattern is card testing: bots trying stolen card numbers through your checkout. Three failed payments in an hour trigger the failed payments alert at once, so you hear about it while it is happening. How to stop it: WooCommerce card testing attacks.
No front-end scripts or styles are loaded at all. The self-check runs in WP-Cron, off the shopper's request path.
Yes. The plugin uses WooCommerce's order CRUD, not direct post queries.
wp magesentinel status prints every check from the command line, and exits 1 when one is red./wp-json/magesentinel/v1/, guarded by a hashed token.