| 开发者 | wolfcourt |
|---|---|
| 更新时间 | 2026年10月7日 02:56 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
wolfcpf_selected_option as a non-negative format index and wolfcpf_paid_addon as yes or true to the add-item route. The server checks the choice and recalculates the price from saved product data; a request without a required format is rejected. Untested custom quick-add interfaces should link customers to a product form that visibly presents the choices.
Classic product forms use a cart security token tied to the visitor's WooCommerce session. The product-page script refreshes it before submission so that cached pages can still be used. If JavaScript is disabled on a cached page, reload the page before retrying an expired form. Store API clients continue to use WooCommerce's own Nonce or Cart-Token header.
No customer data is collected or sent to an external service.
Only cart items with a selected format or paid add-on are adjusted. The saved WooCommerce catalog price is not overwritten.
Version 1.0 focuses on simple products. Variable products, conditional rules, per-product add-ons, imports, and bulk editing are suitable premium extensions.
No. It has no telemetry and no external service dependency.
Not every block. The classic product form is supported, and Add to Cart + Options passed a browser cart test with a regular POST form in our WooCommerce 11.1.2 test. The Store API can accept a format choice from a custom client. Standard catalogue buttons now open the product form when a format is required; other blocks and custom quick-add interfaces need separate verification or integration.