• Paid for the Premium version, but there is a critical error in the Free version that the paid version relies on. Advanced Coupons Plugin support claimed that the issue was “new” even though it was reported here four months ago in a Support post.

    We have had the plugin two days. Made a Refund request immediately after have two issues in those two days. Now Advanced Coupons is putting up roadblocks to get a refund.

    We complied with the refund request as described on the site and now they are requesting as screenshot to verify the plugin is deleted. Now it appears our two-day old password was disabled.

    My client had to reset the password so we could send the additional image showing the Advanced Coupons plugins were deleted. (Free and Premium version deleted, but all this company had to do was deactivate or Premium license. The Free plugin is useless since that is root of the problem with the Expiry date.

    This company should be avoided at all costs. The free plugin is broken and will trash all your Expiry dates. Then they will send you a snippet of PHP code to install in functions.php. If this was a trusted vendor that fixed problems and that PHP was a short-term fix, maybe. This is a vendor that told me yesterday this was a new problem, when in fact it wasn’t.

    Massive fail, no trust and dishonesty are not what anyone pays for.

    Also, the plugin is bloated with nags for other plugins. Every page under the Dashboard nags to add this or that free or premium plugin. I’d have put up with that IF the plugin worked.

    I will also make any and all exchanges with Support, available to back up our experience or as necessary.

    • This topic was modified 2 weeks, 2 days ago by Wudman. Reason: Add additional details
Viewing 1 replies (of 1 total)
  • Plugin Support Fauzan Azizie

    (@fauzanade)

    Hi @wudman,

    You’re right that this was reported on this forum in March. Our team replied, couldn’t reproduce it, and the thread was left there without ever being logged with our developers. So when you reported it this week you were told it was newly identified, and from the point of view of the person answering you that was true, but only because that earlier report was never recorded anywhere they could see it. The gap is real and it’s ours.

    For anyone else reading this, I want to be precise about what the issue is, because it isn’t data loss. It’s a display problem on the admin coupon list. The Expiry date column shows blank for coupons that haven’t expired yet. The dates are still stored, and coupons still expire correctly at checkout. You can confirm that yourself: deactivate Advanced Coupons for WooCommerce Free and the expiry dates appear in the list again exactly as they were, because nothing was ever removed.

    That doesn’t make it acceptable. A fix is written and will ship in an upcoming update of Advanced Coupons for WooCommerce Free.

    On the code snippet you were given, that was meant as an interim workaround so you weren’t stuck while the fix was being written, not as something you should have to keep in your theme. You were right to decline it, and the update is the actual answer.

    The refund has been processed in full.

    On the process around it, removing the plugin is a published condition in our refund terms rather than something we asked for on the spot, and the screenshot was only how we confirmed it. It wasn’t there to delay anyone or to create grounds to refuse, and the refund followed once we had it. We also didn’t disable an account or reset a password. If there was a login problem on our site around that time I would genuinely like to know, because nothing like that is part of how a refund is handled here. I’ve followed the rest up privately, since billing specifics aren’t something to work through on a public forum.

    The thing we’re changing: forum reports like the March one get raised with our developers even when support can’t reproduce them. That’s what failed here.

    I’m sorry for the experience. Thank you for reporting it anyway. A lot of stores are running with this problem without realising, and it gets fixed because you flagged it.

Viewing 1 replies (of 1 total)

You must be logged in to reply to this review.