01 · Ownership
Who writes woocommerce_cheque_settings?
WooCommerce is the tested owner for woocommerce_cheque_settings under the WooCommerce 10.3, 10.7, 10.9 & 11.0 ConfigOps adapter contract. This is a source-backed adapter claim, not a guess based on naming.
- Component type
- WordPress plugin
- Component entry point
woocommerce/woocommerce.php- Adapter ID
woocommerce- Adapter schema
- 1
- Visible setting
- WooCommerce → Settings · Offline payments
- Classification
- Configuration
02 · Stored value
Associative array with nested fields.
| Path | Visible meaning | Kind | Why it matters |
|---|---|---|---|
/enabled | Cheque payments enabledOffline payments | portable | Controls whether customers can select this bundled offline payment method. |
/title | Cheque payments titleOffline payments | portable | The payment-method name shown during checkout. |
/description | Cheque payments descriptionOffline payments | portable | The payment-method explanation shown during checkout. |
/instructions | Cheque payments instructionsOffline payments | portable | Instructions shown after the customer places an order. |
03 · Technical state & secrets
What belongs beside the setting—but not inside the decision?
Known version, inbox, scheduler, onboarding, task-list, empty-selector, note, and rewrite state stays technical. Orders, products, customers, tax tables, shipping zones, webhooks, API keys, Action Scheduler jobs, and analytics tables remain outside option-only recovery.
The adapter-wide technical boundary still applies; absence here is not proof that a save has no runtime side effects.
Known secret paths
No secret field is declared inside this exact option schema. ConfigOps still applies its conservative global secret detector.
04 · ConfigOps recovery
Adapter-backed, not Smart Undo.
woocommerceSchema 1; tested against WooCommerce 10.3, 10.7, 10.9 & 11.0.
Supported values can use adapter-aware, conflict-checked Undo when evidence is complete and the current value still matches.
No. Smart Undo is only for ordinary associative options that no adapter claims. This option is adapter-owned.
History boundary: ConfigOps records only saves it observes while active. It cannot tell you what changed this row before installation.
05 · WP-CLI read commands
Inspect without writing.
Run these on the intended environment. The commands read current state; they do not reconstruct history.
wp option get woocommerce_cheque_settings --format=jsonwp option list --search=woocommerce_cheque_settings --fields=option_name,autoload --format=tablewp eval 'print_r( array_keys( (array) get_option( "woocommerce_cheque_settings", array() ) ) );'06 · Save autopsies
No option-specific autopsy published yet.
The owner and field map are verified by the adapter source, but this Atlas record does not claim an option-specific browser or integration save trace.
07 · Direct answers
Questions developers ask mid-incident.
What plugin writes woocommerce_cheque_settings?
WooCommerce is the tested owner in the ConfigOps WooCommerce 10.3, 10.7, 10.9 & 11.0 adapter contract. The assignment is verified, not inferred from the option prefix.
What is stored in the woocommerce_cheque_settings WordPress option?
Associative array with nested fields. woocommerce_cheque_settings contains 4 mapped fields in this adapter schema.
Can ConfigOps track and undo changes to woocommerce_cheque_settings?
ConfigOps can attribute and record supported Options API writes while active. Supported values can use adapter-aware, conflict-checked Undo when evidence is complete and the current value still matches. No. Smart Undo is only for ordinary associative options that no adapter claims. This option is adapter-owned.
Does WordPress keep a history of woocommerce_cheque_settings?
WordPress normally exposes the current option value, not a universal before-and-after history. ConfigOps must observe the original save to create local evidence; it cannot reconstruct older changes retroactively.
08 · Provenance
Why this page exists.
This record was generated from pinned ConfigOps source commit e319f502ff677bd76e53b7034650f9ee2afead72. The exact option name passed the publication allowlist; arbitrary searches do not.