• Resolved Alfio Piccione

    (@picaland)


    Hi,

    Lately some customers complain that they can’t complete the payment because of this error or “null is not an object (evaluating e.submit)”.

    I can’t recreate the problem, I’ve tested from different browsers (Chrome, Firefox, Safari) but I don’t get any error.

    Can you tell me what I can do to avoid the problem?
    Thanks!

    The page I need help with: [log in to see the link]

Viewing 15 replies - 1 through 15 (of 18 total)
  • Plugin Support omarfpg a11n

    (@omarfpg)

    Hi @picaland,

    I just tested the checkout on your site, and I see the Credit Card fields aren’t showing up, thus causing the error you mentioned:

    Direct link to the image: https://snipboard.io/569Hns.jpg

    Upon further inspection, I see that an instrumental JS file isn’t loading in your site, the payment-requests.js. I also see the following errors in the browser’s console:

    Direct link to the image: https://snipboard.io/JfT450.jpg

    With this in mind, I’d like to troubleshoot a few things, first, I see you’re using the Siteground’s Speed Optimizer plugin. Can you please make sure first to properly configure this caching plugin for WooCommerce? You can learn more here: https://developer.woocommerce.com/docs/how-to-configure-caching-plugins-for-woocommerce/.

    If this doesn’t fix it, a full conflict test would be in order.

    Please keep us posted.
    -OP

    Thread Starter Alfio Piccione

    (@picaland)

    Hi @omarfpg

    The Siteground Speed ??Optimizer caching plugin doesn’t have many configurations, I excluded the recommended WC pages from the cache and the /checkout/ page is definitely excluded

    I still can’t find the errors in the console whether logged in or not

    but I can’t do anything other than disable the minidication and combination of js. could that be the problem?

    Thread Starter Alfio Piccione

    (@picaland)

    Hi @omarfpg
    I deactivated the WooCommerce Stripe Gateway plugin which was active but not used as a payment gateway. I currently only use WooPayments, so do you still encounter the same problem?

    Thread Starter Alfio Piccione

    (@picaland)

    Hi @omarfpg

    By disabling the WooCommerce Stripe Gateway plugin from anonymous and not logged in I get the error in the console.. how can we solve it? I also tried to disable the cache plugin but the error remains.

    Plugin Support Rajesh K. (woo-hc)

    (@rajeshml)

    Hello @picaland,

    Sorry to know that disabling these plugins didn’t help. I would also suggest a full conflict test could help us with identifying if anything external is conflicting here.

    To run the conflict test, you’ll first want to change the theme on your site to?Storefront or Twenty Twenty-Four, then check to see if the issue is still present. If that resolves the issue, you’ll want to get in touch with your theme’s developer and see if they have an update or fix for you.

    If changing the theme doesn’t help, you’ll want to deactivate all plugins except for WooCommerce and WooPayments and take a look. If that fixes the problem, re-enable the other plugins one by one (gradually), checking after each, to see where the issue is coming from.

    Be sure you have a good backup in place of your full site and database. You can ask your host for backup functionality or you can consider using a service like Jetpack. If something goes wrong, you will be able to restore it.

    I hope that helps! Let us know once you have done a conflict test!

    Thread Starter Alfio Piccione

    (@picaland)

    Hi @rajeshml

    Yes thanks for your intervention, I am also a wordpress developer and I know the conflict tests.

    but apart from that, I created a staging https://staging4.woopop.it/ from the live site, where the only difference is the safe mode of WCpayments

    here I do not find errors.

    Curious as what….

    Hey, @picaland!

    Thanks for the staging site link!

    I checked it and noticed that the credit card fields are showing correctly there, so it seems that confirms what my colleague found regarding this causing the issue.

    As I understand the only difference between the live and staging version is that WooPayments is on test mode, correct?

    All other plugins are exactly the same, including being on the same version?

    The reason I’m asking is because this is commonly caused by a plugin/theme conflict.

    What version of Woo and Woopayments are you using?

    Looking forward to your reply.

    Have a wonderful day!

    Thread Starter Alfio Piccione

    (@picaland)

    Hi @carolm29

    Yes, I tell you that all the plugins are the same and they are all the same version, as mentioned the only difference is the safe mode of WooPayments.

    for more details I will provide you with the staging status report
    https://gist.github.com/Picaland/3bdf53deef829d1ea43542c1a835df70

    Hey, @picaland!

    Thanks for confirming!

    I checked your SSR and did not see anything unusual.

    Are you able to temporarily switch to test mode on the live site just to check if the credit card fields show up normally?

    Can you also please confirm the country your webstore is set to?

    Looking forward to your reply.

    Have a wonderful day!

    Thread Starter Alfio Piccione

    (@picaland)

    Hi @carolm29,

    This morning before trying to switch to test mode on the live site, I checked the checkout and inexplicably now I do not see the error … can you confirm it for me too ?

    very strange… at this point I wonder what caused the error the past few days?

    Thanks!

    Plugin Support Zubair Zahid (woo-hc)

    (@doublezed2)

    Hello Alfio Piccione

    Thank you for your reply.

    I checked the live site and noticed a few errors in the console.
    Here is a screenshot:

    Could you share a screenshot from your end?
    This will help me compare your results with mine.

    Looking forward to your response. ??

    Best regards.

    Thread Starter Alfio Piccione

    (@picaland)

    Hi @doublezed2

    mmm strange this morning the error wasn’t present, now instead it is..
    https://snipboard.io/lWpEuq.jpg

    Thread Starter Alfio Piccione

    (@picaland)

    Hi @doublezed2
    other info, I activated the test mode for a moment and the problem remains
    https://postimg.cc/672rxvJh

    Hey, @picaland!

    Thanks for the info!

    ?I activated the test mode for a moment and the problem remains
    https://postimg.cc/672rxvJh

    Can you please try deactivating WooPayments and removing it. Then downloading it again to see if the issue is solved?

    Looking forward to your reply.

    Have a wonderful day!

    Thread Starter Alfio Piccione

    (@picaland)

    Hi @carolm29
    I deleted the plugin, reinstalled it but unfortunately it doesn’t change anything.

    Thanks for your support but I don’t know what to do anymore…
    it’s all very strange

Viewing 15 replies - 1 through 15 (of 18 total)
  • You must be logged in to reply to this topic.