Support » Plugin: WooCommerce Stripe Payment Gateway » Issues with Stripe 3.0.3 and 3.0.4

  • Plugin Support Hannah S.

    (@fernashes)


    Automattic Happiness Engineer

    We are aware of the problems that the latest Stripe update (3.0.3 and 3.0.4) caused to some of our customers. A big thanks to those of you who alerted us about the problem: you were crucial in getting this resolved as soon as possible.

    It’s not possible for us to test every possible server configuration, so we also need you to test before updating on your live site. This is especially important when it comes to a business-critical plugin such as Stripe. For more information, please take a look at our update doc:
    https://docs.woocommerce.com/document/how-to-update-your-site/

    Even though we do extensive testing before every update, we are not able to catch all possible configurations. If you were affected, please accept our apologies.

    The technical background is that we had an issue in both versions where certain JavaScript files weren’t included in the plugin. This caused the error Developers: Please make sure that you are including jQuery and there are no JavaScript errors on the page.

    If you have updated to version 3.0.5 of the plugin, done a hard refresh and are still seeing this message, then it is an unrelated issue. Please create a new thread here and we’ll be happy to help.

Viewing 8 replies - 16 through 23 (of 23 total)
  • Just to subscribe, am on 3.02 glad I did not update!

    OK just to update

    I tested this on localhost

    Update from 3.02 to 3.05 – works

    I am using minify in a cache plugin – it’s part of WP Fastest cache

    HTH someone

    Just ran some testing and sure enough – 3.0.2 works like it’s supposed to, 3.0.5 breaks the checkout functionality.

    Either some thorough upgrade instructions or a better release compatible with all systems able to run 3.0.2 would be helpful!

    Here’s the site kellyraeroberts.com

    Plugin Support Hannah S.

    (@fernashes)

    Automattic Happiness Engineer

    @tgriff I’ll be happy to help you, but please create your own thread.

    I put in the first ticket about 11 days ago. I also followed the Woocommerce ticket route as you had suggested. I have to say, it has been 11 days since then, you have gotten several other complaints which only confirm this isn’t an isolated incident, and yet, you do not have a solution.

    It is kind of scary especially for website owners that run a business and make a living through this plugin.

    I will rather pay to have support that fixes a problem than getting something for free, and having to wait weeks before a solution is seen.

    Apart from that, Hannah, you have been very nice, and helpful!

    I appreciate it!

    @fernashes – You’ve now had 8 people on this thread report that this issue is still happening in 3.0.5 and you’ve yet to actually respond to any of us about this issue except to say ‘open a new ticket’ which apparently has already been done by @lictech. The reason we’re all posting here is because this thread claims that 3.0.5 is safe. Has this issue in 3.0.5 even been discussed by the Automattic team?

    @lipctech – they make plenty of money on this free plugin. They’re getting a tiny piece of every $ processed via this plugin, otherwise they never would have made it free.

    Plugin Support Hannah S.

    (@fernashes)

    Automattic Happiness Engineer

    @jprummer – The problem is that the error is very common. It tends to show up when there is a conflict with another plugin or the theme. That’s why each person with an issue with their Stripe plugin needs their own thread, so we that we can troubleshoot each individually.

    I’ve tested each version as it came out, along with other members of our team and the developers, but we haven’t been able to reproduce this issue. Due to the feedback from this thread, I have been monitoring these forums and our tickets but still haven’t seen a situation where the problem can be reproduced on a customer’s site (live or staging). As soon as we’ve got a situation where it can be reproduced and it’s not caused by a third-party add-on, we’ll dig into it.

    Hey Hannah, I totally understand what you say about each one having its own thread but am incredibly disappointed! Whoever is running this plugin clearly does not know how to run a business.

    The issue is still there and I continue to use the 3.0.2 because the same java error appears with the 3.0.5 and I know I am not the only person but among many.

    What Woocommerce Stripe support failed to do, is to login into my site and troubleshoot the error.
    You do this for 10-20 sites and believe you will know what the common culprit/cause of this error will be. That is the way to find this out.

    The replies I got from them, were very disappointing and dismissing. I guess Wooocmerce Stripe developers/owners like to see their business going down. If that is the case, you will never solve it. What a shame!

Viewing 8 replies - 16 through 23 (of 23 total)
  • The topic ‘Issues with Stripe 3.0.3 and 3.0.4’ is closed to new replies.