• Resolved ecosciences

    (@ecosciences)


    We are experiencing issues since this update.

    Errors at checkout page are:
    1. An error occurred, please try again or try an alternate form of payment.
    2. 3D Secure Verification Token is missing

    Looking around on other threads, we’ve tried the following with no resolve to this issue. We take a lot of orders online per day, for thousands of dollars so this is a major issue for our company to deal with.

    We’ve tried the following to resolve this issue:
    1. Disconnect Square in WooCommerce, reconnect.
    2. Enabled the address 2 and we are still getting “An error occurred, please try again or try an alternate form of payment”.

    —- We have tried Visa & Mastercards. Also seeing “3D Secure Verification Token is missing” in logs. Just started seeing this error late yesterday. Payment will not process.

    • This topic was modified 4 years, 9 months ago by ecosciences.
Viewing 10 replies - 16 through 25 (of 25 total)
  • Hello – I’m having the same issue and have tried every solution under this thread with no luck. I’ve rolled back to 2.08… I’ve made address line 2 mandatory… I’ve cloned the site and migrated to another server to see if this was a host issue. I’ve also tried the code snippet as outlined above and still not having any luck.

    The last thing I’ve tried was de-activating all of my plugins except for Woo and Square… but I have 2 mandatory additional plugins… Udesly (which converts some elements I built in webflow)… as well as “Advanced Custom Fields Pro.” So 4 plugins total… but am still having the error.

    Any other ideas here? This is kind of crazy!! Can’t believe between Square and Woo that we don’t have a stable plugin to use.

    I’ve rolled back to 2.08 and payments were able to go through

    Thread Starter ecosciences

    (@ecosciences)

    @livesyzygy Have you checked Chrome > Developer Tools > Console to see if there is any JS errors at checkout? Most of the issues I’ve seen with 2.0.8 were related to jQuery not loading before the square scripts. So you’d see errors in Console which would point to to jQuery not defined specifically.

    We did not use address 2 mandatory, actually it’s still hidden if that’s any help. 2.0.8 is working for us after rollback.

    We’re not using the two plugins you outlined here, but we are using about 30 others, mostly by WooCommerce.

    Yes – The JS error is the following… [Analytics] A token request is already in place e.gettoken @data.js:18

    Thread Starter ecosciences

    (@ecosciences)

    @livesyzygy I can’t say that I can “fix” any issues for you, but if you post up the website URL in question others might also be able to chime in on errors. I can take a quick look and see if I see anything standing out in Console by looking at your checkout.

    Thanks so much for taking a look! Any and all ideas are welcome right now… The URL is https://www.livesyzygy.com

    Thread Starter ecosciences

    (@ecosciences)

    @livesyzygy this is definitely a different issue than what most are experiencing with 2.1.0 update, just laying this out here since it pertains to 2.0.8 also with your site.

    Looking at your checkout I don’t see the typical 2.1.0 or 2.0.8 JS error issue, so that’s off the table. Beyond me actually placing an order to see the full effect of your checkout and errors I can’t say much more except look at the information below to further troubleshoot.

    ** Regarding 2.0.8 there was another thread here: https://www.ads-software.com/support/topic/a-token-request-is-already-in-place/ That outlined this specific issue you are having could be due to a WordPress caching issue. Looks like you’ve already done the step by step of trying to test for plugin and theme conflicts so you’re past that step, but caching is another thing.

    Not sure what caching tools you might be using in your WordPress build, but caching in WordPress helps speed up the site a lot but also seems to cause a lot of issues if not correctly cleared after plugin updates/downgrades and or coding changes. I would start with digging into clearing cache inside WordPress Admin. There are plugins for this and even some provided by your hosting provider (SiteGround provides SG Optimizer) but you’ll have to figure out what tool you want to use to handle this.

    Hi @ecosciences,

    Thank you for taking the time to assist with these issues! Are the issues still happening? We are tracking currently an issue with saved cards not processing correctly, along with a few others.

    For the site https://livesyzygy.com/ I checked the Console and I do see a call for a token already in place:

    https://d.pr/i/MeYA1K

    This particular message should have been resolved in the 2.1.0 update. If you are on 2.0.8 (as you mentioned in your first post), do the following:

    – Disconnect Square
    – Disable and Remove Square plugin from WooCommerce > Plugins > All Plugins
    – Re-install the plugin from this repo
    – Re-connect Square and test to see if the error persists.

    Let us know!

    Hey Guys – I went to code canyon and bought a 3rd party square plugin that fixed the problem and is working great for me! I tried everything for the Woo provided plugin and couldn’t get anywhere. This worked perfect the first time.

    https://codecanyon.net/item/woocommerce-square/22136956

    Hope this helps anyone else who is stuck!

    i cant believe this is a real plugin….constant errors, broken features every upgrade, constant rolling back. i used to like square but this plugin has left such a bad taste in my mouth i just want to get as far away from square as possible.

Viewing 10 replies - 16 through 25 (of 25 total)
  • The topic ‘Version 2.1.0 errors / issues’ is closed to new replies.