Title: Fatal error: Uncaught TypeError
Last modified: February 2, 2026

---

# Fatal error: Uncaught TypeError

 *  Resolved [asaconover](https://wordpress.org/support/users/asaconover/)
 * (@asaconover)
 * [4 months ago](https://wordpress.org/support/topic/fatal-error-uncaught-typeerror-42/)
 * Hello! I just tried updating from version 2.2.4 (running on the live site) to
   version 2.4.2 on our Dev site. The Dev site now fails to launch and shows the
   following error. Do you know how we might fix this?
 * Fatal error: Uncaught TypeError: OnlineOptimisation\EmailEncoderBundle\Front\
   FrontCore::isPostExcluded(): Return value must be of type bool, array returned
   in /code/wp-content/plugins/email-encoder-bundle/src/Traits/PluginHelper.php:
   120 Stack trace: #0 /code/wp-content/plugins/email-encoder-bundle/src/Front/FrontCore.
   php(58): OnlineOptimisation\EmailEncoderBundle\Front\FrontCore->isPostExcluded()#
   1 /code/wp-includes/class-wp-hook.php(341): OnlineOptimisation\EmailEncoderBundle\
   Front\FrontCore->register_hooks() #2 /code/wp-includes/class-wp-hook.php(365):
   WP_Hook->apply_filters() #3 /code/wp-includes/plugin.php(570): WP_Hook->do_action()#
   4 /code/wp-includes/class-wp.php(838): do_action_ref_array() #5 /code/wp-includes/
   functions.php(1343): WP->main() #6 /code/wp-blog-header.php(16): wp() #7 /code/
   index.php(17): require(‘…’) #8 {main} thrown in /code/wp-content/plugins/email-
   encoder-bundle/src/Traits/PluginHelper.php on line 120
 * There has been a critical error on this website.
 * The page I need help with: _[[log in](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fwordpress.org%2Fsupport%2Ftopic%2Ffatal-error-uncaught-typeerror-42%2F%3Foutput_format%3Dmd&locale=en_US)
   to see the link]_

Viewing 1 replies (of 1 total)

 *  Plugin Author [Ivan](https://wordpress.org/support/users/ooivan/)
 * (@ooivan)
 * [4 months ago](https://wordpress.org/support/topic/fatal-error-uncaught-typeerror-42/#post-18807352)
 * Hi [@asaconover](https://wordpress.org/support/users/asaconover/)
 * Thank you for bringing this to our attention.
 * We’ve been doing internal work to improve the codebase and strengthen validation
   and type handling, and a release candidate is now available that should address
   the issue you reported.
 * It’s great that you’re testing this on a development environment first 🙂 Could
   you please visit the following link, download `email-encoder-bundle-2.4.3-rc1.
   zip`, and install it manually to verify whether the issue is resolved?
 * [https://github.com/Online-Optimisation/email-encoder-bundle/releases/tag/v2.4.3](https://github.com/Online-Optimisation/email-encoder-bundle/releases/tag/v2.4.3)
 * If this works as expected, we’ll proceed with preparing the official update after
   completing a few additional checks.

Viewing 1 replies (of 1 total)

You must be [logged in](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fwordpress.org%2Fsupport%2Ftopic%2Ffatal-error-uncaught-typeerror-42%2F%3Foutput_format%3Dmd&locale=en_US)
to reply to this topic.

 * ![](https://ps.w.org/email-encoder-bundle/assets/icon-256x256.png?rev=2056506)
 * [Email Encoder - Protect Email Addresses and Phone Numbers](https://wordpress.org/plugins/email-encoder-bundle/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/email-encoder-bundle/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/email-encoder-bundle/)
 * [Active Topics](https://wordpress.org/support/plugin/email-encoder-bundle/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/email-encoder-bundle/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/email-encoder-bundle/reviews/)

 * 1 reply
 * 2 participants
 * Last reply from: [Ivan](https://wordpress.org/support/users/ooivan/)
 * Last activity: [4 months ago](https://wordpress.org/support/topic/fatal-error-uncaught-typeerror-42/#post-18807352)
 * Status: resolved