WPIntell

Source evidence

Plugin doesn’t work, throws error

Fatal Error Notify · review · 2025-04-15T10:31:00+00:00

praisesentiment
highseverity
0.78relevance
3replies
Evidence linked to opportunitycommercial context

Proof Health

Open evidence

Commercial opportunities need traceable source links before they are treated as build-worthy.

3 / 22 rows with source links

13.6% of this page's analysis has direct source links.

0 build-decision rows missing links

0 rows here require auditable proof before promotion.

19 rows with no attached evidence

0 rows have source counts but still need direct links.

Conversation

review · 5 stars
jogurtt unresolved
PHP Fatal error: Uncaught Error: Call to undefined function fatal_error_notify_test_error_function() in /wp-content/plugins/fatal-error-notify/includes/admin/class-admin.php:68 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 🙂

Comments

3 shown
Jack Arturo 2025-04-15T10:41:00+00:00

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

jogurtt 2025-04-15T10:56:00+00:00

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!

Jack Arturo 2025-04-15T11:05:00+00:00

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 🙂