I had Version 3.0.1 still installed, I just noticed an update for Version 3.0.2.(now updated) I will keep an eye on it. thanks!
I’m still cleaning up the vast damage earlier plugin brought. Involves marking unrelated orders as ‘paid’, failing orders that were actually paid, adding Afterpay order IDs to non-Afterpay orders, etc. You can imagine the damage.
Just for informational purposes only, as I have been watching this thread with interest. We are not suffering any of the above issues at all. Have included our setup if anyone wishes to cross reference.
Wordpress v5.7.1
Supermarket Theme (themeasia) v1.0.9
WooCommerce v5.2.2
Afterpay Plugin v3.0.1 (at time of posting, however it will upgrade to v3.0.2)
WooCommerce Dropshipping v2.13
WooCommerce PayPal Checkout Gateway v2.1.1
WooCommerce PDF Invoices & Packing Slips v2.8.3
WooCommerce Stripe Gateway v5.1.0
Plus the standard security, backup, caching plugins which I won’t bother mentioning as I doubt they manipulate the order number or anything remotely close.
We have custom code in the functions.php to not allow certain categories to be paid for with Afterpay, along with other custom coding as well.
As recently as yesterday after the v3.0.1 update, we had several orders go through and all works exactly as it should. We didn’t suffer any of the problems even with the earlier versions of the plugin. Have had Afterpay sales every day, with zero issues.
The workflow of the sale goes as it should, and they sync correctly with the afterpay dashboard.
Hope this information helps someone, even if it looks random.
@danniee21 According to Afterpay devs they have identified the issue (reliance on unreliable data resulting in this clusterf** and addressed it in the 3.0.2. Earlier (when there was no 3.0.2) i’ve reverted to 3.0.0 that was free of that issue.
As of this moment, i’m a big reluctant to update it to the 3.0.1 such late hour and was planning on doing it sometime tomorrow.
Lemme know how this new update stands. Thank you and good night!
@wilfredswholesale Glad to hear that! Considering what the tech-side of the issue was, i suspect you’re just lucky or yet to find the damage. The misfire was small % of all orders, we just have more than a bunch and so the damage is large even tho % is tiny.
Good night everyone. I look forward updating to 3.0.2. Thank you @afterpayit for your quick response on this issue.
@vahanavagyan1 Thanks, I hope everything works out for you!
I just had a few orders went out, I guess I will have eat the cost of those, maybe a tax write-off for next year. I will keep you posted, have a great night!
@danniee21 Any issues with the 3.0.2 so far?
FYI; We’ve updated to Version 3.0.2. Will keep you posted.
@afterpayit @galbaras So far, so good. Close this ticket. Thx.
Hi @vahanavagyan1,
Thanks for verifying the update. The thread will now be resolved. Thank you also for your patience and cooperation identifying and investigating the challenge.
Also, thanks @wilfredswholesale for your valuable contribution. This will useful to better understand the root cause. The team has a high level of confidence that version 3.0.2 addressed the challenge, however, investigation is still ongoing.
Thank you @danniee21 for your comments. Please start a new thread if any further support is needed.
Thanks also to @galbaras for your input; your exemplary caution in your approach to major updates is to be commended.
Thank you all.
