I’ve spoken with the developer of The Newsletter plugin and he’s said that they’d like to work with you to resolve this issue. There was also a similar issue a few months ago that they resolved.
https://www.thenewsletterplugin.com/newsletter-amazon-ses-addon-and-backwpup-plugin-conflict-resolved
Hi,
This is actually more of an issue that I thought. BackWPUp is also causing a conflict with email sending in general, I think it’s something to do with the scheduling system in WordPress but I could very well be wrong. Basically BackWPUp now only break The Newsletter plugin but it also breaks Contact Form 7.
Hi @davehealey
Sorry, but I personally running BackWPUp and Contact Form 7(both the latest version) is about more than 10 sites without any problem.
About the Newsletter plugin, maybe the issue comes from NEWSLETTER’s AMAZON SES addon because of library conflict( this is a premium addon so I can’t have to test yet but will ask our devs for solution ), so I really want to know how you got the issue? any step to reproduce it?
Thank you!
Thanks for getting back to me. To reproduce the newsletter plugin I just activate backwpup and try to send a test email or verify my SES email address through the newsletter plugin’s interface.
This is what the Newsletter plugin dev said to me
Our plugin detects if someone already loaded the amazon library, but probably they [backwpup] decided, to avoid the conflict, to load the library only partially,
if possible forward the problem even to them and say that we’re open to find out together a solution.
I have two sites with backwpup and the newsletter plugin and both have the same issue. They both have the contact form issue too. For example – https://xtant-audio.com/contact/
Hello,
No that didn’t fix the issue unfortunately.
I’ve uploaded a video so you can see the problem is there when the plugin is active, and gone when the plugin is deactivated.
https://youtu.be/A7u23KIXpiE
I also rolled back the plugin to version 3.6.10 and the issue is gone. So this was caused by something you did with the 3.7 update.
This issue is still present in the latest update…
Please try it with the latest version.
Why has the topic been marked as resolved? The latest version 3.8.0 hasn’t fixed the problem as I said 2 months ago.
