Title: PHP Fatal error Last modified: August 20, 2019 --- # PHP Fatal error * Resolved [dimal](https://wordpress.org/support/users/dimalifragis/) * (@dimalifragis) * [6 years, 9 months ago](https://wordpress.org/support/topic/php-fatal-error-183/) * Hello. * This happened AFTER i enabled the file check option and took a snapshot. * I know it also points to GD Mail Queue plugin, still everything worked fine, until i enabled that option. * [20-Aug-2019 11:59:04 UTC] PHP Fatal error: Uncaught phpmailerException: Could not access file: /home/wp-content/nfwlog/cache/nf_filecheck.txt in /home/wp- includes/class-phpmailer.php:2510 * Stack trace: #0 /home/wp-content/plugins/gd-mail-queue/core/objects/core.email. php(161): PHPMailer->addAttachment(‘/home/…’) #1 /home/wp-content/plugins/gd- mail-queue/core/mail/engine.phpmailer.php(62): gdmaq_core_email->build_phpmailer( Object(PHPMailer), true) #2 /home/wp-content/plugins/gd-mail-queue/core/objects/ core.queue.php(206): gdmaq_engine_phpmailer->queue_send(Object(gdmaq_core_email))# 3 /home/wp-content/plugins/gd-mail-queue/core/objects/core.queue.php(168): gdmaq_core_queue- >send(Object(gdmaq_core_email)) #4 /home/wp-content/plugins/gd-mail-queue/core/ objects/core.queue.php(103): gdmaq_core_queue->run_batch() #5 /home/wp-includes/ c in /home/wp-includes/class-phpmailer.php on line 2510 * Thanks Viewing 7 replies - 1 through 7 (of 7 total) * Plugin Author [nintechnet](https://wordpress.org/support/users/nintechnet/) * (@nintechnet) * [6 years, 9 months ago](https://wordpress.org/support/topic/php-fatal-error-183/#post-11850533) * `/home/wp-content/nfwlog/cache/nf_filecheck.txt` is the file attached to the email sent by File Check. It looks like your plugin was not able to find it. * Thread Starter [dimal](https://wordpress.org/support/users/dimalifragis/) * (@dimalifragis) * [6 years, 9 months ago](https://wordpress.org/support/topic/php-fatal-error-183/#post-11856890) * So what is the verdict for us the poor webmasters ? * [https://wordpress.org/support/topic/php-fatal-error-184/#post-11856884](https://wordpress.org/support/topic/php-fatal-error-184/#post-11856884) * Thread Starter [dimal](https://wordpress.org/support/users/dimalifragis/) * (@dimalifragis) * [6 years, 9 months ago](https://wordpress.org/support/topic/php-fatal-error-183/#post-11856898) * Let’s see if i can replicate this after disabling GD mail queue plugin. * I will update asap. * Thread Starter [dimal](https://wordpress.org/support/users/dimalifragis/) * (@dimalifragis) * [6 years, 9 months ago](https://wordpress.org/support/topic/php-fatal-error-183/#post-11857423) * With GD queuing plugin disabled attachments arrive and there are no errors. * Plugin Author [nintechnet](https://wordpress.org/support/users/nintechnet/) * (@nintechnet) * [6 years, 9 months ago](https://wordpress.org/support/topic/php-fatal-error-183/#post-11858089) * The attachment is a temporary file: NinjaFirewall creates it, calls the WP `wp_mail` function and when that functions returns, it deletes the temp file. If you have a plugin that delays the sending but does not manage to retrieve the attached file immediately (i.e., it thinks the file is still on disk), you’ll end up with this error. * Also, if you use another application to send NinjaFirewall’s notifications, make sure it **does NOT send them in HTML format**, but text/plain only. That would be a big security issue otherwise. * Thread Starter [dimal](https://wordpress.org/support/users/dimalifragis/) * (@dimalifragis) * [6 years, 9 months ago](https://wordpress.org/support/topic/php-fatal-error-183/#post-11858123) * Well that is exactly what GD mail queue does. Delay in a qeueu. In order not to create havoc to the hosting provider limitations for smtp. * As for HTML can you explain a bit more, because this is ALSO what GD Queue does. HTML emails. * Plugin Author [nintechnet](https://wordpress.org/support/users/nintechnet/) * (@nintechnet) * [6 years, 9 months ago](https://wordpress.org/support/topic/php-fatal-error-183/#post-11859880) * If you have any plugin that, like NinjaFirewall, is using plain text, it will write its data to the email body as “text/plain” content type. It will not sanitize it. But if you send it as HTML, you must make sure to sanitize all that content, otherwise this could lead to vulnerabilities such as HTML injection and CSRF. See this example: [https://blog.nintechnet.com/html-injection-vulnerability-in-wordpress-pirate-forms-plugin/](https://blog.nintechnet.com/html-injection-vulnerability-in-wordpress-pirate-forms-plugin/) Viewing 7 replies - 1 through 7 (of 7 total) The topic ‘PHP Fatal error’ is closed to new replies. * ![](https://ps.w.org/ninjafirewall/assets/icon-256x256.png?rev=976137) * [NinjaFirewall (WP Edition) - Advanced Security Plugin and Firewall](https://wordpress.org/plugins/ninjafirewall/) * [Frequently Asked Questions](https://wordpress.org/plugins/ninjafirewall/#faq) * [Support Threads](https://wordpress.org/support/plugin/ninjafirewall/) * [Active Topics](https://wordpress.org/support/plugin/ninjafirewall/active/) * [Unresolved Topics](https://wordpress.org/support/plugin/ninjafirewall/unresolved/) * [Reviews](https://wordpress.org/support/plugin/ninjafirewall/reviews/) * 5 replies * 2 participants * Last reply from: [nintechnet](https://wordpress.org/support/users/nintechnet/) * Last activity: [6 years, 9 months ago](https://wordpress.org/support/topic/php-fatal-error-183/#post-11859880) * Status: resolved