Title: fatal error
Last modified: July 3, 2024

---

# fatal error

 *  Resolved [blcsue](https://wordpress.org/support/users/blcsue/)
 * (@blcsue)
 * [1 year, 10 months ago](https://wordpress.org/support/topic/fatal-error-4709/)
 * I updated the latest version today 4.54.0 (**MailPoet and ****MailPoet Premium**).
   It crashed my website and I got the “white screen of death”. Disabled all plugins,
   and one by one reactivated them but when I try and activate the Mailpoet plugins
   I get the following message:
 * Plugin could not be activated because it triggered a **fatal error**.
 * Please help. Thanks
 * The page I need help with: _[[log in](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fwordpress.org%2Fsupport%2Ftopic%2Ffatal-error-4709%2F%3Foutput_format%3Dmd&locale=en_US)
   to see the link]_

Viewing 15 replies - 1 through 15 (of 28 total)

1 [2](https://wordpress.org/support/topic/fatal-error-4709/page/2/?output_format=md)
[→](https://wordpress.org/support/topic/fatal-error-4709/page/2/?output_format=md)

 *  Plugin Support [Ojoma a11n](https://wordpress.org/support/users/geraltrivia/)
 * (@geraltrivia)
 * [1 year, 10 months ago](https://wordpress.org/support/topic/fatal-error-4709/#post-17880188)
 * Hello there [@blcsue](https://wordpress.org/support/users/blcsue/) ,
 * Thank you for reaching out to us.
 * Fatal errors are most often caused by either missing or corrupted files, which
   can happen if there’s some type of glitch while updating WordPress plugins/themes
   and something doesn’t go as expected.
 * As a first step here, I’d recommend re-installing the plugin and then checking
   to see if the issue is resolved. You can remove the plugin and re-install it 
   from your admin dashboard’s Plugins page, or alternatively we have a guide for
   re-installing via FTP here:
 * [Re-installing / Updating the Plugin via FTP](https://kb.mailpoet.com/article/258-re-installing-updating-the-plugin-via-ftp)
 * Please let me know how that goes, or if you have any questions!
 *  Thread Starter [blcsue](https://wordpress.org/support/users/blcsue/)
 * (@blcsue)
 * [1 year, 10 months ago](https://wordpress.org/support/topic/fatal-error-4709/#post-17880651)
 * Thank you for your reply. I did as you suggested; I deleted the current Mailpoet
   plugin, re-installed new version and tried to activate plugin, again fatal error.
 * So I then de-activated all my plugins to see if there was conflict with another
   plugin. I get the same result fatal error
 *  Thread Starter [blcsue](https://wordpress.org/support/users/blcsue/)
 * (@blcsue)
 * [1 year, 10 months ago](https://wordpress.org/support/topic/fatal-error-4709/#post-17881457)
 * I checked the error logs and found this:
 * thrown in /home/kzjmmwgc/public_html/wp-content/plugins/hello.php on line 60
   [
   30-May-2018 09:20:18 UTC] PHP Fatal error: Uncaught Error: Call to undefined 
   function add_action() in /home/kzjmmwgc/public_html/wp-content/plugins/hello.
   php:60
 *  Plugin Support [Ojoma a11n](https://wordpress.org/support/users/geraltrivia/)
 * (@geraltrivia)
 * [1 year, 9 months ago](https://wordpress.org/support/topic/fatal-error-4709/#post-17898128)
 * Hello again [@blcsue](https://wordpress.org/support/users/blcsue/) ,
 * Based on the error log you’ve provided, the issue seems to be arising from a 
   file named `hello.php` rather than directly from the MailPoet plugin. The specific
   error message points out an “Uncaught Error: Call to undefined function add_action()”
   on line 60 of `hello.php`. The `add_action()` function is a core WordPress function,
   which means this error typically occurs when a WordPress environment is not correctly
   initialized before a plugin calls its functions, or there’s a significant conflict
   affecting WordPress’s core functionality.
 * However, if this error is occurring immediately upon activating MailPoet, it 
   could indicate a potential conflict between MailPoet and another plugin or theme
   that uses the `hello.php` file, or an issue with the WordPress environment itself.
 * To troubleshoot this issue, consider the following steps:
    1. **Deactivate Other Plugins**: Temporarily deactivate all other plugins except
       for MailPoet. If the error goes away, reactivate each plugin one by one until
       the error reappears. This process will help identify the conflicting plugin.
    2. **Switch Themes**: Try switching to a default WordPress theme (like Twenty Twenty-
       One) to rule out any theme conflicts.
    3. **Check the Hello Plugin**: The file path suggests that the error might originate
       from a plugin or a custom script named `hello`. If this isn’t a plugin that 
       you intentionally use, consider removing or deactivating it to see if that resolves
       the issue.
    4. **Update WordPress and Plugins**: Ensure that WordPress, MailPoet, and all other
       plugins are up to date. Compatibility issues can sometimes arise from outdated
       software.
    5. **Reach out to your host:** Try sharing the error log with your website host,
       they might be able to help you find out the plugin responsible for this fatal
       error.
 * Remember, it’s crucial to back up your website before making changes like deactivating
   plugins or switching themes to avoid accidental data loss.
 * I hope this helps.
 *  Thread Starter [blcsue](https://wordpress.org/support/users/blcsue/)
 * (@blcsue)
 * [1 year, 9 months ago](https://wordpress.org/support/topic/fatal-error-4709/#post-17903746)
 * Thank you for your reply. I contacted the server provider for the error message:_/
   home/kzjmmwgc/public\_html/wp-content/plugins/hello.php on line 60
   [30-May-2018
   09:20:18 UTC] PHP Fatal error: Uncaught Error: Call to undefined function add\
   _action() in /home/kzjmmwgc/public\_html/wp-content/plugins/hello.php:60
   . This
   refers to an error from 2018 and has no bearing in the present.
 * Also, did as you suggested. I disabled all plugins and changed my theme and when
   I re-activate Mailpoet I get the same error message on both as before.
 *  Plugin Support [Ojoma a11n](https://wordpress.org/support/users/geraltrivia/)
 * (@geraltrivia)
 * [1 year, 9 months ago](https://wordpress.org/support/topic/fatal-error-4709/#post-17918821)
 * Hello again,
 * Thank you for getting back to us.
 * > Also, did as you suggested. I disabled all plugins and changed my theme and
   > when I re-activate Mailpoet I get the same error message on both as before.
 * Do you mean when you deactivated all your plugins, changed to a default theme
   and when you reactivated MailPoet you got the same error?
 * You mentioned you started experiencing this error when you upgraded to MailPoet
   version 4.54.0. In the mean time can you rollback to a previous version of MailPoet
   that worked for you while we keep investigating this?
 * You can roll back the free MailPoet version by:
 * – using the WP Rollback plugin ([https://wordpress.org/plugins/wp-rollback/](https://wordpress.org/plugins/wp-rollback/));
 * or
 * – downloading the previous version here: [https://wordpress.org/plugins/mailpoet/advanced/](https://wordpress.org/plugins/mailpoet/advanced/)(
   scroll down to ADVANCED OPTIONS section) and installing it via FTP: [https://kb.mailpoet.com/article/258-re-installing-updating-the-plugin-via-ftp](https://kb.mailpoet.com/article/258-re-installing-updating-the-plugin-via-ftp).
 * Looking forward to hearing back from you.
 *  Thread Starter [blcsue](https://wordpress.org/support/users/blcsue/)
 * (@blcsue)
 * [1 year, 9 months ago](https://wordpress.org/support/topic/fatal-error-4709/#post-17921466)
 * Yes. I deactivated all my plugins, changed to a default theme and still got the
   same error message.
 * I have now installed version 4.53.0 and it works. Version 4.54.0 was when I started
   experiencing errors.
 * Thank you for your time on this
 *  Plugin Support [Gui A. a11n](https://wordpress.org/support/users/guicmazeredo/)
 * (@guicmazeredo)
 * [1 year, 9 months ago](https://wordpress.org/support/topic/fatal-error-4709/#post-17930268)
 * Have there,
 * As we are on the 4.58.0, can you try to update to this very latest version and
   see if you are still going to experience the issue?
 * You may want to do that on a stating site to avoid affecting your live site. 
   In case your host doesn’t offer this facility, you can create a copy of your 
   website with this plugin: [WP Staging](https://wordpress.org/plugins/wp-staging/)
 *  Thread Starter [blcsue](https://wordpress.org/support/users/blcsue/)
 * (@blcsue)
 * [1 year, 9 months ago](https://wordpress.org/support/topic/fatal-error-4709/#post-17931130)
 * I am still experiencing the same problem. I rolled back to 4.53 version
 *  Plugin Support [Thu P. a11n](https://wordpress.org/support/users/thup90/)
 * (@thup90)
 * [1 year, 9 months ago](https://wordpress.org/support/topic/fatal-error-4709/#post-17933526)
 * Hi there,
 * Can you try removing the hello.php plugin completely? If you can’t do this from
   the frontend, please delete it from the _/wp-content/plugins/_ directory via 
   the FTP connection.
 *  Thread Starter [blcsue](https://wordpress.org/support/users/blcsue/)
 * (@blcsue)
 * [1 year, 9 months ago](https://wordpress.org/support/topic/fatal-error-4709/#post-17936144)
 * Hi
 * I have deleted the hello.php plugin completely. I still got the error message“
   fatal error”.
 * I have re-installed version 4.53.
 *  Plugin Author [Ján Mikláš](https://wordpress.org/support/users/neosinner/)
 * (@neosinner)
 * [1 year, 9 months ago](https://wordpress.org/support/topic/fatal-error-4709/#post-17936668)
 * Hi [@blcsue](https://wordpress.org/support/users/blcsue/), could you please share
   the specific error message you get from the error logs? Without it, we can’t 
   provide guidance on how to fix it, as we don’t know what’s the issue.
 * Thanks
 *  Thread Starter [blcsue](https://wordpress.org/support/users/blcsue/)
 * (@blcsue)
 * [1 year, 9 months ago](https://wordpress.org/support/topic/fatal-error-4709/#post-17938950)
 * I get the “white screen of death” with a message:
 * “There has been a critical error on this website. Please check your site admin
   email inbox for instructions”
 * No email was received
 *  Plugin Support [Kel C. a11n](https://wordpress.org/support/users/kellymetal/)
 * (@kellymetal)
 * [1 year, 9 months ago](https://wordpress.org/support/topic/fatal-error-4709/#post-17940391)
 * Hi there [@blcsue](https://wordpress.org/support/users/blcsue/),
 * Thank you, however the “There has been a critical error” message is a super general
   message so doesn’t clarify much. We understand you did not receive an email, 
   however there should still be some detailed errors written to the server logs.
 * Please make sure you’ve enabled `WP_DEBUG` and `WP_DEBUG_LOG` as described here:
   
   [https://developer.wordpress.org/advanced-administration/debug/debug-wordpress/](https://developer.wordpress.org/advanced-administration/debug/debug-wordpress/)
   Then try activating the plugin again to generate logs. If you don’t have direct
   access to the logs, please check with your hosting, then share any error logs
   you find.
 * Thank you.
 *  Thread Starter [blcsue](https://wordpress.org/support/users/blcsue/)
 * (@blcsue)
 * [1 year, 9 months ago](https://wordpress.org/support/topic/fatal-error-4709/#post-17941276)
 * **Fatal error**: Uncaught Error: Call to undefined function MailPoet\Doctrine\
   Types\mb_convert_encoding() in /home/kzjmmwgc/public_html/wp-content/plugins/
   mailpoet/lib/Doctrine/Types/JsonType.php:42 Stack trace: #0 /home/kzjmmwgc/public_html/
   wp-content/plugins/mailpoet/vendor-prefixed/doctrine/orm/lib/Doctrine/ORM/Internal/
   Hydration/AbstractHydrator.php(206): MailPoet\Doctrine\Types\JsonType->convertToPHPValue()#
   1 /home/kzjmmwgc/public_html/wp-content/plugins/mailpoet/vendor-prefixed/doctrine/
   orm/lib/Doctrine/ORM/Internal/Hydration/ObjectHydrator.php(181): MailPoetVendor\
   Doctrine\ORM\Internal\Hydration\AbstractHydrator->gatherRowData() #2 /home/kzjmmwgc/
   public_html/wp-content/plugins/mailpoet/vendor-prefixed/doctrine/orm/lib/Doctrine/
   ORM/Internal/Hydration/ObjectHydrator.php(87): MailPoetVendor\Doctrine\ORM\Internal\
   Hydration\ObjectHydrator->hydrateRowData() #3 /home/kzjmmwgc/public_html/wp-content/
   plugins/mailpoet/vendor-prefixed/doctrine/orm/lib/Doctrine/ORM/Internal/Hydration/
   AbstractHydrator.php(121): MailPoetVendor\Doctrine\ORM\Internal\Hydration\ObjectHydrator-
   >hydrateAllData() #4 /home/kzjmmwgc/public_html/wp-content/plugins/mailpoet/vendor-
   prefixed/doctrine/orm/lib/Doctrine/ORM/Persisters/Entity/BasicEntityPersister.
   php(384): MailPoetVendor\Doctrine\ORM\Internal\Hydration\AbstractHydrator->hydrateAll()#
   5 /home/kzjmmwgc/public_html/wp-content/plugins/mailpoet/vendor-prefixed/doctrine/
   orm/lib/Doctrine/ORM/EntityRepository.php(84): MailPoetVendor\Doctrine\ORM\Persisters\
   Entity\BasicEntityPersister->load() #6 /home/kzjmmwgc/public_html/wp-content/
   plugins/mailpoet/lib/Doctrine/Repository.php(69): MailPoetVendor\Doctrine\ORM\
   EntityRepository->findOneBy() #7 /home/kzjmmwgc/public_html/wp-content/plugins/
   mailpoet/lib/Config/Populator.php(743): MailPoet\Doctrine\Repository->findOneBy()#
   8 /home/kzjmmwgc/public_html/wp-content/plugins/mailpoet/lib/Config/Populator.
   php(189): MailPoet\Config\Populator->scheduleBackfillEngagementData() #9 /home/
   kzjmmwgc/public_html/wp-content/plugins/mailpoet/lib/Config/Activator.php(80):
   MailPoet\Config\Populator->up() #10 /home/kzjmmwgc/public_html/wp-content/plugins/
   mailpoet/lib/Config/Activator.php(60): MailPoet\Config\Activator->processActivate()#
   11 /home/kzjmmwgc/public_html/wp-content/plugins/mailpoet/lib/Config/Initializer.
   php(445): MailPoet\Config\Activator->activate() #12 /home/kzjmmwgc/public_html/
   wp-includes/class-wp-hook.php(324): MailPoet\Config\Initializer->maybeRunActivator()#
   13 /home/kzjmmwgc/public_html/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters()#
   14 /home/kzjmmwgc/public_html/wp-includes/plugin.php(517): WP_Hook->do_action()#
   15 /home/kzjmmwgc/public_html/wp-settings.php(700): do_action() #16 /home/kzjmmwgc/
   public_html/wp-config.php(113): require_once(‘/home/kzjmmwgc/…’) #17 /home/kzjmmwgc/
   public_html/wp-load.php(50): require_once(‘/home/kzjmmwgc/…’) #18 /home/kzjmmwgc/
   public_html/wp-admin/admin.php(34): require_once(‘/home/kzjmmwgc/…’) #19 /home/
   kzjmmwgc/public_html/wp-admin/plugins.php(10): require_once(‘/home/kzjmmwgc/…’)#
   20 {main} thrown in **/home/kzjmmwgc/public_html/wp-content/plugins/mailpoet/
   lib/Doctrine/Types/JsonType.php** on line **42**

Viewing 15 replies - 1 through 15 (of 28 total)

1 [2](https://wordpress.org/support/topic/fatal-error-4709/page/2/?output_format=md)
[→](https://wordpress.org/support/topic/fatal-error-4709/page/2/?output_format=md)

The topic ‘fatal error’ is closed to new replies.

 * ![](https://ps.w.org/mailpoet/assets/icon-256x256.png?rev=3284564)
 * [MailPoet - Newsletters, Email Marketing, and Automation](https://wordpress.org/plugins/mailpoet/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/mailpoet/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/mailpoet/)
 * [Active Topics](https://wordpress.org/support/plugin/mailpoet/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/mailpoet/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/mailpoet/reviews/)

## Tags

 * [site crash](https://wordpress.org/support/topic-tag/site-crash/)

 * 28 replies
 * 11 participants
 * Last reply from: [blcsue](https://wordpress.org/support/users/blcsue/)
 * Last activity: [1 year, 8 months ago](https://wordpress.org/support/topic/fatal-error-4709/page/2/#post-18010136)
 * Status: resolved