lineweb-store-guard/readme.txt at main · drewmt/lineweb-store-guard · GitHub

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
=== Lineweb Store Guard ===
Contributors: lineweb
Tags: woocommerce, diagnostics, update, preflight, hpos
Requires at least: 6.9
Tested up to: 7.0
Requires PHP: 8.3
Requires Plugins: woocommerce
WC requires at least: 10.8
WC tested up to: 10.9
Stable tag: 0.1.0
License: GPL-2.0-or-later
License URI: https://www.gnu.org/licenses/gpl-2.0.html

Read-only WooCommerce preflight snapshots, update diffs, and WP-CLI diagnostics.

== Description ==

Lineweb Store Guard records a focused WooCommerce configuration snapshot before and after planned changes, without creating orders or changing commerce settings.

The preflight covers:

* WordPress, WooCommerce, and PHP versions.
* Cart and Checkout page state and implementation mode.
* WooCommerce Store API availability.
* Enabled gateways and shipping methods across zones.
* Action Scheduler pending and failed counts.
* HPOS and synchronization state.
* Active-theme WooCommerce template overrides.
* Currency, tax basis, stock management, guest checkout, and permalink settings.

Capture a manual baseline from WooCommerce > Store Guard and compare it with the current state. Updates handled through the WordPress upgrader also receive before/after records; the ten latest update records are retained in plugin-owned options.

WP-CLI output is available with `wp lineweb store-guard check --format=json` or `--format=yaml`.

Store Guard is not a browser checkout test, transaction monitor, backup, security scanner, automatic repair tool, or complete diff of every site option. A real cart and checkout smoke test is still required after updates.

== Installation ==

1. Install and activate WooCommerce 10.8 or newer.
2. Upload and activate Lineweb Store Guard.
3. Open WooCommerce > Store Guard.
4. Review the current preflight.
5. Capture a baseline before the next planned update.

== Screenshots ==

1. Branded Store Guard dashboard with the manual Capture baseline action and current store summary.
2. Current Cart, Checkout, Store API, and Action Scheduler preflight information with the read-only WP-CLI command.

== Frequently Asked Questions ==

= Does Store Guard change WooCommerce settings? =

No. It reads the selected store configuration and writes only its own baseline and snapshot-history options.

= Does it create a test order? =

No. It does not place orders, call gateways, or test shipping transactions.

= Is the WP-CLI command read-only? =

Yes. `wp lineweb store-guard check --format=json` prints the current snapshot without saving a baseline. YAML output is also supported.

= Will every update create a before/after record? =

Automatic history depends on plugin, theme, or core updates passing through the WordPress upgrader hooks. A manual baseline is available for other planned changes.

= What data leaves the store? =

None is sent to Lineweb. The plugin adds no telemetry, tracking, account, or external request. Snapshots remain in WordPress. Review exported CLI output before sharing it publicly because it contains operational configuration.

== Support and Security ==

For support, use https://lineweb.gr/contact/ and include versions, a redacted preflight, and reproduction steps.

Report suspected vulnerabilities privately through https://lineweb.gr/contact/. Do not publish credentials or customer data.

== Changelog ==

= 0.1.0 =

* Initial read-only preflight, update snapshot, diff, admin hub, and WP-CLI release.