| 开发者 |
transactly
drashco |
|---|---|
| 更新时间 | 2026年5月17日 23:11 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 6.9 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
/wp-content/plugins/, or install via Plugins → Add New → Upload Plugin.No. Every number in the report comes from your store's own database. Compass makes no external HTTP calls in v1.0 — that is a deliberate design choice, not an oversight. It removes a whole class of review concerns and lets the plugin run in environments without outbound internet.
No. v1.0 has no user-configurable options on purpose — there is nothing to set up before running your first report. Settings will arrive in a later version when a feature genuinely requires them (the planned PageSpeed integration in v1.5 is the first such feature).
Yes. All order queries use the WooCommerce CRUD API (wc_get_orders(), wc_get_order()) and work in both legacy post-table and HPOS modes. Refund and order-item handling uses the documented instanceof WC_Order / instanceof WC_Order_Refund guards so refund objects never leak into order iteration.
Yes. The Latest Report page has a "Download as Markdown" button that ships exactly what you see on screen as a .md file you can paste into any document, email, or chat tool.
Each finding is calibrated against a 1–10 priority score based on the size of the underlying signal (e.g., percentage share of revenue, magnitude of a rank drop, gap size in completion rates). Reports are sorted by priority descending, capped at the top 10. Patterns below priority 4 don't ship.
If your current 90-day window has fewer than 10 paid orders, Compass returns a "data sufficiency" notice instead of running the rules. Findings on a tiny sample are misleading; an honest "not enough data yet" is more useful.
Brand. The plugin's job is to point at the next thing worth doing — declarative, not exploratory.
Open a thread on the WordPress.org support forum for this plugin. Reproducible steps with WordPress + WooCommerce versions are appreciated.