| 开发者 | harborplugins |
|---|---|
| 更新时间 | 2026年7月13日 02:41 |
| PHP版本: | 8.2 及以上 |
| WordPress版本: | 7.0 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
$order->get_meta(), so no direct database queries are made against order tables.
Requirements
/wp-content/plugins/No. This plugin targets the WooCommerce block checkout exclusively. For the legacy shortcode checkout, use WooCommerce's Checkout Field Editor or a similar plugin.
Yes. Field values are saved automatically by WooCommerce when a registered field is submitted. The plugin reads them via $order->get_meta(). No direct database queries against order tables are made.
WooCommerce 8.9 or later. The woocommerce_register_additional_checkout_field() function was introduced in WooCommerce 8.9.
PHP 8.2 or later. PHP 8.0 and 8.1 reached end-of-life and are no longer supported.
Field values appear in:
Location controls where the field appears in the block checkout:
Yes. Drag the handle icon on the left of each field row in WooCommerce > Checkout Fields to change the display order.
There is no hard limit enforced by this plugin. WooCommerce's own additional fields API handles rendering. Keeping the number of fields small helps keep checkout simple for customers.
No. Fields are registered server-side using WooCommerce's official API. No JavaScript is injected into the checkout frontend. The admin settings use lightweight AJAX.
Field values are stored as order meta on each order and will remain in your database. If you reactivate the plugin, historical field values will be visible again. Deleting a field from the settings page removes it from future checkouts and from the order and email displays; the stored values are not deleted and remain in the database.
Yes. Fields are rendered and validated by the WooCommerce block checkout before payment is processed. They are compatible with all major payment gateways.
Yes. Because this plugin uses WooCommerce's official block checkout extensibility API, it works with any theme that uses the standard WooCommerce block checkout.
$order->get_meta(), no direct DB queries