Free Release Notes

Commerce Health 1.4.0

Four new checkout checks, alert recipients (To and CC), and HPOS compatibility.

1.4.0

  • Added: Alert recipients on the Settings screen. Enter one or more To addresses and, optionally, CC addresses (up to 5 in each) so the critical-issue email and the test email reach the right people. CC is applied to every email the plugin sends, and PRO’s emails use the same addresses. See Settings.
  • Added: Checkout Page Content check. It confirms the checkout page contains the WooCommerce checkout (block or shortcode) and the cart page contains the cart. Pages built with a page builder or a reusable block are reported as “could not confirm”, not as a failure.
  • Added: Checkout Address Fields check. On the classic checkout, it reports address fields that have been removed while the store uses shipping or tax.
  • Added: Recent Failed Orders check. It compares failed orders with finished orders over the last seven days, using order counts only, and judges only after at least ten finished orders.
  • Added: Payment Gateway Test Mode check. It flags an enabled Stripe, PayPal or Braintree gateway that is still in test mode on a production site. It reads only the on/off test-mode setting, never keys or credentials.
  • Added: the plugin now declares compatibility with WooCommerce high-performance order storage (HPOS).
  • Added: a kodenzo_ch_issue_changed action that runs when an issue is new, reopened or changes severity, so add-ons can react to scan findings.
  • Changed: the PHP Version check now says plainly when the PHP version has reached the end of its support (PHP 8.1 and older) and no longer receives security fixes. PHP 8.2 keeps the “approaching the end of its support window” wording, and PHP 8.3 and newer pass.
  • Changed: the plugin now has 34 checks. Stores where one of the new checks finds something may see a lower health score than before. See Diagnostic checks and categories.
  • Changed: the critical-issue email and the “Send test email” button now go to the alert recipients instead of always the site admin address.
Was this article helpful?

Still need help?

Search the docs first — or open a ticket and our team will pick it up from the Support screen.