denniskamprad
Forum Replies Created
-
Just following up as we found the conflict: There’s a plugin that we use for our WooCommerce shop called Kadence Shop Kit and this has an option to control variations. As soon as we disabled the variation control option there, the original error went away. I’m not sure if that information is helpful for you but I thought to share it anyway, just in case (especially as Kadence is quite popular) ??
Thanks for double-checking this, Jonas! That’s already a great starting point to investigate further from out side!
And the page just moved to https://impactful.ninja/donation/ as we are trying a workaround for the other previously shared link (where we disabled the form and redirected the initial entry to our checkout page – not really ideal but better than nothing) ??
Just to follow up, this is how the first two steps are currently shown at once: https://ibb.co/927FmHF
Hello again @dbisupport,
I’ve finally gone ahead and disabled the above plugins one-by-one and it indeed looks like WishList Member X caused the problem (not ideal since this is our membership solution).
When this plugin is deactivated, Offload SES sends out all emails but when it’s activated again, Offload SES doesn’t send out emails anymore.
Btw, I’ve noticed that the previous solution, Post SMTP, as well as another trouble-shooting solution, Fluent SMTP, did send out emails just fine even with WishList Member X activated. Just thinking out loud, maybe there’s a way to force WP Offload SES to be the dominant wp_mail () plugin in the future ??
Either way, thanks for getting me to the bottom of it, I’ll now trouble-shoot this with the WishList devs – wish me luck there!
Best,
DennisHey @dbisupport,
Thanks so much for these instructions!
I’m using GeneratePress and deactivated plus uninstalled the only other mail/SMTP plugin that I had before: Post SMTP.
I then had my hosting provider (Cloudways) run the above commands (ok, I just shared your whole instructions) and they shared two images with me:
It seems like something still prevents WP Offload SES to override the WP Mail function…
Would the pictures above already be sufficient to point me in the right next direction here?
Thanks so much again – I really can’t wait to finally send out all my emails via your plugin!
Best,
DennisHey @dbisupport
Thanks so much for these instructions!
- I can confirm that Send Mail Using SES has been enabled in the plugin.
- I got the following debug information: “WP Offload SES #101: Mail function already overridden.”
Would there be an easy fix for #2?
Some additional information on what I tried in the meanwhile:
- I deactivated and then uninstalled the Post SMTP plugin, but that didn’t solve the issue
- I then uninstalled and reinstalled the WP Offload SES plugin again, but that didn’t solve the issue either
Could I force enable the WP Offload SES plugin to be overwrite the Mail Function? Or would there be anything specific that you’d recommend me to do to achieve that? (Please also feel free to share some documentation that I could then share my my developer. He’s not an email expert but he might be able to solve that.)
On a side note: as enabling Send Email Using SES stands for “Route all outgoing emails through SES.” shouldn’t that automatically overwrite the Mail Function? (Just thinking out loud ow I’d interpretate these words as someone without any dev experience)
Either way, thanks so much already! Now, at least it feels like there is a specific problem to tackle ??
Best,
DennisHey Jonas,
I freshly downloaded and installed all of these a few days ago – it’s Woo Subscriptions 5.7.0 and WooCommerce 8.3.1. I tried understanding from my dev what the conflicting issue with the subscription plugin was but I have no idea in the end. I’m just happy that he fixed it.
I’m super happy to hear that the fee recovery mode will also work in compatibility mode in the future! Cause once I start selling other products (in a few weeks), I’ll have to use the compatibility mode. And for reference, about 1/3 of our donors are currently supporting us with fee recovery.
Btw, you should totally add a live version of your plugin to your website, where we could support your work and also can experience the full user journey till the end ??
Thanks so much again for your great work!
Best,
Dennis- This reply was modified 11 months, 3 weeks ago by denniskamprad.
Just to update this thread: My dev was in the end able to fix it. Apparently, there was a plugin conflict with the official Woo Subscriptions plugin that caused the issue with the “Next” button not working and that neither Credit Card nor PayPal payments worked.
However, is there a way to still keep the “cover transaction fee” working even in “compatibility mode”? (I deactivated this one now to keep the “cover transaction fee” option as we don’t sell anything else yet)
Other than that – great work, great plugin!
Ok, I just recreated the second error with a new donation form that doesn’t have any subscription options.
- I could now at least make it work beyond the first step
- The “cover transaction fee” option didn’t show even though it is activated in the donation plugin (note that this one returned once I disable the “compatibility mode” to run the donation platform and webshop simultaneously)
- The payment options don’t seem to work either: I can’t add any information when selecting credit card (via Stripe) and am getting the following error message when selecting PayPal “Could not retrieve order. Maybe it was already completed or this browser is not supported. Please check your email or try again with a different browser.” (both PayPal and Stripe show up and work fine when I open the same test donation as a normal product: https://impactful.ninja/product/test-donation/)
Here’s a direct link to a quick test page where I embedded the donation form without any subscription option to recreate the above errors: https://impactful.ninja/donation-test-page/
- This reply was modified 12 months ago by denniskamprad.