| 开发者 | artprojectgroup |
|---|---|
| 更新时间 | 2026年5月27日 19:15 |
| 捐献地址: | 去捐款 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.0 |
| 版权: | GNU General Public License v3 or later |
| 版权网址: | 版权信息 |
apg_nif_display_error_message and apg_nif_error_message filters.apg_nif_add_fields filter.apg_nif_skip_validation filter.apg_nif_skip_required filter.wc-apg-nifcifnie-field folder to the /wp-content/plugins/ directory via FTP.The plugin settings are very simple: you only need to indicate whether you want the NIF/CIF/NIE field to be validated or not, and configure the optional VIES and EORI validation if you need them.
If your store placed orders via the Checkout block (or the classic checkout) with an older version of the plugin, some orders may have duplicate or legacy billing_nif / shipping_nif metadata rows that prevent the field from updating correctly in the admin panel.
Option 1 – Settings page (recommended): Go to WooCommerce -> NIF/CIF/NIE field. If duplicates are detected, a "Fix duplicate NIF metadata" button appears at the bottom of the page. Click it to run the cleanup. The button disappears automatically once there are no more duplicates.
Option 2 – WP-CLI (large stores): Run the following command from the root of your WordPress installation to avoid HTTP timeouts:
wp eval-file wp-content/plugins/wc-apg-nifcifnie-field/includes/admin/limpieza-meta-duplicados.php
WC - APG NIF/CIF/NIE Field is a free plugin. Art Project Group does not provide free technical support, but offers a paid technical support service for installation and configuration.
wc_orders_meta); they relied on the $wpdb->wc_orders_meta property, which WooCommerce does not set, so on HPOS stores the 4.14.0 migration touched only postmeta and left the orders untouched. The HPOS table is now detected from the database prefix, and the automatic one-time cleanup runs again on update to 4.14.1 to migrate those orders to _billing_nif / _shipping_nif._billing_nif / _shipping_nif (with a leading underscore), matching WooCommerce's native order meta convention (_billing_*) so the value is read by ERP integrations such as Holded and others that expect the underscored key. Reading still falls back to the legacy billing_nif / shipping_nif for orders placed with previous versions.billing_nif / shipping_nif keys to the canonical _billing_nif / _shipping_nif (in both postmeta and HPOS wc_orders_meta). Run it from the plugin settings or via WP-CLI on large stores.billing_nif / shipping_nif, as WooCommerce stores customer billing fields without the underscore._billing_nif / _shipping_nif), while the value is still stored under the canonical billing_nif / shipping_nif keys._billing_nif / _shipping_nif copy, and editing an order from the admin panel no longer creates a second metadata entry.billing_nif and _billing_nif (or shipping_nif and _shipping_nif) coexist, works on both postmeta and wc_orders_meta (HPOS, including sync mode and configurations where the cleanup button previously failed to appear), and caches the query for one hour to avoid performance issues on large stores. The cleanup migrates lone legacy keys to the canonical key, removes legacy keys when the canonical one already exists, and deduplicates repeated rows, so detection and cleanup always agree (fixing the case where the button appeared but reported "0 fixed").id, so WooCommerce was writing the admin-entered value to _billing_nif / _shipping_nif instead of billing_nif / shipping_nif. As a result, the display always showed the original checkout value unchanged.postmeta and wc_orders_meta (HPOS) regardless of the active storage mode. Previously the cleanup button could fail to appear on stores using HPOS sync mode or certain HPOS configurations.billing_nif / shipping_nif metadata rows generated when placing orders with Checkout Blocks, which caused the NIF field to appear unchanged after editing an order from the admin panel.[woocommerce_my_account] shortcode on stores using Checkout Blocks.billing_nif and shipping_nif first, with fallback to legacy meta keys.requerido_envio in classic checkout so the shipping NIF/CIF/NIE field is only required when the customer checks "Ship to a different address".apg_nif_skip_required filter to override the required status for billing or shipping via hook.Codice Fiscale validation.valida-bloques-nif.js.product_instance_caching.apg_nif_skip_validation filterapg_nif_add_fields filter.apg_nif_display_error_message and apg_nif_error_message.