Linux 软件免费装
Banner图

Dreamfoxmedia Checkout Logic Builder for WooCommerce

开发者 dreamfox
更新时间 2026年10月13日 20:31
PHP版本: 7.4 及以上
WordPress版本: 7.1
版权: GPLv2 or later
版权网址: 版权信息

标签

woocommerce checkout conditional fields checkout fields checkout builder

下载

1.0.2 1.0.3

详情介绍:

Dreamfoxmedia Checkout Logic Builder for WooCommerce gives you full control over your checkout form. Add your own fields, hide or relabel the built-in ones, reorder everything with drag-and-drop, and show fields only when they are relevant with conditional logic — all with custom validation rules and your own error messages. The big differentiator: it works on both WooCommerce checkouts. The classic [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 Block checkout notes (honest fine print) The block checkout supports a smaller set of field types than the classic checkout. Definitions degrade gracefully, and the builder shows a badge on affected types so you're never surprised: Conditional logic on the block checkout currently covers field-value conditions. Conditions on cart total, cart contents, shipping method or payment method apply to the classic checkout only. Hiding or relabeling default address fields applies to the classic checkout; the block checkout manages its own address fields. Built by Dreamfox Media.

安装:

  1. Upload the plugin files to /wp-content/plugins/dreamfox-checkout-logic-builder, or install through the WordPress plugins screen.
  2. Activate the plugin through the 'Plugins' screen.
  3. Go to WooCommerce → Checkout Fields and open the Fields tab to add your first custom field.
  4. Optionally hide or relabel built-in fields under Default Fields.

屏幕截图:

  • Editing a field: type, section, validation and conditional logic.
  • Default Fields: hide, relabel or change required-ness of built-in fields.
  • A custom field on the classic checkout.
  • The same field on the block checkout.
  • Captured values on the admin order screen and in the order email.
  • Tools: JSON import/export and reset.

升级注意事项:

1.0.3 Renamed to Dreamfoxmedia Checkout Logic Builder for WooCommerce; new listing images. No functional changes. 1.0.2 Maintenance release, no functional changes. 1.0.1 Renamed to Dreamfox Checkout Logic Builder for WooCommerce. 1.0.0 Initial release.

常见问题:

Does this work with the block checkout?

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.

Why does my textarea/radio/date field look different on the block checkout?

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.

Where do I find the captured values?

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}.

Can I show a field only for certain countries?

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.

Can conditions depend on the cart or the payment method?

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.

Does it support a multi-step checkout plugin?

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.

What happens to captured values when I delete a field or uninstall?

Nothing. Values already stored on orders are order data and are kept. Uninstalling removes only the plugin's settings.

Is it GDPR-friendly?

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.

Is the plugin compatible with HPOS (High-Performance Order Storage)?

Yes, the plugin declares full HPOS compatibility and only ever touches order meta through the CRUD API.

更新日志:

1.0.3 1.0.2 1.0.1 1.0.0