Hi @rangevolk,
By default, the free WooCommerce will always display the Billing Fields on the checkout page and there are no settings in the WooCommerec plugin itself which would remove those.
I’ve performed some cross-testing for us today on several of my sites which have the latest versions of WordPress, WooCommerce and our free Storefront theme as the only enabled software. When doing so I’ve not been able to replicate the behaviour which you describe with Billing Fields not displaying.
https://woostaging.mystagingwebsite.com/
Looking at your site I can see that no fields are not being outputted within the HTML including the Additional Information text box.
Image Link: https://cloudup.com/cGOFvXaP1Ka
This indicates that something isolated to your site is removing those fields from displaying as what you’re experiencing is not directly related to WooCommrce itself. If you’ve deactivated all plugins aside from WooCommerce and at the same time activated a theme like Storefront to test I’m not sure what would be removing those fields on only your install.
Hi Stuart Duff,
Do you know how i can be able to fix it? It is very frustrating.
Hey @rangevolk,
You could try carrying out another conflict test on your site to try and locate the culprit by disabling all other plugins aside from WooCommerce along with switching to a theme like Storefront. This will help with trying to and locate what software or custom code you have installed which could possibly be causing this behaviour? You could use a free plugin called Health Check and Troubleshooting to carry out such testing.
When in Troubleshooting mode all plugins will be deactivated and only the admin of the site carrying out the troubleshooting would see those changes. Any customers visiting the site would see no changes at all.
Once you have disabled all other plugins and switched theme if the behaviour is resolved you can then enabled your theme and sites plugins testing after each one is enabled until the behaviour returns to locate the culprit.
https://docs.woocommerce.com/document/how-to-test-for-conflicts/
Thanks Stuart.I was able to figure theme is the one causing the issue while trobleshooting.Contacting the developer for the theme.
Thanks and have an Awesome Day
Hey @rangevolk,
That’s fantastic to hear you found the culprit which was causing this when conflict testing 🙂
I’m going to mark this as resolved – if you have any further questions, you can reopen it again if you need be.