WPIntell

Source evidence

Fatal error: Uncaught TypeError

Email Encoder – Protect Email Addresses and Phone Numbers · support · 2026-02-02T19:38:00+00:00

complaintsentiment
highseverity
0.72relevance
1replies
Evidence linked to opportunitycommercial context

Proof Health

Open evidence

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

4 / 28 rows with source links

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

0 build-decision rows missing links

0 rows here require auditable proof before promotion.

24 rows with no attached evidence

0 rows have source counts but still need direct links.

Conversation

support
asaconover resolved
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 to see the link] Hi @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 If this works as expected, we’ll proceed with preparing the official update after completing a few additional checks.

Comments

1 shown
Ivan 2026-02-03T01:23:00+00:00

Hi @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 If this works as expected, we’ll proceed with preparing the official update after completing a few additional checks.