MageSentinel – Checkout Monitoring for WooCommerce

Changelog

2.10

• Changed: the button that runs MageSentinel’s test purchase is now called “Test cart & checkout”, so it is not mistaken for “Check again”, which re-runs the health checks on this site.

2.9

• New: “DNS on this server” health check. It times a lookup at each nameserver in /etc/resolv.conf and warns when the first one does not answer, which makes every outgoing call from the site (payments, couriers, updates) wait seconds first.

2.8

• Improved: during a test purchase, “Where the time went” now moves while a step is running. The current step counts up live from the moment MageSentinel started it, instead of the bar waiting for the step to finish.

2.7

• New: dark colours. The plugin screens follow your system’s light or dark setting, and a small switch in the header lets each user pin Light or Dark instead. The dashboard widget stays light.

2.6

• New: after two weeks, and only while every check is healthy, the overview asks once for a review on WordPress.org. “Later” hides it for 30 days, “No, thanks” for good.

2.5

• New: Revenue this week vs last week, day by day.
• New: Selling, but out of stock: products that sold in the last 30 days and have none (or almost none) left, with an estimate of the sales missed this month.
• New: Health over 7 days: the worst result of each day’s health checks.
• New: Checkout speed: how long a test purchase takes from start to the last click before paying. Your free monthly tests without an account, the last 30 checks with MageSentinel connected.

2.4

• New: a free test purchase once a month, without an account. MageSentinel goes through your checkout from outside like a shopper, up to the last click before paying, and shows each step as it happens.
• New: “Test purchase now” in the dashboard widget for connected stores.

2.3

• Translations now use WordPress’s standard system, so the plugin can be translated on translate.wordpress.org. Greek is bundled.

2.2

• The weekly summary email is now opt-in, and loads nothing from outside when opened.
• All markup the admin screens build is escaped before it is printed.
• The readme describes the external service in one place, including the test purchase requested after an update.
• Deleting the plugin removes its settings and stored data.

2.1

• Tools → Site Health shows a “WooCommerce checkout health” test: critical when something stops orders, recommended when something is worth a look.
• wp magesentinel status prints every check from the command line, and exits 1 when one is red.

1.10

• The HTTPS self-check now verifies the certificate.
• The readme lists the external services the plugin talks to.
• Plugin Check clean: inputs are unslashed and sanitized, the error-log reader uses SplFileObject, and the name now reads “Checkout Monitoring for WooCommerce”.

1.9

• Connected stores: MageSentinel now receives the updates applied in the last week (name and version), to mark them on the store’s charts next to the checks.

1.8

• The plugin is now listed as “MageSentinel — WooCommerce Checkout Monitoring”. Same slug, settings and features.

1.7

• New: checks that http:// sends shoppers on to https:// and shows which security headers the storefront sends (HSTS, nosniff, frame protection, referrer policy).

1.6

• Connected stores: when WooCommerce, the theme or a payment or shipping plugin is updated, MageSentinel runs a test purchase two minutes later instead of waiting for the next scheduled check. At most one every 15 minutes.
• The update email links to the overview with every check.

1.5

• MageSentinel now sees whether WooCommerce would actually offer each enabled payment method, and whether checkout and cart are built with the WooCommerce blocks or the classic shortcode. When a check finds no payment method at checkout, the alert names the one WooCommerce itself refuses to offer.

1.4

• The self-check runs every 15 minutes instead of every hour, so a broken checkout, a payment method switched off or a site left in maintenance is emailed within a quarter of an hour. The expensive parts keep their 12-hour cache, so the extra runs cost the site little.

1.3

• Settings: “Settings saved” shows only after saving, not on every visit.

1.2

• New check: the SSL certificate, with a warning two weeks before it expires.
• New check: products in stock without a price, which nobody can add to the cart.
• Payments by method over 7 days: paid, failed, unpaid and success rate.
• Checkout over 7 days: shoppers who reached checkout and how many paid. Counts only.
• Stores not connected see the steps MageSentinel’s hourly test purchase goes through.

1.1

• The weekly summary is a designed email: tiles with the change against the week before, a chart of orders per day, the health checks and the updates.
• Versions now run 1.1 to 1.10, then 2.1.

0.13

• Failed payments: three in an hour trigger the check at once, and a payment method that only fails while the others take money is named.
• New check: a payment method left in test or sandbox mode on the live store.
• Updates of WooCommerce, the theme and the plugins behind checkout, payment and shipping are recorded; you get one email asking for a test order.
• Weekly summary email every Monday: orders, revenue, average order and failed payments against the week before, plus what needs a look.

0.12

• Test purchase: the progress shows each checkout step by name, with a tick, a cross or a skip and how long it took, the same flow as the MageSentinel app.

0.11

• Test purchase: the button stays readable while it runs, and the progress bar is labelled.

0.10

• Connected stores: “Test purchase now” asks MageSentinel to run a real test purchase and shows it step by step, with the verdict and a link to the run.

0.9

• The Save button is always shown; it saves the alert address and the token.

0.8

• Fix: settings switches failed to save (“Could not save”).

0.7

• Settings: switches save as soon as you flip them; the Save button appears only when you edit the alert address or paste a token.

0.6

• Alerts on the overview are a single on/off switch with a link to their settings.
• Background tasks: WooCommerce’s own housekeeping (such as fetching block patterns) no longer counts as a failure; a real failed task is named.
• Recent setting changes name the plugin that was switched on or off.

0.5

• “Check again” now runs the checks on the spot (and sends the alert email if something turned red), instead of only reloading the page.

0.4

• Free email alerts: the health checks run every hour and email you when one turns red, and again when it is fixed. Any address, or off.
• New check: orders stopped coming in, for stores with a steady flow.
• Connected to MageSentinel, the plugin shows “Monitored by MageSentinel” and pauses its own emails; they resume if MageSentinel stops checking in.
• Links to try MageSentinel or see its plans, shown only while not connected.

0.3.0

• Optional CAPTCHA exemption for MageSentinel’s own checks, off by default: requests carrying this store’s connector token skip CAPTCHA 4WP, reCAPTCHA for WooCommerce, hCaptcha for WP and Simple Cloudflare Turnstile. Pages served that way are never cached.

0.2.0

• Admin overview: cart and checkout pages, payment methods, shipping zones, fatal errors, Action Scheduler and pending WooCommerce database updates, each linking to the screen that fixes it.
• Table view of every figure on the overview, so nothing lives in the chart alone.
• Activity panel: MageSentinel’s last contact and its recent test orders.
• Diagnostics now report catalog size, pending updates, cache state and configuration changes.
• Greek admin strings.

0.1.0

• First release: diagnostics, order confirmation and test-order cancellation over /wp-json/magesentinel/v1/, guarded by a hashed token.