Plugin Support
Akash
(@akashelex)
Hi @james-feaver
I hope you are doing well.
We are currently working on WooCommerce block checkout compatibility for the basic version of the plugin, which is now in the testing phase.
This feature is already available in the premium version, and we expect the update for the basic version to be released shortly.
I will keep you updated once the new version is available.
Thread Starter
James
(@james-feaver)
Hi @akashelex,
That’s great news. Thanks very much,
Thread Starter
James
(@james-feaver)
Hi @akashelex,
Thanks for the new version and the block support – lookign good. One or two issues to report though for both billing and shipping addresses:
- Order of fields – your autocomplete appears at the end of the address blocks. As a customer, if you work your way down filling in the address fields, you only see autocomplete at the end. Logic says it should be at the beginning. Is this possible please?
- The county field gains the country name, not the county – if county is not in the address should that be blank?
Happy to check a test version for you before it goes live.
Thanks,
James
Hello @james-feaver ,
Thank you for your detailed feedback — it’s really helpful.
We’ve shared your suggestion regarding the autocomplete field placement with our team and are currently evaluating the feasibility of moving it to the top of the address section for a better user experience.
Regarding the county field: if the county information is available for the searched address, it will be populated accordingly. Otherwise, the field will remain blank.
We’ll proceed with the fix and include it in an upcoming release once it’s ready.
Please feel free to share any additional observations.
Thread Starter
James
(@james-feaver)
Hi,
Doing some more testing, there are discrepancies between the classic and block based checkouts. For the same auto address:
Classic – town / city gets populated – https://prnt.sc/DZoJkcmPGPQn
Block – town / city does NOT get populated – https://prnt.sc/x2gJwfW7kPII
Neither takes the “district” part of the address, in the screenshots – “Mayals”.
For this address:
Classic – takes district and city correctly – https://prnt.sc/DkN8y4DJzA15
Block – district put into the city field, the city is discarded – https://prnt.sc/EZ7nlvINUEJ_
Thanks,
James
Plugin Support
Akash
(@akashelex)
Hi @james-feaver
Thank you for your feedback regarding the block-based checkout. Please see our updates below:
1. Currently, we cannot change the address autocomplete field position on the block checkout page. Unlike the legacy checkout, the block-based checkout does not yet provide options to set field positions, and there is no updated documentation available for this. If this functionality becomes available in a future WooCommerce version, we will include it in our plugin.
2. We are currently investigating why the autocomplete flows are working differently between the classic and block checkouts and will provide an update soon. Regarding UK addresses, the API primarily populates address line 1, city, country, and postcode. Address line 2 and the county field are optional; our plugin will auto-fill these only if that specific data is provided in the API response.
Please feel free to contact us if you have any further queries.
-
This reply was modified 2 months, 1 week ago by
Akash.
Thread Starter
James
(@james-feaver)
Hi,
I was in touch with WooCommerce support on another matter and asked about the order of fields on the checkout page such as within the address area, specifically do custom ones have to be at the end? They replied:
Regarding your follow-up question, fields are not restricted to being last. You can control their position using the priority argument when registering the field, which allows you to place them before or after other fields within the same section.
Does this help so they can be in a more logical order?
Thanks,
Plugin Support
Akash
(@akashelex)
Hello @james-feaver
The priority-based field positioning works only with the classic WooCommerce checkout, as it relies on PHP hooks. This option is not available in the block checkout, which uses a different (React-based) structure.
You can still add custom fields in block checkout, but their exact position cannot be controlled. For precise placement of the address autocomplete field, we recommend switching to the classic checkout.
Please let me know if you have any queries.
Thread Starter
James
(@james-feaver)
Hi @akashelex,
Earlier in this thread, I reported differences in the address fields returned for the same addresses with the classic and block based checkouts. When I saw the description of the latest update (1.8.7) – “Improve autocomplete accuracy for specific address formats”, I guessed this might have been fixed but testing shows not. Did your investigation get anywhere towards a fix please?
Thanks,
Plugin Support
Akash
(@akashelex)
Hello @james-feaver
We have tested across multiple addresses and countries, and we are seeing the same results with classic and block checkout in the latest version 1.8.7. Could you please deactivate the plugin, clear the cache, reactivate it, and check whether the issue persists?
Thread Starter
James
(@james-feaver)
Hi @akashelex,
All good now – identical between classic and block-based and all elements being used with the “Flat, suite, etc (optional)” field.
Thanks very much.
James
Plugin Support
Akash
(@akashelex)
Hi @james-feaver
I am glad to hear that the plugin is now working correctly on your site.
If you are happy with the product and our support, please consider sharing a review. Should you have any further questions or if the issue persists, don’t hesitate to reach out.
Thread Starter
James
(@james-feaver)
Hi @akashelex,
I am encountering an issue with the use of your plugin on a block-based checkout. My site has United Kingdom as the store address’s country.
This image (https://prnt.sc/dOEyHCOYgjvW) shows my checkout (staging site) with all plugins deactivated (except WooCommerce and Wordfence). I deliberately leave the “phone” field empty and when I place the order, I correctly get a warning because the required “phone” field is invalid.
If I activate your plugin, return to the checkout and refresh the page, then deliberately try to place the order without completing any shipping address fields, I get errors for the required fields and the optional “county” field (https://prnt.sc/HyRbChh26DYk).
Making no changes to the plugins that are active, I go back and use your plugin to populate the address fields. County is left empty. If I leave the phone number empty, I get errors for them both (https://prnt.sc/7sjp0OvaRLVN). I should not be getting an error for an optional field.
Oddly, if I complete the phone number but leave county blank, the order goes through without any errors.
I am trying this in an incognito browser window and clearing the cache between goes. It is not happening every single time!
Thanks very much.
James
Plugin Support
Akash
(@akashelex)
Hello @james-feaver
I hope you are doing well.
1.This image (https://prnt.sc/dOEyHCOYgjvW) shows my checkout (staging site) with all plugins deactivated (except WooCommerce and Wordfence). I deliberately leave the “phone” field empty and when I place the order, I correctly get a warning because the required “phone” field is invalid.
As per the new WooCommerce default theme, the phone number field is now optional for the shipping address. The phone number field can be left blank.
https://prnt.sc/g55hkseZ7kjy
2.If I activate your plugin, return to the checkout and refresh the page, then deliberately try to place the order without completing any shipping address fields, I get errors for the required fields and the optional “county” field (https://prnt.sc/HyRbChh26DYk).
Our plugin returns warnings to fill in the address, first & last name and email address fields which are required for placing the order and address validation. It is the expected behaviour of the plugin.
3.Making no changes to the plugins that are active, I go back and use your plugin to populate the address fields. County is left empty. If I leave the phone number empty, I get errors for them both (https://prnt.sc/7sjp0OvaRLVN). I should not receive an error for an optional field.
Based on our testing with the WooCommerce default twenty five theme, it only returns a warning for the county field only. Even when our plugin is deactivated, we still receive a warning only for the county field. Therefore, this is not a plugin issue as the notification coming from WooCommerce.
https://prnt.sc/0n446nlLCxlM
Hope it clarifies! Please feel free to contact us if you have any queries.
-
This reply was modified 2 weeks, 3 days ago by Akash.
Thread Starter
James
(@james-feaver)
Hi @akashelex,
Thank you very much for looking into this. It is an intermittent issue and I cannot exactly nail down what you need to do to trigger it, but I have had the County warning with your plugin deactivated so confirm it is a WooCommerce issue.
Googling it a bit more I found the bug has been reported – https://github.com/woocommerce/woocommerce/issues/63002 and following it’s steps, I can recreate it routinely. Hopefully it will get fixed.
