Forum Replies Created
-
AuthorPosts
-
Birendra
ModeratorHi,
I apologize for the delayed response.
The VAT should remain removed after the order is placed by default. There may be a setting or compatibility issue causing the VAT to be added again, so we’d like to check this directly in your environment to better understand what’s happening.
Could you please provide temporary access to your staging site? This will allow us to investigate the issue and identify what may be causing it. You can send the access details to [email protected].
Once we have access, we’ll take a closer look and do our best to get this resolved as soon as possible.
Best regards,
Birendra
ModeratorHi Dennis,
In WooCommerce Block checkout, there is a limitation in how custom fields are handled. If we register the VAT field directly in the address section, it will appear in both shipping and billing sections. Because of this, we register the VAT field in the Contact section and then move it using JavaScript.
From what I understand, you want to place the VAT field after the Shipping Address block. You can adjust its position using a CSS selector like this:
add_filter( ‘alg_wc_eu_vat_field_position_block_checkout’, function () {
return ‘.wc-block-components-address-address-wrapper’;
} );Or place it after a specific field, for example Shipping Company:
add_filter( ‘alg_wc_eu_vat_field_position_block_checkout’, function () {
return ‘#shipping-company’;
} );The filter accepts a CSS selector, so you can pass any valid ID (#element-id) or class (.element-class) where you would like the EU VAT field to be inserted.
Screenshot showing VAT field after Shipping Company: https://prnt.sc/JA5IbSInaSTD
Could you please try this and let us know if this works for you? If you have any questions or need further help, just let us know.
Thank you!
Birendra
ModeratorHi Antonio, CliffordThank you for your patience.
We have released a new version (v3.7.0) that fixes the email preview issue. The preview should now correctly display the selected custom email content.
Please update the plugin to the latest version and check on your end. Let us know if the issue persists or if you encounter any other problems.
Best regards.
Birendra
ModeratorHi Ned,
Yes, the XML feed can filter products by a custom meta field, but the meta key must be saved for the product.
From your snippet, it looks like a function definition. To filter, you need the actual meta key (e.g., xml_status ) and its value saved. Once saved, you can use the Custom Meta Filter in the XML feed settings:
- Meta Key: xml_status
- Condition: =
- Value: yes
I’ve attached the screenshot for reference:
https://prnt.sc/jvAYqms1YPiMPlease give it a try and let us know how it works.
Best regards
Birendra
ModeratorHi Bernard,
Thank you for sharing this information. I’ve tested the plugin on both WordPress 6.7 and the latest version 6.9.3, but I didn’t encounter the “early textdomain call” warnings. This issue should already be fixed in a previous version.
Could you please check which version of Wish List for WooCommerce Pro you’re using? The current version is 3.4.1.
Thanks again for your feedback.
Best regards,
-
AuthorPosts