CHECK BEFORE INSTALLATION

Classic or Blocks: what works?

Custom questions work in both. Use this quick comparison to check the existing fields and advanced inputs your store needs.

Add a first test field Compare support

On this page

START WITH YOUR STORE

Check these three versions.

WordPress

6.7 or newer

WooCommerce

9.9 or newer

PHP

8.0 or newer

Your WooCommerce version may require newer WordPress or PHP versions. Free 1.8.11 is available on WordPress.org. Pro 1.8.11 is supplied separately for eligible accounts and requires Free 1.8.4 or newer. The current matched pair is Free 1.8.11 and Pro 1.8.11. Install or update Free first, then Pro, and keep Free active. Existing Pro 1.8.7 remains compatible with Free 1.8.11. Initial Pro licence activation is supported on single-site WordPress installations. A previously earned unlock remains tied to the same website identity.

Open WooCommerce → Cartdini to check the detected checkout implementation. The editor preview shows structure; it cannot establish theme or gateway compatibility.

Which checkout does your store use?

In WordPress, edit the page assigned as your WooCommerce checkout. A Checkout block means Checkout Blocks; a [woocommerce_checkout] shortcode means Classic checkout. Cartdini also shows the detected checkout in WooCommerce → Cartdini.

A page builder or checkout extension may provide its own layout. Check its documentation and test a field on staging.

KNOWN CHECKOUT BLOCKS LIMITATION

Check customer details after cart updates.

On WooCommerce 11.2.1 Checkout Blocks, a delayed cart update can replace email or address details entered more recently. We reproduced this with Cartdini active and with both Cartdini plugins removed. Since Pro 1.8.2, Cartdini protects newer customer details from its own successful paid-choice responses and refreshes address-dependent totals before ordering. This is a scoped fix: unrelated WooCommerce or extension cart responses can still replace newer details.

Before using Blocks with shoppers, test typing and changing customer details while cart or fee updates finish, then verify the saved order. If your store reproduces the issue, do not launch that Blocks setup until it is resolved. Assess Classic checkout on staging as an alternative.

Earlier 1.8.2 checks

Selected native checks covered the minimum PHP 8.0 / WordPress 6.7 / WooCommerce 9.9 setup and current PHP 8.3 / 8.5 with WordPress 7.1.3 / WooCommerce 11.2.1, plus targeted PHP 8.1, 8.2 and 8.4 workflows. Both HPOS and legacy storage, MariaDB and Redis were used. Selected checkout and error-retry browser checks used Chromium, Firefox and WebKit. Coverage varied by scenario and candidate; this was not a complete feature matrix on every combination. These checks do not establish every theme, gateway, cache or physical-device combination. The delayed-response issue above remains open.

RECORDED RELEASE CHECKS

What was checked, and when.

Free 1.8.11, checked 8 November 2026: a fresh isolated store on WordPress 7.1.4 / WooCommerce 11.2.1 / PHP 8.3.6 covered editor saving, required answers, actual Classic and Blocks orders, saved responses and the generated WooCommerce order email. Desktop and 390px browser captures show these Free workflows. Orders used an offline test method; email was intercepted locally, with no inbox-delivery claim.

Separate installation checks used Free 1.8.11 with unlicensed Pro 1.8.7 on WordPress 6.7 / WooCommerce 9.9 / PHP 8.0.8 and WordPress 7.1.4 / WooCommerce 11.2.1 / PHP 8.3.6. These checks recorded settings and synthetic order answers and confirmed that unlicensed Pro editing stayed locked. They did not exercise paid activation, authenticated update delivery or every Pro checkout workflow. Older checks below remain historical evidence, not fresh repetitions for every current combination.

A separate 8 November 2026 native ZIP replacement check upgraded active Pro 1.8.7 to Pro 1.8.11 with Free 1.8.11 on both setups above. Settings and synthetic order answers were preserved, installed files matched the selected packages, and unlicensed Pro editing remained locked. This was not a paid activation, authenticated updater, completed checkout or inbox-delivery test.

Selected 1.8.7 checks covered the Free and Pro workspace on desktop and narrow screens, plus Free order-question placement on WordPress 7.1.4 / WooCommerce 11.2.1 and WordPress 6.7 / WooCommerce 9.9. A separate Free 1.8.6-to-1.8.7 replacement check used fictional physical-product orders from a guest and a returning shopper, shipping totals and locally captured native order emails. These checks used isolated stores and offline payment methods, not a real payment provider or inbox delivery. They do not establish every Pro workflow, theme or gateway.

The earlier 1.8.4 audits covered selected native WordPress checks on PHP 8.0 with WordPress 6.7 and WooCommerce 9.9, and newer environments using WordPress 7.1.3 and WooCommerce 11.2.1. The audits covered editor saving and draft recovery, precise number rules, conditional required answers, fees, private uploads, privacy failures and native update paths. Browser coverage used Chromium and selected Firefox checks. Individual checks used different source generations and environments; this is not a complete feature matrix on every combination.

Free 1.8.4 added the shared draft-recovery repair needed by Pro 1.8.4. That historical release required both versions for its new Pro behavior. Tests used isolated stores and fictional licence-provider responses; they do not establish delivery on every customer host.

Remaining limits from these audits

For extremely precise numbers, Blocks can show the inline min/max message only after submission. Server validation still rejects an invalid answer.
The minimum test host had no image editor: PDF handling was tested there, while image re-encoding was tested on the newer stack.
Physical phones, operating-system Safari and screen readers were not part of these audits. Very long native select choices can be width-limited with enlarged text.
Historical translation notices without backtraces cannot be conclusively attributed. Selected upstream WooCommerce/Jetpack notices remain recorded.

Compare your checkout.

The same task can use different controls in Classic and Checkout Blocks.

At a glance — current Cartdini Free & Pro
Task	Classic	Checkout Blocks
Nine custom field types · Free	Supported	Supported
Conditions & advanced inputs · Pro	Supported	Supported; older saved rules have limits below
Uploads, repeaters & priced choices · Pro	Order location	Order location
Existing address labels & ordering · Free	Supported controls and Classic overrides	Ten shared address fields
Existing address placeholders · Free	Supported Classic controls	Native WooCommerce controls
Default Place Order text · Free	Theme / WooCommerce	Cartdini setting; payment methods may override it

Nine custom field types · Free

Classic: Supported
Checkout Blocks: Supported

Conditions & advanced inputs · Pro

Classic: Supported
Checkout Blocks: Supported; older saved rules have limits below

Uploads, repeaters & priced choices · Pro

Classic: Order location
Checkout Blocks: Order location

Existing address labels & ordering · Free

Classic: Supported controls and Classic overrides
Checkout Blocks: Ten shared address fields

Existing address placeholders · Free

Classic: Supported Classic controls
Checkout Blocks: Native WooCommerce controls

Default Place Order text · Free

Classic: Theme / WooCommerce
Checkout Blocks: Cartdini setting; payment methods may override it

Field types, locations and storage details

CLASSIC & CHECKOUT BLOCKS

Custom questions work in both.

The same Free field types and Pro additions are available in both checkout implementations, with the location limits below.

FREE · BOTH CHECKOUTS

Nine field types

Text, select, checkbox, textarea, email, telephone, number, radio and URL. Configure required answers, text and number limits, and order/email display. Up to 100 custom fields.

PRO · BOTH CHECKOUTS

More inputs & conditions

Date, time, multiselect and checkbox group, plus conditional questions and requirements. Standalone dates support rolling lead days, available weekdays and excluded dates in both checkouts. Older saved native Blocks rules have additional limits below.

PRO · ORDER LOCATION

Files & repeatable questions

Private uploads and repeatable groups work in both checkouts at the order location only. They require the relevant storage and configuration limits.

PRO · ORDER LOCATION

Fixed paid choices

Configured checkbox, select and radio choices can add a fixed positive per-order fee. They use the order location in both checkouts.

Pro’s personal Orders-list columns and selected-answer CSV export support HPOS and legacy orders. Check selection limits and permissions. Date rules do not reserve appointments, capacity or stock.

Order storage uses WooCommerce order APIs, including HPOS. Read the file, group and fee limits.

Using an older saved Pro workflow in Blocks?

Expanded grouped conditions, conditional requirements and advanced inputs use Cartdini’s registered Checkout Blocks integration with server validation on WooCommerce 9.9+.

Older workflows on WooCommerce’s native additional-fields path retain earlier limits: field rules use select/checkbox sources; cart, product, category, role, shipping/payment and conditional contact rules require WooCommerce 10.1+. A legacy text-source rule on a native field needs review into the expanded group format before it works in Blocks. The editor identifies unavailable workflows.

Existing-field controls and separate save actions

Existing fields have different controls.

These controls keep WooCommerce’s country-specific validation and essential requirements.

Labels, placeholders & ordering

Classic: Supported text and ordering controls for selected existing fields, including supported placeholder changes.
Checkout Blocks: Ten shared address labels/order. Address placeholders and contact email remain native WooCommerce controls.

Company, Phone & Address line 2

Classic: Shared settings apply; explicit Classic overrides take precedence.
Checkout Blocks: WooCommerce’s shared visibility and requirement settings.

Place Order button text

Classic: Controlled by the theme and WooCommerce.
Checkout Blocks: Free can change the default text. Payment methods or other extensions may supply their own text.

Saving native settings

Shared address/button settings save separately from custom fields. They are not part of custom-field templates, transfers or restore history. WooCommerce retains native section content, hidden fields and supported inputs.

Hidden on checkout hides a shared native address input. WooCommerce can still store existing address data or values submitted through its API, including on the order and saved customer address. This setting does not reject or erase that data; Cartdini custom questions have separate controls.

BEFORE YOU UPDATE

Keep a way back.

Back up the store, update Free first and keep it active while replacing Pro. Replace Free with 1.8.11 without uninstalling. For the matched current pair, replace Pro with 1.8.11 after Free, without uninstalling. Existing Pro 1.8.7 remains compatible and does not need replacement solely for this Free update. Existing compatible Pro can remain active during the Free replacement; Pro 1.8.11 retains the Free 1.8.4 minimum. When both plugins need updating, complete the replacements during a maintenance window. Free’s extension API 6 temporarily pauses older Pro versions, including 1.7.16, while preserving settings and order answers. Install compatible Pro to resume its checkout fields; licence and update access remain available during the interval. Expanded settings use a separate configuration format; older pairs cannot use the new controls. Keep a complete site backup for downgrade recovery.

Follow the installation and update instructions. Plugin messages use WordPress language packs. A translation template is included; complete translations for every language are not.

TEST YOUR OWN STORE

A preview is the beginning.

Match the live setup.
Use staging with the same theme, extensions and checkout implementation.
Try both shopper states.
Start with one optional field. Test as a guest and a signed-in shopper, including separate billing and shipping when supported.
Change the inputs.
For Pro, change source answers, products and methods. Check visible/hidden fields, requirements, date boundaries, file removal and selected fees where applicable. Change addresses while fee requests finish and verify the final tax and order details.
Finish a test order.
Submit an incomplete checkout once, correct it and complete an order in the gateway’s test mode. Test longer answers and recovery after a failed paid-choice request. Verify saved answers and expected email display, then check any configured Orders columns and CSV export.
Check recovery.
Test deactivation on staging and restore your staging backup before relying on a downgrade.

STORAGE & MAINTENANCE

Your store stays part of the setup.

Free sends no telemetry. Pro contacts its license service only after an explicit connection. Checkout answers stay in WordPress/WooCommerce; private uploads stay on the store server and need suitable private storage outside public web roots.

Hosting, themes and payment extensions still need testing on your own store. Read the data and recovery guidance or get help with a specific setup.