WPIntell

Source evidence

Critical error

Enhanced Autoload Manager · support · 2026-05-22T12:56:00+00:00

Enhanced Autoload Manager plugin evidence original source source API
mixedsentiment
highseverity
0.88relevance
3replies
Evidence linked to opportunitycommercial context

Proof Health

Open evidence

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

7 / 33 rows with source links

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

0 build-decision rows missing links

0 rows here require auditable proof before promotion.

26 rows with no attached evidence

0 rows have source counts but still need direct links.

Conversation

support
Bob resolved
Updated 2 (very similar) sites to WordPress 7.0. Both use EAM. One has no issues, on the other EAM stopped working (critical error). I have no idea what’s going on. WordPress version 7.0 Active theme: Hueman (version 3.7.27) Current plugin: Enhanced Autoload Manager (version 1.6.3) PHP version 8.4.19 Error Details An error of type E_ERROR was caused in line 282 of the file …/wp-content/plugins/enhanced-autoload-manager/enhanced-autoload-manager.php. Error message: Uncaught TypeError: strlen(): Argument #1 ($string) must be of type string, array given in …/wp-content/plugins/enhanced-autoload-manager/enhanced-autoload-manager.php:282 Stack trace: 0 …/wp-content/plugins/enhanced-autoload-manager/enhanced-autoload-manager.php(370): Enhanced_Autoload_Manager->get_autoload_data() 1 …/wp-includes/class-wp-hook.php(341): Enhanced_Autoload_Manager->display_page() 2 …/wp-includes/class-wp-hook.php(365): WP_Hook->apply_filters() 3 …/wp-includes/plugin.php(522): WP_Hook->do_action() 4 …/wp-admin/admin.php(264): do_action() 5 …/wp-admin/tools.php(40): require_once(‘/home/XXX…’) 6 {main} This topic was modified 1 month, 1 week ago by Bob . This topic was modified 1 month, 1 week ago by Bob . It seems this relative new plugin is already abandoned. Too bad… Hi Bob — not abandoned at all I was working on another project Visual Sentinel , and thanks for the detailed trace, it made this quick to diagnose. The crash happens when a persistent object cache returns already-unserialized (array) values for some options; the size calc then ran strlen() on an array, which is fatal on PHP 8 — that’s why one of your two otherwise-identical sites was hit and the other wasn’t. Fixed in v1.6.5 (just released): option values are now handled safely regardless of how the cache returns them. Please update and it should load normally. Tested up to WordPress 7.0 / PHP 8.4+. Apologies for the disruption. I’m glad you didn’t drop the project 🙂 One of my sites has Object cache, the other hasn’t. Maybe that’s why it went wrong here. This latest update solved that as I didn’t find any issue! Thanks.

Comments

3 shown
Bob 2026-05-29T18:21:00+00:00

It seems this relative new plugin is already abandoned. Too bad…

Rai Ansar 2026-06-29T06:35:00+00:00

Hi Bob — not abandoned at all I was working on another project Visual Sentinel , and thanks for the detailed trace, it made this quick to diagnose. The crash happens when a persistent object cache returns already-unserialized (array) values for some options; the size calc then ran strlen() on an array, which is fatal on PHP 8 — that’s why one of your two otherwise-identical sites was hit and the other wasn’t. Fixed in v1.6.5 (just released): option values are now handled safely regardless of how the cache returns them. Please update and it should load normally. Tested up to WordPress 7.0 / PHP 8.4+. Apologies for the disruption.

Bob 2026-06-30T17:54:00+00:00

I’m glad you didn’t drop the project 🙂 One of my sites has Object cache, the other hasn’t. Maybe that’s why it went wrong here. This latest update solved that as I didn’t find any issue! Thanks.