Check these requirements first
- WordPress 6.7+, WooCommerce 9.9+ and PHP 8.0+. Your WooCommerce version may require newer WordPress or PHP versions.
- Using Blocks product or total rules? You need Pro and WooCommerce 10.1+. Conditional Contact information fields also need 10.1+.
- Classic or Blocks? Open WooCommerce → Cartdini to see the detected checkout type, then check the matching column below.
Free RC11 and Pro RC8 are release candidates. Use the staging checklist before production. Passing release tests does not guarantee compatibility with every theme or extension.
Classic checkout vs Checkout Blocks
| Feature | Classic | Checkout Blocks |
|---|---|---|
| Text, select, checkbox | Free + Pro | Free + Pro |
| Field-answer conditions | Pro; text/select/checkbox/radio sources | Pro; select/checkbox from WC 9.9; conditional contact from WC 10.1 |
| Product and final-total conditions | Pro | Pro; WooCommerce 10.1+ |
| Textarea, email, telephone | Free + Pro | Not registered |
| Number, date, radio | Pro | Not registered |
| Four order/email display controls per field | Free + Pro | Free + Pro |
| Optional core-field changes | Supported subset | Use the WordPress checkout editor |
| Custom placeholders | Supported | Not applied |
| Help text | Inline | Input tooltip; not select |
| HPOS order storage | WooCommerce CRUD | Native additional-field API |
Conditional contact fields in Blocks require WooCommerce 10.1 or newer; unconditional contact fields still support 9.9+. Text/radio-source conditions are Classic-only, and unsupported saved fields are retained without being registered in Blocks. Classic core controls cover company, phone, address line 2 and order notes. Cartdini does not take over essential address, tax or payment fields. Read the Blocks setup guide for location and display differences.
Recorded plugin test environments
On 24 September 2026, Free RC11 / Pro RC8 passed 297 website/editor tests, 4,024 PHP assertions on each of PHP 8.0 and 8.4, and 600 new native WooCommerce 10.1 frontend rule cases. A local WordPress 7.1.2 / WooCommerce 11.1.1 / PHP 8.5.4 store also passed product lookup, exact variation rules, coupon refreshes, direct server validation, hidden-answer cleanup, final totals including tax and shipping, recipe saves, cross-store mapping and recovery checks. Classic and Blocks completed offline-payment test orders. No live gateway or email delivery was tested. See the release guide for evidence and boundaries.
Earlier release test evidence (RC10, RC9 and RC1)
Historical Free RC10 / Pro RC7 evidence
On 23 September 2026, Free RC10 / Pro RC7 passed 2,687 PHP assertions on each of PHP 8.0 and 8.4, 270 website/editor tests, and 36 native WooCommerce frontend contract checks. A separate real WordPress 7.1.2 / WooCommerce 11.1.1 / PHP 8.5.4 / MariaDB store completed Classic and Blocks test orders with visible and hidden follow-ups, server-side rejection of missing required answers, stored-answer and HTML/plain email visibility checks, and Free editing after Pro deactivation. These were local zero-total orders; no external payment gateway or email delivery was exercised.
Historical Free RC9 / Pro RC6 evidence
Historical checks recorded on 23 September 2026: Free RC9 and Pro RC6 passed 1,417 PHP assertions on each of PHP 8.0 and 8.4. These checks execute actual Cartdini handlers and the real WooCommerce 9.9.0 and 10.0.0 schema validators; WordPress APIs, orders and HTTP are controlled doubles. They cover legacy configurations, grouped conditions, hidden-answer handling, update credentials and package integrity. The editor was also exercised in Chromium at desktop and mobile widths. This is not a complete WordPress store or real-payment test. The older integration results below apply only to RC1.
| WordPress | WooCommerce | PHP | Results |
|---|---|---|---|
| 7.1 | 11.1.0 | 8.3.33 | 101 integration assertions passed, including 39 security checks |
| 6.8 | 9.9.0 | 8.0.30 | 101 integration assertions passed, including 39 security checks |
These checks ran against WordPress and WooCommerce with PHP WebAssembly and SQLite. They exercise configuration validation, order data, checkout-field registration and access controls. Those results describe the earlier RC1 package, not RC9 or RC10 store compatibility.
Passing checks are evidence about those cases and environments. They are not a guarantee for every theme, extension, host or future release. The historical PHP-WASM checks above did not run a complete browser checkout or a live payment gateway. Historical RC10 / RC7 native-store checks are listed separately at the start of this section.
Validate your own store before production
- Back up the store and use a staging copy with the same theme, checkout extensions, database and payment gateways.
- Confirm whether the checkout uses the Checkout block or the Classic shortcode. Add one optional field first.
- Place test orders as a guest and a signed-in customer. Include separate billing and shipping addresses when your store supports them.
- For Pro rules, test both visible and hidden states, including missing required answers. Confirm the saved order and email output.
- Check taxes, shipping and gateway redirects using the gateway’s test mode. Then test deactivation and your rollback procedure.
Installation and recovery documentation explains templates, restore points and retained order data.
Security is ongoing maintenance
The release checks include restricted roles, REST nonce handling, malformed saved settings and invalid input. Administrative changes require WooCommerce management permissions and server validation. The plugins make no external telemetry calls.
No release can be described as exploit-free forever. Keep WordPress, WooCommerce, PHP and all extensions updated, and retest checkout after meaningful changes. Review the changelog and security reporting instructions when planning updates.
Read the release guide