Conversation
supportHello, After updating to the latest version, we are receiving the following error message: “Cannot read properties of null (reading ‘submit’)” Could you please suggest a solution? Thank you.
Hi @tiacovou Thank you for contacting Payment Plugins. Can you share a product url so we can observe that error? Are you using a cache or multiple Stripe plugins on your site? Kind Regards
Hello We are using both, cache and multiple Stripe plugins Thank you
Hi @tiacovou The issue is likely due to the use of multiple Stripe plugins. Are you using “WooCommerce Stripe Gateway”? If so we are working on a change in 4.0.5 that will resolve this. What is happening is the WooCommerce Stripe Gateway plugin is loading a different version of the Stripe JS SDK which causes an error. Can you please share a product page url to your site so we can observe the error and confirm? If you want to keep your site url private please create a support ticket via our plugin’s support widget within your WordPress Admin. Thanks
Hi @tiacovou Thank you for sharing the link. You have the following Javascript error on your checkout page which you will want to resolve as it can interfere with the checkout page functionality: Uncaught TypeError: el.className.match is not a function at checkout/:2657:30 at NodeList.forEach (<anonymous>) at checkout/:2656:38 It looks like that might be some custom code that’s been added to your site. Please reach out to us via the plugins support widget and we will share a pre-release of 4.0.5 which you can test. That should resolve the error you’re seeing due to the 2 Stripe JS versions being loaded. Kind Regards This reply was modified 2 days, 4 hours ago by Clayton R .
Hi @tiacovou Version 4.0.5 has been released which uses the same Stripe JS SDK version as the “WooCommerce Stripe Gateway” plugin which should prevent any errors on the checkout page when using both plugins. Kind Regards
Hi @tiacovou Thank you for contacting Payment Plugins. Can you share a product url so we can observe that error? Are you using a cache or multiple Stripe plugins on your site? Kind Regards
Hello We are using both, cache and multiple Stripe plugins Thank you
Hi @tiacovou The issue is likely due to the use of multiple Stripe plugins. Are you using “WooCommerce Stripe Gateway”? If so we are working on a change in 4.0.5 that will resolve this. What is happening is the WooCommerce Stripe Gateway plugin is loading a different version of the Stripe JS SDK which causes an error. Can you please share a product page url to your site so we can observe the error and confirm? If you want to keep your site url private please create a support ticket via our plugin’s support widget within your WordPress Admin. Thanks
Hi @tiacovou Thank you for sharing the link. You have the following Javascript error on your checkout page which you will want to resolve as it can interfere with the checkout page functionality: Uncaught TypeError: el.className.match is not a function at checkout/:2657:30 at NodeList.forEach (<anonymous>) at checkout/:2656:38 It looks like that might be some custom code that’s been added to your site. Please reach out to us via the plugins support widget and we will share a pre-release of 4.0.5 which you can test. That should resolve the error you’re seeing due to the 2 Stripe JS versions being loaded. Kind Regards This reply was modified 2 days, 4 hours ago by Clayton R .
Hi @tiacovou Version 4.0.5 has been released which uses the same Stripe JS SDK version as the “WooCommerce Stripe Gateway” plugin which should prevent any errors on the checkout page when using both plugins. Kind Regards