Closed yangm97 closed 1 year ago
Confirming, is the fatal error before the stack trace PHP Fatal error: Uncaught Error: Call to a member function get() on null in /app/wp-content/plugins/wp-redis/object-cache.php:139
, or a different fatal error? This seems related, if not the same as #410.
After removing esc_html
from the exception handler I could see I got an authentication error because the password was blank (just like #359 but I'm using PHP 7.4.12 instead), so I worked around the issue by changing the redis configuration to require a password.
This is fixed in 1.4.2, now live on .org
Not sure which wordpress version introduced this behavior but I'm using wordpress 6.2 and
esc_html()
callswp_check_invalid_utf8()
which callsget_option()
that ends up making awp_cache_get()
call.Not only does this bring the whole site down but it also ends up obfuscating whatever the real issue is.
You should be able to reproduce this with bad redis credentials/server down/whatever.