Plugin Support
Saransh
(@saranshwpm)
Hi @bmaberry,
Thank you for reporting this.
At the moment, I haven’t seen other reports of a critical error with Imagify 2.2.8, and I haven’t been able to reproduce the issue on my side either.
Could you please share the actual fatal error details from:
- the WordPress recovery mode email,
- your PHP error logs,
- or your hosting error logs?
The exact error message, file path, and stack trace will help identify what is failing.
Since a fresh reinstall produces the same result, the error details will be the most useful next step for troubleshooting.
Best Regards,
I’ve verified this is the issue… some kind of conflict between Imagify and Imsanity. I was able to deactivate Imsanity and activate Imagify without any issue.
https://wordpress.org/support/topic/fatal-error-with-2-9-1-update/
Here’s my error log:
[05-Jun-2026 14:22:38 UTC] PHP Fatal error: Uncaught Error: Undefined constant “IMSANITY_DEFAULT_MAX_WIDTH” in /domain.com/public_html/wp-content/plugins/imsanity/settings.php:686
Stack trace: 0 /domain.com/public_html/wp-includes/class-wp-hook.php(343): imsanity_adjust_default_threshold() 1 /domain.com/public_html/wp-includes/plugin.php(205): WP_Hook->apply_filters() 2 /domain.com/public_html/wp-content/plugins/imagify/inc/classes/class-imagify-options.php(87): apply_filters() 3 /domain.com/public_html/wp-content/plugins/imagify/classes/Traits/InstanceGetterTrait.php(36): Imagify_Options->__construct() 4 /domain.com/public_html/wp-content/plugins/imagify/classes/Plugin.php(108): Imagify_Options::get_instance() 5 /domain.com/public_html/wp-content/plugins/imagify/inc/main.php(33): Imagify\Plugin->init() 6 /domain.com/public_html/wp-includes/class-wp-hook.php(341): imagify_init() 7 /domain.com/public_html/wp-includes/class-wp-hook.php(365): WP_Hook->apply_filters() 8 /domain.com/public_html/wp-includes/plugin.php(522): WP_Hook->do_action() 9 /domain.com/public_html/wp-settings.php(622): do_action() 10 /domain.com/public_html/wp-config.php(100): require_once(‘/home/u20446580…’) 11 /domain.com/public_html/wp-load.php(50): require_once(‘/home/u20446580…’) 12 /domain.com/public_html/wp-blog-header.php(13): require_once(‘/home/u20446580…’) 13 /domain.com/public_html/index.php(17): require(‘/home/u20446580…’) 14 {main}
thrown in /domain.com/public_html/wp-content/plugins/imsanity/settings.php on line 686
We’ve identified the source of the issue in Imsanity and will push out an Imsanity bugfix release early next week. Fix currently available at https://github.com/nosilver4u/imsanity/
