Sorry for your inconvenience. Your order is active now, also it is now fixed permanently :).
The add-on has been published:
Please update to v3.2.91, if that doesn’t resolve your issue, please give me temporary wp-admin login info in a private reply.
Hi,
you can’t download the package as the package is not published yet, it is scheduled to publish on 26 dec 2024 05:07. So, it will be downloadable from that date.
Hi,
you can’t download the package as the package is not published yet, it is scheduled to publish on 26 dec 2024 05:07. So, it will be downloadable from that date.
You’re welcome :). If you get some free moments, please give us a 5* here https://wordpress.org/support/plugin/download-manager/reviews/?rate=5#new-post, it will inspire us a lot.
Yes :).
Should be checkout.session.completed and charge.succeeded. However, no need to create webhook link manually, the add-on will handle it automatically.
Stripe is working fine now, the issue was, probably you registered the webhook endpoint with wrong events.
Checking.
Hi,
You need to contact ‘WP Hide & Security Enhancer’ plugin support. As we didn’t change anything there in last few updates.
Okay, got it, we are adding a cancel button with each active subscription, next update is coming soon.
I think, it will not happen again as there is no issue with code and also working good as per my test.
Yes, he consulted with me, initially we thought there could be an issue, then we went through codebase and made some test, got everything working fine.
I couldn’t able to regenerate any such issue. However, if anyone close the browser tab before complete the subscription process, it could happen.
Hi,
I’ve tested canceling subscription from admin, it is working fine for me. Tested with both paypal and stripe.
Hi,
I’m checking this right now.
Sorry for your inconvenience. Please update to v6.5.3, we have fixed the issue there :).
Yes :).
From the next update we are adding a delete all button there.
okay, not worry, as I said, we also added a condition on our side to bypass the situation.
Thanks, it has been fixed with v3.2.87