Hey @jogurtt ,
That error will happen when you click the Send Test button from the settings page. It intentionally triggers a fatal error so that you can make sure the email notifications are working.
If the error happens when you activate the plugin, it could be something at your host preemptively checking to see if the plugin *could* cause an error. Since the test is designed to trigger an error, I’m not sure how we can get around that, but maybe we can come up with something. Who are you using for web hosting?
Thanks
Jack
Hey @verygoodplugins
Thanks for the reply! You’re right- the error was triggered when I manually tried to send an email notification. I mistakenly assumed that since the email didn’t arrive, the error was the cause. I’ll keep digging. Appreciate the quick response!
Glad to hear it 🙂
If you’re using a third-party SMTP service, it’s possible it hasn’t fully loaded or initialized by the time the error is triggered. Our next update will fall back to the server’s mail() function in cases where a plugin (like FluentSMTP) isn’t available.
If you are using a service like that you could check the logs to see if it *tried* to send. WP Mail Logging is also helpful with this: https://wordpress.org/plugins/wp-mail-logging/
Finally, because the notification emails contain debugging code, they often go to spam, so make sure you check there 🙂
