FlxWoo
| 开发者 | rickey29 |
|---|---|
| 更新时间 | 2026年7月9日 05:31 |
| PHP版本: | 8.0 及以上 |
| WordPress版本: | 7.0 |
| 版权: | GPL v2 or later |
| 版权网址: | 版权信息 |
详情介绍:
- A REST API layer for WooCommerce checkout state (namespace:
flxwoo/v1) - A server-side rendering layer for checkout and product page templates
- A Stripe Checkout integration with server-side session management and webhook handling
- A fallback-safe product page rendering layer: falls back to native WordPress/WooCommerce templates when the Render service is unavailable or the product type is not supported
- An admin dashboard for operational monitoring: Overview, Settings, and System Status pages
- An infrastructure layer that extends WooCommerce without replacing it
- Not a WooCommerce fork or replacement
- Not a page builder or visual checkout designer
- Not a payment processor — payment remains in WooCommerce and Stripe
- Not a headless CMS
- Not a replacement for WooCommerce's admin, order management, or product system
- Agencies building custom checkout experiences on WooCommerce
- Developers who need REST access to WooCommerce checkout state
- Projects requiring server-side rendered checkout templates
- Teams integrating Stripe Checkout while keeping WooCommerce as the order system
flxwoo/v1). Checkout state endpoints (cart, order, coupon, customer) return JSON. Render endpoints (/render/checkout, /render/thank-you) return server-side rendered HTML. Product pages are intercepted at the template layer and rendered through the external Render service, with automatic fallback to native WordPress/WooCommerce templates if the service is unavailable or the product type is not supported.
WooCommerce remains authoritative for all order, cart, tax, and payment data. FlxWoo reads and writes through WooCommerce's standard APIs without modifying its data structures or core behavior.
Features
- REST API under the
flxwoo/v1namespace - Cart and checkout state endpoints returning JSON
- Stripe Checkout integration — server-side session creation and webhook handling
- Duplicate order prevention at the checkout session level
- Concurrent submission guard
- Session-independent Stripe return flow (order identity carried via URL, not session state)
- Server-side HTML rendering for checkout and thank-you templates
- Product page rendering via external Render service, with automatic fallback to native WordPress/WooCommerce templates
- Product type gate: only simple products (including virtual) are routed to the Render service; variable, external, and unrecognized types use native templates
- Structured logging for checkout and payment events
- Operational event store tracking webhook failures, Stripe connectivity issues, and auth denials
- Health endpoint at
GET /wp-json/flxwoo/v1/healthfor uptime monitoring - Admin Overview page with operational health summary and last-payment/last-webhook signals
- System Status page with diagnostics across environment, Stripe, cache, webhooks, checkout failures, and database
- Automated data retention: scheduled cleanup for idempotency records, Stripe events, checkout sessions, and operational events with defined retention windows
- Preserve-by-default uninstall policy: data is retained unless explicitly opted out in Settings
安装:
- Upload the plugin to
/wp-content/plugins/, or install it from the WordPress admin plugin installer. - Activate the plugin. Required database tables are created automatically on activation.
- Configure your Stripe API keys in the FlxWoo settings page.
- Before going to production, configure cache bypass rules for
/checkout*,/thank-you*, and/wp-json/flxwoo/*. See the Cache and CDN Configuration section above. - Verify the installation by requesting the health endpoint:
GET /wp-json/flxwoo/v1/healthshould return HTTP 200.
常见问题:
Does FlxWoo replace WooCommerce checkout?
No. FlxWoo adds a REST and rendering layer on top of WooCommerce's checkout system. WooCommerce remains responsible for cart calculation, order creation, tax, coupons, and inventory.
Does FlxWoo replace WooCommerce payment processing?
No. Payment is handled by WooCommerce and Stripe. FlxWoo creates Stripe Checkout sessions server-side and handles webhook callbacks — the order record and payment status are managed by WooCommerce as normal.
Is this a headless WooCommerce solution?
It is headless-friendly. FlxWoo provides the REST API and server-side rendering infrastructure needed for decoupled checkout workflows. A fully headless setup is possible but not required — FlxWoo can also be used within a standard WordPress/WooCommerce installation.
Why do I need to configure my cache?
FlxWoo REST endpoints and the checkout and thank-you HTML pages carry live session, cart, and payment state. Caching any of them produces incorrect behavior — stale carts, duplicate orders, broken payment confirmation pages, and session data surfacing to the wrong customer. These failures are often intermittent and cannot be reproduced in local environments where CDN layers are inactive. See the Cache and CDN Configuration section for specific instructions, or docs/cache-configuration.md for full per-system details.
Does FlxWoo modify WooCommerce orders or products?
No. FlxWoo creates and reads orders through WooCommerce's standard APIs. It does not modify product data, order structure, or WooCommerce core settings.
Is FlxWoo compatible with WooCommerce's built-in checkout?
FlxWoo operates independently of WooCommerce's default checkout. It provides its own checkout flow via REST, leaving WooCommerce's built-in checkout pages intact. Running both simultaneously is technically possible but is not a tested configuration.
What happens if the Render service is unavailable?
FlxWoo falls back to native WordPress/WooCommerce product page templates. If the Render service cannot be reached, the product page loads using the default WooCommerce template instead. No broken page is served; fallback is automatic and does not require manual configuration.
Does FlxWoo support all WooCommerce product types?
Only simple products (including virtual) are currently routed to the Render service. Variable, external, and grouped products — and any unrecognized product type — fall back to native WordPress/WooCommerce templates. This is handled automatically; no configuration is required.
What happens to my data if I delete the plugin?
Data is preserved by default. Deleting the plugin does not drop database tables or remove settings unless the Delete all data on uninstall option was enabled in FlxWoo Settings > Data before deletion. Deactivating the plugin never removes any data.
更新日志:
- Security:
/checkout/stripe-sessionnow requires the caller to be the order owner or present a valid order key, matching the access model already used by/order/getand/checkout/success. Previously any caller could request a Stripe Checkout session for any order ID. - Security:
/checkout/successno longer transitions an order toprocessing. A browser redirect is informational only; only the signature-verified Stripe webhook can confirm payment. - Security:
/checkout/finalize-ordernow verifies payment against Stripe's API (succeeded status, matching amount/currency, single-use) before completing an order, instead of trusting the client-supplied payment reference.
- Preserve-by-default uninstall policy: FlxWoo data (database tables, settings) is retained when the plugin is deleted unless the opt-in is explicitly enabled
- Added "Delete all data on uninstall" option in FlxWoo Settings > Data
- Product type gate: variable, external, and unrecognized product types now fall back to native WordPress/WooCommerce templates instead of being routed to the Render service
- System Status improvements: human-readable timestamp formatting, top-level System Health indicator, improved webhook health labels and remediation text
- Translation template synchronization: admin UI strings added to the .pot template
- Initial stable release
- REST API infrastructure under the
flxwoo/v1namespace - Stripe Checkout integration: server-side session creation and webhook handling
- Duplicate order prevention and concurrent submission guard
- Server-side HTML rendering layer for checkout templates
- Structured logging and a health endpoint for uptime monitoring
- Security hardening: ABSPATH guards, input sanitization, PHPCS release gate
- Internationalization baseline with text domain support