| 开发者 | duafatima |
|---|---|
| 更新时间 | 2026年6月21日 18:22 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.0 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
[woocommerce_checkout] shortcode. Most "checkout field" plugins were written for that old PHP checkout, so on a block checkout their fields silently break - or never appear at all.
Fieldnest is block-first. It is built on WooCommerce's official Additional Checkout Fields API, part of the Store API, so every field you add:
/wp-content/plugins/.Yes - that is the whole point. Fieldnest uses WooCommerce's native Additional Checkout Fields API (part of the Store API), so fields render in the block checkout without reverting to the classic shortcode.
Fieldnest is designed for the block checkout. The Additional Checkout Fields API it relies on is provided for the block-based checkout, so the block checkout is what we support and recommend.
Yes. Each field value is stored as standard order (and where relevant, customer) metadata, and is available through the Store API. You can see the values on the order.
The free version supports text, dropdown (select) and checkbox fields. Fieldnest Pro adds date, radio, multi-select and file-upload fields.
In the Contact, Address or Order section of the block checkout - you choose per field.
Yes. Fieldnest declares compatibility with HPOS and with the cart and checkout blocks.
No. Fieldnest registers fields through WooCommerce's own API and adds no external requests, so there is no measurable overhead.
No. There is no tracking, no external API calls and no nag banners. Everything runs on your site.
Many checkout-field plugins were built for the classic PHP checkout and only partly support (or completely miss) the block checkout. Fieldnest is built block-first on the native API, so fields actually appear, save correctly and keep working after updates.
That is conditional logic, available in Fieldnest Pro, along with validation rules and extra field types.