Linux 软件免费装
Banner图

MageSentinel – Checkout Monitoring for WooCommerce

开发者 magesentinel
更新时间 2026年11月13日 01:41
PHP版本: 7.4 及以上
WordPress版本: 7.1
版权: GPLv2 or later
版权网址: 版权信息

标签

woocommerce alerts woocommerce checkout store health checkout monitoring

下载

3.10 3.4 2.7 2.8 3.9 2.3 2.5 2.6 2.9 3.1 2.4 3.2 3.5 2.10 3.6 2.2 3.7 3.8

详情介绍:

Find out when your WooCommerce store stops taking orders, before your customers tell you. Every 15 minutes the plugin checks the things that quietly break checkout, and emails you when one turns red: Free, no account, and nothing leaves your server. One email per problem, and another when it is fixed. It comes in two parts. The first one is free and needs no account. A health page in your admin. Under the MageSentinel menu you get a plain reading of the things that quietly stop a WooCommerce store from taking money: whether the cart and checkout pages are still set and published, whether any payment method is enabled at all, whether a shipping zone exists, how many fatal errors WooCommerce logged in the last day, whether Action Scheduler is running on time, whether this server's DNS answers quickly (a slow nameserver makes every payment and courier call wait), and whether a WooCommerce database update is waiting. Each row links straight to the screen that fixes it. Email alerts, every 15 minutes. The same checks run on your site every 15 minutes. When one turns red — no payment method, the checkout page unpublished, maintenance mode left on, a pile of failed payments, or orders that stopped coming in when your store normally has a steady flow — you get an email naming the problem and the screen that fixes it, and another when it is fixed. One email per problem, not one per hour. The email goes out through your site's own mail; nothing else leaves your server. Send it to any address, or switch it off. A weekly summary email (optional, off until you switch it on): every Monday, last week's orders, revenue, average order and failed payments against the week before, with the health checks as they stand. Built from your own orders and sent through your site's own mail. These checks read your settings and counts from the inside. They cannot tell whether a shopper can actually pay — a broken payment script, a theme update that hides the button. That is what MageSentinel checkout monitoring is for. A connector for MageSentinel checkout monitoring (optional, paid, 14 days free). MageSentinel walks your storefront the way a customer does — finds a product, adds it to the cart, fills the checkout — and tells you when that stops working. This plugin is the part that runs inside WordPress, so the check can confirm what actually happened in your database instead of guessing from the page. The connector is off by default. Nothing is exposed until you switch it on and paste a token from your MageSentinel dashboard. Once on, it lets MageSentinel: CAPTCHA on your checkout? MageSentinel never solves or gets around a CAPTCHA. If your checkout asks for one, you can switch on Let MageSentinel's checks past your CAPTCHA: requests that carry this store's own connector token are then served without the CAPTCHA, through the CAPTCHA plugin's own allow-list. Every other visitor still gets it. Off by default. Supported: CAPTCHA 4WP (Advanced noCaptcha & invisible Captcha), reCAPTCHA for WooCommerce, hCaptcha for WP and Simple CAPTCHA Alternative with Cloudflare Turnstile. Test orders never reach anyone's inbox: the plugin silences WooCommerce's new, cancelled, failed, on-hold and customer emails for its own orders. Once MageSentinel is connected and checking in, it sends your alerts (email or Slack), so the plugin's own emails pause to spare you duplicates. If MageSentinel stops checking in for three hours, they resume on their own.

安装:

  1. Install and activate the plugin. WooCommerce must be active.
  2. Open MageSentinel in the admin menu. The health page works immediately — no account, no token, nothing to configure. Email alerts go to the site admin address from the first self-check; change the address or switch them off under MageSentinel → Settings.
  3. To connect monitoring, go to MageSentinel → Settings, switch the connector on and paste the token from your store's page in the MageSentinel dashboard. The token is stored hashed; it is never shown again.
  4. Optionally switch on Test orders so MageSentinel may cancel the orders it places itself. Leave it off and those orders are only ever read.
To disconnect, switch the connector off. The endpoints stop answering at once.

屏幕截图:

  • The overview: a health score, today's orders and revenue, failed payments, and orders by day and by hour. MageSentinel's own test orders are left out of the numbers.
  • Revenue this week against last week, checkout speed over the last 30 test purchases, health over 7 days, and products that sell but have run out, with the sales they are missing.
  • The store at a glance: catalog and stock, pending updates, performance and security, payments by method and how many shoppers who reached checkout paid.
  • Test purchases placed and cancelled automatically, next to recent changes to payment, shipping and plugin settings.
  • Settings: email alerts, the weekly summary, the connector token and the test-order switches, next to what MageSentinel can and cannot see.
  • The dashboard widget: the health score, today's numbers and a test purchase one click away.
  • Tools → Site Health: the checkout check sits next to WordPress's own tests.

升级注意事项:

3.10 The check after an update is marked as such in your dashboard. 3.8 Safer lock between overlapping runs of the checks. 3.7 Faster checks on large stores, most of all on stores that still keep orders in the posts table. 3.6 The last checks that loaded orders one by one now count them in the database: a full run stays around 35 queries on any store size. 3.5 Lighter checks on busy stores, an "orders stopped" alert that knows your store's usual hours, and clearer alert emails. 3.4 Security checks (injected scripts, PHP in uploads, "admin" user), unsent order emails and object cache, grouped health cards and an hourly 7-day view. 3.3 Tested with WooCommerce 11.2; small translation fix. 3.2 On MageSentinel's Free plan the connection card now says the connector is inactive and that the checkout is still checked once a day. 2.2 The weekly summary email is now off until you switch it on in Settings. 2.1 Checkout health in Tools → Site Health, and a wp magesentinel status command. 1.10 Housekeeping for the WordPress.org directory; nothing changes in your settings. 1.9 Updates applied to the store are marked next to MageSentinel's checks. 1.8 New display name only; nothing changes in your settings. 1.7 Checks the http:// to https:// redirect and the storefront's security headers. 1.6 Connected stores get a test purchase right after a checkout-relevant update. 1.5 Failed payment steps now name the payment method WooCommerce will not offer. 1.4 The free self-check runs every 15 minutes instead of every hour. 1.3 Fixes "Settings saved" showing on every visit to Settings. 1.2 SSL expiry and price checks, payments by method and a checkout funnel. 1.1 A designed weekly summary email with a chart of orders per day. 0.13 Test-mode payment check, update alerts and a Monday summary email. 0.12 Test purchase progress shows every checkout step by name. 0.11 Readable Test purchase button while it runs. 0.10 Run a MageSentinel test purchase from the plugin and watch it live. 0.9 The Save button is always visible again. 0.8 Fixes saving the settings switches. 0.7 Settings switches save instantly. 0.6 Clearer overview: alerts switch, fewer false background-task warnings, named plugin changes. 0.5 "Check again" now really re-runs the checks. 0.4 Adds free hourly email alerts. They are on by default and go to the site admin address; change or switch them off under MageSentinel → Settings. 0.2.0 Adds a store-health overview that works without an account, and reports more diagnostics to connected MageSentinel monitors.

常见问题:

Do I need a MageSentinel account?

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.

Why did I get an email saying orders stopped?

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.

The alert emails never arrive

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.

What can the token do?

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.

Will test orders email my customers, or me?

No. The plugin filters WooCommerce's order emails for its own orders before they are addressed.

Will test orders pollute my reports?

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.

Why did my WooCommerce orders suddenly stop?

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.

A payment method disappeared from my checkout

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.

Orders are stuck in Pending payment

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.

WooCommerce order emails are not sending

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.

Many failed orders from the same card in minutes

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.

Does it slow the store down?

No front-end scripts or styles are loaded at all. The self-check runs in WP-Cron, off the shopper's request path.

Is HPOS supported?

Yes. The plugin uses WooCommerce's order CRUD, not direct post queries.

更新日志:

3.10 3.9 3.8 3.7 3.6 3.5 3.4 3.3 3.2 3.1 2.10 2.9 2.8 2.7 2.6 2.5 2.4 2.3 2.2 2.1 1.10 1.9 1.8 1.7 1.6 1.5 1.4 1.3 1.2 1.1 0.13 0.12 0.11 0.10 0.9 0.8 0.7 0.6 0.5 0.4 0.3.0 0.2.0 0.1.0