John Gudmundson

BTW, I have just uninstalled this plugin because of lack of support. I am handling bulk discounts manually at this point until something better crosses my path.

Ducksportsfan: I think you have a different issue altogether. I think yours is a configuration issue. In the woocommerce settings under bulk discount, make sure you have “Treat product variations separately” unchecked. This causes the bulk discount counts to occur across all variations within a product, whereas if you have it checked it will behave as yours seems to be.

Also reported a bug against woocommerce plugin https://www.ads-software.com/support/topic/cant-drag-and-drop-product-variations-anymore?replies=1. That was 2 weeks ago with no developer response. I wonder if they care….

So I tested the feature in 1.35 and it works great. Made a small donation to your coffee money. Thanks again.

John

Hi Stephen,

Excellent! I will try to install and test 1.35 tomorrow.

Really appreciated!

John

Hi Stephen,

Yes, current order total.

BTW, though it should be obvious to the admin, a nice to have would be a warning if the current order total
exceeds the original authorized amount at the time the capture is about to occur. I would think Stripe would prevent any amount
greater than the auth amount from being captured, but I’m not sure if the capture API would give some sort of failure code or just
complete quietly. For me, I know that if a customer adds to and order after it is made, I will have to re-invoice, but there could be subtle cases where a minor change is made to an order that slightly increases the total.

Many thanks!

John

Hi Sean,

How did you make out with that “other angle of attack?” I’ve rolled back to 0.12, which is a stable version the works for me until you tell me that you are comfortable you have the race condition and the “uncaught type error” issues under control.

Thanks,

John

Hi Sean,

FYI
I ssh’d to my bluehost account and did a find command to look for superfish.js. It showed up under the wootique theme I am using.

John

Ok, I upgraded to .16 and it works. Let me know if you want me to downgrade to .15 so you can give that a try.

John

Sorry for the delay. Since I don’t know the chrome debug stuff, the next best thing is that I give you the URL that will get you to the checkout:

northarmknives.com/product/test

I’ve left striper .12 in place until you can try this. Then I can try .16
if needed.

Thanks for all you are doing.

John

Hi Sean,

Yes I had updated to the latest woo (2.0.20). I updated striper to .15 and the problem still existed. I am running wordpress framework 3.6.1 BTW.

So, I used Updraft to restore my plugins to the state they were Nov 21st and tried again and everything worked again. The only 2 plugins that changed since Nov 21 were striper and woocommerce. The working versions are striper .12 and woo 2.0.19

Then I updated striper to .15 and the system stopped working. Then I updated woo to 2.0.20 but it remained broken. I cleared cookies in the browser and restarted. No change.

Next I updated WP to 3.7.1 and reverted back to striper .12 and woo 2.0.19 and it works. Then I updated woo to 2.0.20 and it kept working. Lastly, I updated striper to .15 and it stopped working with the same error message as I noted above. I tried with a different browser on another computer and it still doesn’t work.

Conclusion is that .15 does not work for me regardless of woo or WP versions, whereas .12 works with all the combinations.

John

Hi Sean,

I can’t give you a URL, but I can say that the test I made was from the front end: a regular web order. I didn’t try anything on the backend with .14.

Good luck.

John

Oh, I see now there was a bug in .14. I’ll look for the next update. Still, how do I revert to an older version, just in case?

Thanks,

John

Hi Sean

I installed .14 and tried to make 2 orders from the web. Both failed
on order submit with a message from stripe saying:

“Payment error:You must supply either a card or a customer number…”

At the back end the orders were created, but there seems to be some striper internal error because unlike the previous behavior, no custom fields were created in the failed orders (eg key or transaction_id).

Are the old versions of the plugin available to revert back to (eg .12)?

Thanks,

John

Hi Sean,

Tested .11 and found it to work as expected for reduced-charge orders.
Great job adding the feature.

BTW, related to ruess’ remarks, all the testing I’ve done so far with the auth and capture setting shows no difference in behavior whether it’s turned on or off.

Thanks,

John