Posted: December 30, 2019 at 10:06 am
Hello! I recently installed WooCommerce on my website to sell books and have been trying to get it to work. I receive an error in regards to Node.js whenever I try to complete a purchase. I removed the functions involving Event Espresso and it then works. There seems to be a conflict between Event Espresso and Woocommerce. Would you have any work arounds for this error? Chris
|
|
Hi, May I ask what’s the exact text of the error message, are there additional errors in the console, and which WooCommerce payment gateway are you using for WooCommerce? |
|
The error I receive is “An error occurred, please try again or try an alternate form of payment. I am using the Authorize.net for both Event Espresso and WooCommerce. Could it be because I am using the same API Login and Transaction key? |
|
It’s not likely from using the same API Login and Transaction key. I checked the site and there is a JavaScript error being thrown on the page near where the WooCommerce Authorize.net gateway loads its scripts, and if the JS error happening earlier on in the page can be resolved everything may be allowed to work as expected. Here’s the block of JS code that’s throwing the error:
The above looks like there was some copy/paste related errors where there’s a mismatch of closing script tags and likely just the parts of the same code was pasted in twice. If you, or the individual on your team that added the above code, can review and fix the code in question, you could then test the WooCommerce gateway again and check the browser’s console for any other errors if it still does not work. |
|
I found one other error that’s related to using Event Espresso but it’s not coming from Event Espresso. Here’s a screenshot of both errors, and the second error, the Uncaught ReferenceError, is from a custom script loaded from the site’s theme: https://slack-files.com/T02SY781D-FRTT64FA7-36c57a8aec The second error in the screenshot is coming from your site’s wp-content/themes/gsb-2019-new/assets/js/ticket_selector.js file, on line 11. The simple solution for there would be to not use the eei18n localized variable and instead just use your own text string in your custom script. |
|
The support post ‘WooCommerce (2)’ is closed to new replies.
Have a question about this support post? Create a new support post in our support forums and include a link to this existing support post so we can help you.