Checkout page loading spinner

Hi @danacs,

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 an endless loading spinner icon on the cart and checkout pages of WooCommerce.

From what you have described, 99.9% of the time this behaviour is caused by code from another plugin or theme which has caused a conflict and affected the functionality of WooCommerce.

To see if that is the case we’d suggest carrying out a conflict test on your site 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 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/

I hope this helps.

I tried to disable all plugins other than woocommerce & i tried it with twenty twenty-one theme & the problem was still there.

Ill try it with the storefront theme & deactivate plugins again & see if that helps.
Ill give the troubleshooting plugin a go, I didn’t know there was something like that available that would help.

I am using a Child theme of clean commerce & it has previously been running fine for approx 2 years. Child theme is mostly style.css changes.
Not sure if it makes a difference but I am running multisite (I tried deactivating plugins on all sites & network)

thanks for your help.

Problem still exists with storefront theme & deactivated all plugins including on multisite network & the site itself.

will the troubleshooting plugin help me further? or is that plugin just to make testing easier by disabling plugins etc & testing?

Hey @danacs,

The troubleshooting plugin would perform the same process as manually deactivating all of the plugins, it’s just less disruptive for customers when doing so. ??

Could you provide a link to the checkout page where you’re seeing the behaviour of something from your site or web server breaking the loading of the WooCommerce checkout page?

the site is https://www.albanycarstereo.com.au/shop/
I don’t appear to have any other issues that I have noticed, only that the checkout won’t load.

Hi @danacs,

Looking at your site today and inspecting that using Google Chromes browser developer tools console feature the shop page of your site is displaying errors with WordPress Ajax call. This is preventing products from being added to your site’s cart from the Shop page and product category pages.

On the checkout page, there are also Ajax errors which are causing WooCommerce Ajax dependent functions to produce a 404 Not Found errors. It’s these errors throughout your site which is preventing the WooCommerce checkout page from fully loading details like shipping, payment gateways etc and also the addition of products to cart from the Shop/Product Category sections.

Image Link: https://cloudup.com/cInMsDbJpYF

To resolve this you will have to try and track down why your specific site is causing these errors as it’s not something when testing we can replicate on other installations using the latest version of WooCommerce.

I hope this helps point you in the right direction!

they are the exact errors I am getting on my end.
when I disable all plugins the stripe one disappears but the other 2 still remain.

my issue was I didn’t know what else to do to try find the issue but I believe i have sorted the problem now.
Thanks for your help.

Hey @danacs,

That’s fantastic to hear you’ve resolved this behaviour now. I’m going to mark this as resolved – if you have any further questions, you can reopen it again if you need be.