Still broken

  • Sean

    (@sean-h)


    2 days, 4 hours ago

    So I waited on 10.7.0, after the botched 10.8.1 update. Adaptive Pricing and Visa/Master via Link was working, Bancontact remained off.

    Today I update to 10.8.2. Adaptive Pricing stops working, and Bancontact is miraculously enabled?

    Think I’m going to stay on 10.7.0, for a while. At least that much seems to be working; Visa/Master(Link), and Adaptive Pricing. Belgians must just use cc, even though we’re a Belgian store.

    But even if Bancontact is now working, the only real way to test it is to make a real payment with my own personal Bancontact account, which complicates our book keeping. The Belgian tax department will ask uncomfortable questions, if I keep doing it. And every time I do it we have to remit 21% VAT, and I end up burning through stock, which also costs us, and which is complicated to be refunded from our supplier.

    The only issue now is the circular plugin update arrows right at the top of the menu bar, taunting me. Maybe I’ll hide that with a functions.php snippet.

    I’m trying to launch a store, to earn a living. I don’t have time to fiddle like this.

    If you really need to put a subscription price on this plugin in order to maintain it better, just do it. Basic features can remain free.

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

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Support Frank Remmy (woo-hc)

    (@frankremmy)

    2 days, 3 hours ago

    Hi @sean-h,

    I completely understand the frustration. You’re trying to launch a store and earn a living, and instead you’re stuck firefighting payment method behavior across updates. That’s not the experience you should be having, and I’m sorry it’s been this rocky.

    I checked your previous thread, and a developer was able to reproduce the Bancontact issue about a week ago and flagged it. I’m going to ask the team internally for a status update on where that’s at and will circle back here once I have something concrete.

    In the meantime, one quick question out of curiosity: have you ever had a chance to test Bancontact using Stripe’s test mode? It lets you simulate a real Bancontact payment flow without any actual money changing hands, no VAT, no stock burned, no bookkeeping headaches. Here’s how to set it up if you haven’t tried it: https://woocommerce.com/document/stripe/customer-experience/testing/#using-test-mode

    It won’t fix the underlying issue, but it could at least let you verify the payment flow works without the cost each time you need to check something.

    Thread Starter Sean

    (@sean-h)

    2 days, 1 hour ago

    Problem is, even if I simulate Bancontact or CC, it’s still going to call the API to provision an eSIM. When I was testing with Stripe 4242 etc, I had a sandbox account at my provider, with free stock. Now I’m in full production mode, with paid stock. Re-coding my custom plugin to not make API calls is not an option, not right now.

    I’m at a week long conference right now, to hard launch my store. I will have to leave as is until I get home.

    Several hundred people looking me in the face as they try buy from my broken store…awkward, to say the least.

    In 10 years working with WordPress this has been one of the most problematic plugins I’ve worked with, and I’ve only been using it for a few months now. Can’t say it’s been fun. Pity there’s little to no choice, at this time.

    Plugin Support Frank Remmy (woo-hc)

    (@frankremmy)

    1 day, 1 hour ago

    Hi @sean-h,

    I hear you. Hundreds of people in front of you trying to buy, mid-conference, with a store that isn’t behaving the way it should. That’s an awful position to be in, and I’m sorry the timing on this couldn’t be worse. I also want to acknowledge the eSIM provisioning issue directly: you’re right that simulating a payment would still trigger a real API call to your provider and burn real stock, so suggesting test mode isn’t actually a workable option for your setup.

    Here’s the update from the dev team on all three points:

    • Adaptive Pricing breaking on 10.8.2: Confirmed as a genuine bug. The developer has identified the cause and is actively working on a fix.
    • Bancontact not working (your original issue): This has already been fixed in 10.8.2. The fix is in these two PRs #5550 and #5553.

    Bancontact unexpectedly turning on: This is most likely tied to Bancontact being enabled directly in your Stripe Dashboard settings, rather than something WooCommerce did on its own. Worth checking your Stripe Dashboard’s payment methods configuration when you have a moment, that’s likely where it’s toggled.

    Given where things stand, staying on 10.7.0 for now is a reasonable call until you’re back from your conference and have time to verify things properly. Once the Adaptive Pricing fix ships, we’ll let you know here so you can decide when it’s right to update.

    I hope that helps. Let us know if you need anything else.

Viewing 3 replies - 1 through 3 (of 3 total)

You must be logged in to reply to this topic.