| 开发者 | dreamfox |
|---|---|
| 更新时间 | 2026年10月13日 20:31 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
[woocommerce_checkout] shortcode and the block checkout (the default since WooCommerce 8.3) are driven by the same field definitions, and a captured value lands on the order under the same meta key (_dfclb_{field id}) either way. Migrate checkouts whenever you like — your fields and your data pipeline don't change.
Free features
meta_data) and in the WordPress personal-data export/erase tools (GDPR).dfclb_field_label) for WPML/Polylang string translation.YYYY-MM-DD format./wp-content/plugins/dreamfox-checkout-logic-builder, or install through the WordPress plugins screen.Yes — that's the point. Fields defined in the builder are registered with WooCommerce's Additional Checkout Fields API for the block checkout and injected into woocommerce_checkout_fields for the classic checkout. The captured value is stored under the same _dfclb_{field id} order-meta key in both cases.
The block checkout natively supports text, select and checkbox fields. Other types degrade to the closest supported type: textarea becomes single-line text, radio becomes a dropdown, and date becomes a text field validated as YYYY-MM-DD. The builder shows a badge on these types.
On the order screen in wp-admin (a "Checkout fields" box), in the order emails, on the customer's order-received/view-order page, and via the REST API in the order's meta_data under _dfclb_{field id}.
Yes. Add a conditional-logic rule like "billing_country equals NL" to the field. The field then appears only when that condition holds, live in the browser and enforced again server-side. A field hidden by its conditions is never validated as required.
On the classic checkout, yes: cart total, cart contents (product ID), shipping method and payment method are all available as rule sources. On the block checkout, only field-value rules apply in v1.
Multi-step checkouts are not actively supported or tested. On the classic side the plugin uses only standard WooCommerce hooks (woocommerce_checkout_fields, checkout validation and order creation), so a multi-step plugin that keeps those hooks intact will usually work — but that's a bonus, not a promise.
Nothing. Values already stored on orders are order data and are kept. Uninstalling removes only the plugin's settings.
Yes. Captured values are included in WooCommerce's personal-data export for an order and removed when an order is anonymized via the WordPress erase tools.
Yes, the plugin declares full HPOS compatibility and only ever touches order meta through the CRUD API.