Hey there!
It’s possible that your theme is causing a problem because it overrides WooCommerce’s default templates improperly. The simplest check for this is to either switch totally to a default theme(Twenty Seventeen or Storefront) or move your template overrides temporarily out of the theme directory.
Most theme authors fix their themes in a timely manner, so you can contact the theme developer to have them update the templates.
If the theme is not updated, or if you modified the templates yourself or are using a child theme, you would need to update the templates yourself.
You can read more about how to update the templates here:
https://docs.woocommerce.com/document/fix-outdated-templates-woocommerce/
Hi! Thanks for replying!
I thought about that too, but WooCommerce articles tells that the checkout page is not affected by any compatibility issue, for the HTML structure is simply rendered on the template’s default page… but I’ll check that! (I modified the templates files)
I’m also in contact with the template developer.
Do you think this might be happening for jQuery reasons?
The Order Details area is refreshed via JavaScript so that every time the shipping address is modified the shipping amount is recalculated.
If you have JavaScript errors on the Checkout page it can prevent that “refresh” JavaScript from running. I see JavaScript errors on your product and checkout pages:
http://cld.wthms.co/uSdg3
I would start here:
https://codex.wordpress.org/Using_Your_Browser_to_Diagnose_JavaScript_Errors
Hey, thank you very much!
Actually, this is a conflict I’ve already KINDA solved…
This conflict is related to the payment gateway I’m using.
This is the line mentioned:
var checkIfInputHasDefaultBehavior = $(“#checkInputClass”).css(“background-image”).includes(“url”);
I was suggested to turn that into
var checkIfInputHasDefaultBehavior = $(“#checkInputClass”).length && $(“#checkInputClass”).css(“background-image”).includes(“url”);
this actually fixed the issue, but it generates a new warning, so I’m not sure this workaround actually works.
But I’ll implement that workaround again, then, may you check again?
I’ve found out some differences between the consoles of different templates:
– When I’m using the conflicting template, this is what console gives me (I didn’t include details cause they are too long)
12:56:56.508 JQMIGRATE: Migrate is installed with logging active, version 1.4.1
12:56:56.511 VM2306 jquery-migrate.js?ver=1.4.1:45 JQMIGRATE: jQuery is not compatible with Quirks Mode
12:56:56.697 Navigated to http://medicinecursos.com.br/novosite2017/finalizar-compra/
12:56:56.715 VM2304 webfont.js:35 GET http://medicinecursos.com.br/novosite2017/wp-content/plugins/js_composer/assets/lib/bower/font-awesome/fonts/fontawesome-webfont.woff2?v=4.6.3 net::ERR_ABORTED
12:56:57.045 VM2305 jquery.js?ver=1.12.4:3 [Violation] Added synchronous DOM mutation listener to a ‘DOMNodeInserted’ event. Consider using MutationObserver to make the page more responsive.
12:56:57.180 VM2305 jquery.js?ver=1.12.4:3 [Violation] Added non-passive event listener to a scroll-blocking ‘touchstart’ event. Consider marking event handler as ‘passive’ to make the page more responsive. See https://www.chromestatus.com/feature/5745543795965952
12:56:57.215 VM2328 selectWoo.full.js?ver=1.0.1:6302 [Violation] Added non-passive event listener to a scroll-blocking ‘wheel’ event. Consider marking event handler as ‘passive’ to make the page more responsive. See https://www.chromestatus.com/feature/5745543795965952
12:56:57.238 VM2328 selectWoo.full.js?ver=1.0.1:6302 [Violation] Added non-passive event listener to a scroll-blocking ‘wheel’ event. Consider marking event handler as ‘passive’ to make the page more responsive. See https://www.chromestatus.com/feature/5745543795965952
12:56:57.330 VM2328 selectWoo.full.js?ver=1.0.1:6302 [Violation] Added non-passive event listener to a scroll-blocking ‘wheel’ event. Consider marking event handler as ‘passive’ to make the page more responsive. See https://www.chromestatus.com/feature/5745543795965952
12:56:57.347 VM2328 selectWoo.full.js?ver=1.0.1:6302 [Violation] Added non-passive event listener to a scroll-blocking ‘wheel’ event. Consider marking event handler as ‘passive’ to make the page more responsive. See https://www.chromestatus.com/feature/5745543795965952
12:56:57.383 VM2306 jquery-migrate.js?ver=1.4.1:45 JQMIGRATE: jQuery.parseJSON requires a valid JSON string
12:56:57.383 VM2306 jquery-migrate.js?ver=1.4.1:47 console.trace
12:56:57.416 VM2354 perfect-scrollbar.jquery.min.js?ver=0.6.12:2 [Violation] Added non-passive event listener to a scroll-blocking ‘wheel’ event. Consider marking event handler as ‘passive’ to make the page more responsive. See https://www.chromestatus.com/feature/5745543795965952
12:56:57.417 VM2354 perfect-scrollbar.jquery.min.js?ver=0.6.12:2 [Violation] Added non-passive event listener to a scroll-blocking ‘touchstart’ event. Consider marking event handler as ‘passive’ to make the page more responsive. See https://www.chromestatus.com/feature/5745543795965952
12:56:57.417 VM2354 perfect-scrollbar.jquery.min.js?ver=0.6.12:2 [Violation] Added non-passive event listener to a scroll-blocking ‘touchmove’ event. Consider marking event handler as ‘passive’ to make the page more responsive. See https://www.chromestatus.com/feature/5745543795965952
12:56:57.501 VM2328 selectWoo.full.js?ver=1.0.1:6302 [Violation] Added non-passive event listener to a scroll-blocking ‘wheel’ event. Consider marking event handler as ‘passive’ to make the page more responsive. See https://www.chromestatus.com/feature/5745543795965952
12:56:57.520 VM2328 selectWoo.full.js?ver=1.0.1:6302 [Violation] Added non-passive event listener to a scroll-blocking ‘wheel’ event. Consider marking event handler as ‘passive’ to make the page more responsive. See https://www.chromestatus.com/feature/5745543795965952
12:56:57.549 VM2305 jquery.js?ver=1.12.4:2 [Violation] ‘DOMContentLoaded’ handler took 400ms
12:56:57.578 [Violation] Forced reflow while executing JavaScript took 136ms
12:56:57.664 [Violation] Forced reflow while executing JavaScript took 53ms
12:57:00.095 VM2305 jquery.js?ver=1.12.4:4 XHR finished loading: POST “http://medicinecursos.com.br/novosite2017/?wc-ajax=get_refreshed_fragments”.
12:57:00.573 VM2305 jquery.js?ver=1.12.4:4 XHR finished loading: POST “http://medicinecursos.com.br/novosite2017/?wc-ajax=update_order_review”.
– When I set Twenty Seventeen, this is what it gives me:
12:59:30.968 Navigated to http://medicinecursos.com.br/novosite2017/finalizar-compra/
12:59:31.248 jquery-migrate.js?ver=1.4.1:23 JQMIGRATE: Migrate is installed with logging active, version 1.4.1
12:59:31.250 jquery-migrate.js?ver=1.4.1:45 JQMIGRATE: jQuery is not compatible with Quirks Mode
12:59:31.250 jquery-migrate.js?ver=1.4.1:47 console.trace
12:59:31.415 VM2444:1 Uncaught ReferenceError: google is not defined
12:59:31.661 jquery.js?ver=1.12.4:3 [Violation] Added synchronous DOM mutation listener to a ‘DOMNodeInserted’ event. Consider using MutationObserver to make the page more responsive.
12:59:31.718 jquery.js?ver=1.12.4:3 [Violation] Added non-passive event listener to a scroll-blocking ‘touchstart’ event. Consider marking event handler as ‘passive’ to make the page more responsive. See https://www.chromestatus.com/feature/5745543795965952
12:59:31.728 realia.js?ver=1.2.1:133 Uncaught TypeError: $(…).not(…).colorbox is not a function
at HTMLDocument.<anonymous> (realia.js?ver=1.2.1:133)
at i (jquery.js?ver=1.12.4:2)
at Object.fireWith [as resolveWith] (jquery.js?ver=1.12.4:2)
at Function.ready (jquery.js?ver=1.12.4:2)
at HTMLDocument.K (jquery.js?ver=1.12.4:2)
Hey, thank you very much!
Actually, this is a conflict I’ve already KINDA solved…
This conflict is related to the payment gateway I’m using.
This is the line mentioned:
var checkIfInputHasDefaultBehavior = $(“#checkInputClass”).css(“background-image”).includes(“url”);
I was suggested to turn that into
var checkIfInputHasDefaultBehavior = $(“#checkInputClass”).length && $(“#checkInputClass”).css(“background-image”).includes(“url”);
this actually fixed the issue, but it generates a new warning, so I’m not sure this workaround actually works.
But I’ll implement that workaround again, then, may you check again?
I’ve also founded some differences between the consoles when using different templates, I sent that through a comment but I think it is under approval, so…
Plugin Support
Hannah S.L.
(@fernashes)
Automattic Happiness Engineer
I’m glad to hear that you found a solution – thanks for letting us know!
