Skip to content

Repository files navigation

Lineweb Store Guard — WooCommerce Update Preflight & Health Checks

A free, read-only WooCommerce health-check plugin that records comparable store snapshots before and after updates—without creating test orders or changing commerce settings.

Store Guard gives merchants and maintainers a compact view of the configuration that commonly explains a broken cart or checkout. It is independently installable, GPL licensed, and includes both an admin dashboard and a machine-readable WP-CLI command.

Screenshots

Both screenshots come from an isolated local demo store. They contain no client, customer, or production configuration data.

Lineweb Store Guard dashboard and manual baseline action

Current WooCommerce preflight checks and WP-CLI command

What it checks

  • WordPress, WooCommerce, and PHP versions.
  • Cart and Checkout page publication state and block, classic, custom, or missing implementation mode.
  • Availability of the core WooCommerce Store API product and cart routes.
  • Enabled payment gateways.
  • Enabled shipping methods across WooCommerce zones.
  • Action Scheduler availability plus pending and failed action counts.
  • HPOS usage and compatibility-mode synchronization state.
  • WooCommerce PHP template overrides in the active theme.
  • Currency, tax-display basis, stock management, guest checkout, and permalink configuration.

How snapshots work

Use Capture baseline on WooCommerce → Store Guard before a planned change. The dashboard compares that manual baseline with the current store state and lists changed values.

For plugin, theme, and WordPress core updates handled through the WordPress upgrader, Store Guard also records a before/after pair. It retains the ten latest update records in plugin-owned options.

The plugin is read-only with respect to WooCommerce configuration and orders. It writes only its own baseline and snapshot history.

WP-CLI

Print the current snapshot as JSON:

wp lineweb store-guard check --format=json

YAML is also available with --format=yaml. The command reads current state and does not save a baseline.

Practical update workflow

  1. Verify that a current backup can be restored.
  2. Open WooCommerce → Store Guard and capture a manual baseline.
  3. Perform the planned update through WordPress.
  4. Reopen Store Guard and review the changed values and update history.
  5. Run the real cart, checkout, shipping, payment, and email smoke tests required by the store.

Store Guard complements those tests; it does not replace them.

Requirements

  • WordPress 6.9 or newer
  • WooCommerce 10.8 or newer
  • PHP 8.3 or newer

Installation

  1. Install and activate WooCommerce.
  2. Upload the Lineweb Store Guard ZIP from Plugins → Add New → Upload Plugin.
  3. Activate the plugin.
  4. Open WooCommerce → Store Guard.
  5. Review the current preflight and capture a baseline before the next planned update.

Privacy

Store Guard does not inspect or create orders and does not send store state to Lineweb. It adds no telemetry, tracking, account, or external request.

Snapshots remain in the site's WordPress database. They contain the checked configuration, version information, configured Cart/Checkout URLs, gateway and shipping method identifiers, and relative template-override paths. Treat exported CLI output as operational information and review it before sharing publicly.

Deliberate boundaries

Store Guard is not:

  • an uptime monitor or hosted monitoring service;
  • a browser-based checkout test;
  • a payment or shipping transaction test;
  • a backup, restore, malware, or vulnerability scanner;
  • an automatic repair or rollback tool;
  • a complete diff of every WordPress or WooCommerce option.

Automatic before/after history depends on updates that pass through the WordPress upgrader hooks. Always perform a real storefront smoke test after an update.

Support and security

Read the shared support policy. For reproducible support requests, use the Lineweb contact form and include the plugin version, current preflight output with sensitive details removed, and steps to reproduce.

Please report suspected vulnerabilities privately as described in the security policy. Do not include credentials, customer data, or production database exports.

License

GPL-2.0-or-later.

About

WooCommerce update preflight and health checks with read-only snapshots, diagnostics, HPOS and Store API checks, and WP-CLI.

Topics

Resources

Security policy

Stars

0 stars

Watchers

0 watching

Forks

Releases

Packages

Contributors

Languages