WP-CLI Commands

WP Sell Services ships a wpss command namespace for site operators and developers. Run wp wpss to list everything, or add --help to any command for its full options.

wp wpss demo         Manage demo services
wp wpss preflight    Run release-readiness preflight checks
wp wpss scale        Seed, benchmark and teardown a production-shape dataset
wp wpss service      Manage services (alias of `demo` -- same subcommands)
wp wpss test:flow    Run end-to-end data flow tests
wp wpss validate     Validate models and schema

All commands respect the current site in multisite (--url=).

Demo content

wp wpss demo and wp wpss service are the same command registered under two names, so every subcommand below works with either prefix.

wp wpss demo create --count=20 --featured=5   # seed 20 services, 5 featured
wp wpss demo marketplace                      # seed a FULL demo marketplace
wp wpss demo list                             # list services with stats
wp wpss demo stats                            # marketplace statistics summary
wp wpss demo regenerate-meta                  # rebuild computed service meta
wp wpss demo delete --yes                     # remove all demo/test content

create and marketplace are not the same thing. create seeds service listings only. marketplace builds a working marketplace: multiple vendors with profiles and portfolios, buyers, orders across the whole lifecycle, reviews, buyer requests with proposals, and conversations. Use marketplace for staging sites, theme testing, and client demos; use create when you just need catalog volume.

Demo content is flagged internally, so demo delete never touches real customer data. delete prompts for confirmation -- pass --yes in scripts.

Health checks

wp wpss preflight    # verify database tables, settings defaults, page mappings
wp wpss validate     # validate marketplace data integrity

Run preflight after installation, after a migration, and before a release. Every check prints PASS or FAIL with the reason.

Testing and gap detection

wp wpss test:flow      # end-to-end data flow tests

Earlier documentation listed wp wpss test run, test tables, test gaps, test seed and test clean. No bare wpss test command is registered -- those examples fail with "not a registered subcommand". The only command in this group is test:flow. For seeding and cleanup use wp wpss demo, and for release checks wp wpss preflight.

test:flow walks a complete order lifecycle through the data layer and reports where a flow breaks. It is the fastest way to confirm a fresh install actually works end to end.

API payload contract

wp wpss api:shapes                        # audit every GET route
wp wpss api:shapes --verbose              # also list routes it could not reach
wp wpss api:shapes --route=conversations  # narrow to one area
wp wpss api:shapes --user=diego           # audit as a vendor, not an admin

Walks every registered GET route in both namespaces, fills parameterised routes from real rows in the database, and inspects each response for the two conventions a client depends on: dates are ISO-8601 with an offset, and any object describing a person carries deleted. Exits non-zero on a breach, so it can gate a build.

Run it after adding or changing an endpoint. It exists because the same class of inconsistency was reported three times, and twice the fix was verified against a hand-picked sample of endpoints and reported as if it covered the API.

Read the "Not audited" count as part of the result. Those are routes with no matching row on the current dataset, or not readable as the chosen user -- an unaudited route is exactly where the last gaps hid, so the command names them rather than passing over them silently. Seeding the missing data, or re-running with --user, shrinks the list.

Scale benchmarking

For verifying the marketplace holds up at production shape -- 10k vendors with orders and wallet transactions.

wp wpss scale seed                    # seed a production-shape dataset
wp wpss scale bench                   # time every hot-path query vs its budget
wp wpss scale bench --seed --teardown # seed, bench, teardown in one shot (CI gate)
wp wpss scale teardown --yes          # remove all benchmark data

Every seeded row carries a sentinel (a description / vendor_notes prefix plus a high user-id offset), so teardown removes exactly what seed created and never touches real marketplace data.

bench measures each hot-path query against a per-query budget, so it fails loudly when a change makes a list view unusable at scale, rather than leaving you to discover it on a customer's site.