• Resolved janthegroat

    (@janthegroat)


    After upgrading to 9.2.0 the checkout process throws this error: “There was an error registering the payment method with id ‘express_checkout_element’: Error: Stripe initialization data is not available”

    The previous version worked fine, even after upgrading to Woocommerce 9.6.2 and WordPress 6.7.2

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

Viewing 15 replies - 1 through 15 (of 15 total)
  • Plugin Support shahzeen(woo-hc)

    (@shahzeenfarooq)

    Hi there!

    I understand that you are encountering an error message after upgrading to version 9.2.0. I checked the checkout page and noticed some JavaScript errors in the browser console, which may be causing the issue.

    It seems that the latest version might be conflicting with another plugin. To assist you further, could you please share the following details?

    • System Status Report?which you can find via WooCommerce > Status
    • Fatal error logs?(if any) under WooCommerce > Status > Logs.

    Please use?https://pastebin.com/?or?https://gist.github.com/ and share a link to that paste in reply here. Once we have more information, we’ll be able to assist you further.???????????????????????????????????????????????????????????

    Also, in the meantime, I would suggest you run a conflict test by deactivating all plugins except WooCommerce and the Stripe payment gateway plugin.

    I’m suggesting this because I am not able to see any errors with the latest version of the Stripe plugin on my site.

    For more details on how to run a conflict test, you can refer to this article:
    How to test for conflicts

    Thank you

    Thread Starter janthegroat

    (@janthegroat)

    Hi! Thank you so much for looking at this. The status report and fatal errors are here: https://gist.github.com/admin-jackieteachesenglish/f0ff8dcc8509ec48a40553d36f6aba1e

    I’ll check for conflicts as well.

    Thread Starter janthegroat

    (@janthegroat)

    I deactivated all plugins and it made no difference to the behavior. I also cleared caches/browser caches and disabled the cache on Chrome, which also had no effect. Very specifically, the plugin that is causing the problem is WooCommerce Stripe Payment Gateway version 9.2.0. The previous version 9.1.1 does not have this behavior is and working perfectly.

    Plugin Support Zubair Zahid (woo-hc)

    (@doublezed2)

    Hello janthegroat,

    Thank you for your reply.

    I understand you deactivated all plugins except WooCommerce and Stripe plugins but the error is still showing up.

    I can see you have set up a staging site, this is a good step and will help in troubleshooting.
    Could you please make it publicly accessible and disable all plugins except WooCommerce and Stripe?
    Also, change the theme to Twenty Twenty-Four.

    Please let me know when these changes are done so I can check the site from my end.

    Best regards.

    Thread Starter janthegroat

    (@janthegroat)

    Hi Zubair Zahid (woo-hc)

    I did as you asked and you should be able to view the staging site (https://staging2.jackieteachesenglish.com/). At first, I thought that switching to Twenty Twenty-Four had fixed the issue, but I can still reliably create it by doing this:

    1. Add a lesson package to the cart (Go to /shop, select “American English Accent Coaching – Package”, click “Add to Cart”, then click View Cart.
    2. Click “Proceed to Checkout”
    3. Use the browser’s back button to return to the Cart page. The error usually appears right away. A couple of times I’ve had to refresh that page to get it to appear.

    Thank you so much for looking into this.

    Plugin Support Moses M. (woo-hc)

    (@mosesmedh)

    Hi @janthegroat,

    Thank you for making the staging site publicly accessible. I followed the steps you provided but wasn’t able to reproduce the issue. I also refreshed multiple times, and everything appears to be working fine.

    It also looks like express checkout isn’t enabled on the staging site. Could you confirm which express checkout option is active? If possible, please also share a screenshot of the error.

    Thread Starter janthegroat

    (@janthegroat)

    Hi @mosesmedh,

    I have attached screenshots to the bottom of the original gist.github link (https://gist.github.com/admin-jackieteachesenglish/f0ff8dcc8509ec48a40553d36f6aba1e). I have included screenshots of the issue shown on two staging sites, one with all plugins active and the other with no plugins active. Express checkout is enabled on the staging sites – with Link By Stripe being the only options selected. I do notice that once I put something in the cart and then view the cart, the page has “__trashed” added to the URL. (https://staging2.jackieteachesenglish.com/__trashed/) Is that normal?

    Thank you again!

    Janice

    Plugin Support Moses M. (woo-hc)

    (@mosesmedh)

    Hi @janthegroat,

    Thank you for getting back to me.

    I’ve reviewed your system status report, and I noticed that you still have 25 active plugins on your staging site. Please try deactivating all plugins except WooCommerce and the Stripe payment gateway plugin. Additionally, switch your theme to Twenty Twenty-Five, as the error log you shared suggests a possible issue with Coachify Pro and possibly the Coachify theme.

    Once you’ve done that, please update the system status report again. Also, I checked your site and couldn’t see the error on my end. I was able to click on “Pay with Link” without any issues.

    Could you clarify when exactly the error appears? Does it show up as soon as you visit the cart page, or only after clicking “Pay with Link”? Also, when you click “Pay with Link,” does the login popup for email appear, and does the redirect work correctly?

    Providing more details on when and how the error occurs would be really helpful, as I’ve followed the steps to reproduce the issue but couldn’t encounter it on my end. Looking forward to your response!

    Everything appears to be functioning correctly on both the cart and checkout pages. Even when I navigated back to the cart page, no errors appeared.

    Could you check your browser’s developer console to see if there are any JavaScript errors?

    Lastly, regarding the “__trashed” issue, it seems like this might be the URL of your cart page. Please go to Pages, click on Quick Edit for the cart page, and check the slug. Is it “cart” or “__trashed”?

    Looking forward to your feedback.

    Thread Starter janthegroat

    (@janthegroat)

    Hi @mosesmedh ,

    Sorry, the system status report on that link was old: I had already switched off all plugins. I’ve now switched to theme Twenty Twenty-five and the new status report is here, along with a screen shot of the error on that configuration: https://gist.github.com/admin-jackieteachesenglish/cf5d22b0d3157df9207ef3c2e0dd816f

    Chrome is displaying this error: 418Denying load of <url>. Resources must be listed in the web_accessible_resources manifest key in order to be loaded by pages outside the extension.

    I can’t seem to upload the Chrome .log file to gist.github, so I added another screenshot.

    To recreate:

    https://staging2.jackieteachesenglish.com/.

    1. If you already have something in the cart, remove it, then go to the /shop page and add a lesson package , click “Add to Cart”, then click View Cart.
    2. Click “Proceed to Checkout”. (Don’t click Pay with LInk). The error intermittently appears here.
    3. If it doesn’t appear, use the browser’s back button to return to the Cart page. You might have to refresh a couple of times.

    Thank you so much!

    Thread Starter janthegroat

    (@janthegroat)

    @mosesmedh

    I diagnosed the ‘418Denying load of <url>” error as being a DuckDuckGo extension. I turned it off and those errors vanished, but it did not fix the Stripe express checkout element error.

    Plugin Support Jonayed (woo-hc)

    (@jonayedhosen)

    Hi @janthegroat ,

    I’m glad to hear that the issue is resolved and that you’ve pinpointed the extension causing it.

    Regarding the Stripe element appearing broken, I tried to check the issue on my end but couldn’t reproduce it. It looks like it might be a browser caching issue displaying an older version.



    Would you mind trying the following?

    • Check the issue in a new browser or incognito window.
    • If you have any caching plugins, try clearing the cache to see if that resolves it. Here’s a helpful guide: How to Clear Your Cache in WordPress.

    If this isn’t the issue you’re referring to, could you send us a screenshot for more context? That would help us investigate further. If you don’t already have a screenshot tool, you can use Snipboard.io to easily share screenshots.

    Let me know what you find! ??

    Thread Starter janthegroat

    (@janthegroat)

    Hi @jonayedhosen

    I’ve uploaded a screenshot here: https://snipboard.io/kX8n0z.jpg

    There are several more at the bottom of the comments here: https://gist.github.com/admin-jackieteachesenglish/cf5d22b0d3157df9207ef3c2e0dd816f.

    I tried using an incognito window as you suggested and the problem did not occur, which is good news. If that indicates a caching problem, are there steps I can take to ensure this doesn’t occur in a non-incognito browser window?

    Plugin Support Zubair Zahid (woo-hc)

    (@doublezed2)

    Hello janthegroat,

    Thank you for your reply.

    I am glad to know that you have pinpointed the cause of the problem.
    Since this issue is related to cache, I recommend clearing the cache on your site and server (if server cache is enabled).

    Also, I recommend checking your browser and all the extensions you have installed on it.
    Sometimes, a browser can cause issues related to the cache.

    Please let me know how it goes. ??

    Best regards.

    Thread Starter janthegroat

    (@janthegroat)

    Hi @doublezed2, @jonayedhosen, @mosesmedh, and @shahzeenfarooq

    Thank all of you for your assistance. I would never have figured out it was an odd caching issue. I use Siteground and their Speed Optimizer caching and was able to exclude the shop, cart, and checkout pages from caching. I think that’s solved the issue. Thank you so much for the time you spent on this – I’m very grateful.

    Plugin Support Zubair Zahid (woo-hc)

    (@doublezed2)

    Hello janthegroat,

    Thank you for your reply.

    I am glad to know that you have resolved the issue.

    If you feel that WooCommerce Stripe has been beneficial to your business, we would be truly grateful if you could take a few moments to leave a review.

    Your feedback not only supports our continuous improvement but also helps others make informed decisions about using WooCommerce Stripe.

    Have a great day!

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