Checkout – jQuery problem
-
Hello
We use Elementor, WooCommerce and SiteKit. I don’t know why, but when SiteKit is enabled, a JQuery error occurs on the checkout page (among other things, you can see that the shipping fields are broken). Other functions don’t work either.
When we disable the SiteKit plugin, everything goes back to normal and checkout works normally.
Console:
jquery-3.6.0.min.js:2 jQuery.Deferred exception: Cannot read properties of undefined (reading ‘defaults’) TypeError: Cannot read properties of undefined (reading ‘defaults’) at HTMLDocument.<anonymous> (https://filtrujemy.com/wp-content/plugins/woocommerce/assets/js/frontend/checkout.min.js?ver=9.1.4:1:81) at e (https://code.jquery.com/jquery-3.6.0.min.js:2:30038) at t (https://code.jquery.com/jquery-3.6.0.min.js:2:30340) [email protected]:2The page I need help with: [log in to see the link]
-
Thanks for reaching out @wordpressdatasal. If you’d like to share the following we can hopefully determine more on the cause and ensure all does work as expected:
- Your Site Health information. You can use this form to share privately if preferred.
- Does the same occur if you disabled any enhanced conversion tracking within Site Kit? You’ll find this setting within your Google Analytics or Google Ads module, as per this guide.
- Does this error appear as a console error only, or is the error presented to users? Feel free to share a screenshot using a service such as Imgur or Jumpshare. You can share via the same form above if you wish to share this privately.
Let me know if you have any questions with the above. Once we have this information we can provide the most suitable troubleshooting suggestions, which may be to check with another theme using the Health Check & Troubleshooting plugin, or to review your Elementor plugin for any conflicts. Thank you.
Hello,
The problem was solved after disabling enhanced conversion tracking. Do you know why this is happening? We are interested in this solution.
Thanks for your time
Thanks for the update. I’m not certain at this stage what the issue may be, however, there could be other plugins also making use of your Ads Conversion ID, resulting in a conflict.
While I will check this with the team, please share the folowing:
- Your Site Health information. You can use this form to share privately if preferred.
- Does the same occur if you temporarily disable Cloudflare on your site and enable Enhanced Conversion Tracking once more? I can see some Cloudflare references when checking your sites source code, with some optimizations performed.
- Does the same occur if you temporarily deactivate the Tag Manager module within Site Kit and enable Enhanced Conversion Tracking once more? This can be useful in the event you have some tags that impact the checkout process.
Let me know if you have any questions with the above.
Hi James,
- I have sent site health info via google form – thanks.
- We disabled cloudflare (pause option in cloudflare dashboard) – nothing changed.
- About GTM4WP – A Google Tag Manager (GTM) plugin for WordPress – This plugin is always disabled.
Thanks
@wordpressdatasal Thanks for the information. I will check this with the team and get back to you with an update as soon as possible.
In the meantime, would you please be able to share a screenshot or recording of this happening on your site? I will continue to investigate this and any updates I will share here.
@wordpressdatasal Thanks for sharing the information. Could you please try following the troubleshooting steps here to see if you encounter the same while in troubleshooting mode?
Ok, I can confirm that the problem (i.e. JS problem, no response to changing the product quantity or choosing a different shipping method) still occurs with Troubleshooting Mode enabled (the only active plugin is SiteKit and WooCommerce and the default theme is Twenty Twenty Two).
The problem is 100% generated by Site Kit plugin when enhanced conversion tracking mode is enabled.
-
This reply was modified 1 year, 8 months ago by
wordpressdatasal.
@wordpressdatasal Thanks for trying this it’s much appreciated. While we test this ourselves, it would be good if you could share a recording of your experience so we can see what to expect and what steps to take. Or you can share the exact steps you take so that we can attempt to recreate this ourselves.
Currently I can’t do this type of tests because the store already has ads enabled.
But we know that this problem also occurs in our other stores, so I’m sure you’ll be able to easily reproduce this problem.
After enabling enhanced conversion tracking mode, the functionality on the /cart page (e.g. changing the number of products) doesn’t work, or on /checkout the order fields don’t work either.
Thanks for the update on this. Just to let you know we are still testing this, and it may take a while longer. On a couple of test sites I don’t encounter the same
Uncaught TypeErrorwith WooCommerce and Site Kit active (with Enhanced Conversion Tracking enabled).While we’re checking this further can you share whether the same occurs with Enhanced Conversion Tracking enabled once more, but with the Google Ads module not active?
After disabling the Google Ads module (with Enhanced Conversion enabled), the cart and checkout work properly.
Another developer points out that the problem may be a fields conflict…
Thanks for checking @wordpressdatasal. We do have one field that can be configured in either Google Ads or Google Analytics, although there is no conflict we’re aware of with the plugin alone, and we did perform some checks on this.
There are a couple of checks you can perform to try and determine the source of this issue, as it may be a multi party conflict. For example you may be encountering this based on some optimization configurations such as deferring of JS, similar to this query although in your case possibly with a WP Rocket or host configuration.
Another possibility is you have a WooCommerce configuration with one of active plugins that is impacting your checkout behavior. Note also that the console error is pointing to WooCommerce. Yes it occurs with a particular configuration of Site Kit active, however, other plugins you have also hook into WooCommerce on your site. To troubleshoot this further, please perform the steps below:
- Login to your live site from a Chrome browser incognito window.
- Install and activate the Health Check & Troubleshooting plugin.
- Navigate to “Plugins > Health Check & Troubleshooting > Troubleshoot”.
- From the same screen click on the “Available Plugins” tab at the top right and then click on the “Enable” option next to “Site Kit by Google“ and “WooCommerce”.
- Visit the front end of your site and go through the checkout experience, checking for the same error. Note that a different theme will be active. This is for you only as a logged in administrator, this doesn’t impact non-logged in users.
When performing the checks above, you should have Enhanced Conversion Tracking enabled via Site Kit, with Google Ads active.
Let me know if you have any questions with the above. While we’re investigating this, you may also wish to temporarily make use of one of the workarounds, such as enabling enhanced conversion tracking via Tag Manager, or not using the Google Ads via Site Kit.
We already did this test with the Site Health plugin…
We only had Site Kit plugin and WooCommerce plugin enabled, and the default wordpress theme. On the Sit Kit side, Google Ads and enhanced conversion tracking mode were enabled.
With this configuration there was still a problem with the cart and checkout page.
Apologies @wordpressdatasal, I can indeed see you did perform this check. If you wish to temporarily enable Enhanced Conversion Tracking once more, I’ll once again visit your site to check for console errors. If I can determine a Site Kit specific error, I can check this further with the team or create a GitHub issue.
Alternatively, you can use enhanced conversion tracking via Tag Manager as mentioned above, but I am happy to check this further. I noticed you’re using Cloudflare so there may be something there or at original host level that’s impacting your experience.
The topic ‘Checkout – jQuery problem’ is closed to new replies.

