Can you share more details about the exact issue you’re facing?
here is the object cache document i have now
https://file.io/D3kDGSAzLs6e
Aha, it looks like you have the LiteSpeed object cache plugin installed.
Can you disable the Redis cache in LiteSpeed and then try to enable Redis Object Cache again via Settings > Redis?
i progressed a bit,
if i disabled litespeed object caceh, deleted object-cache
your plugin shows connected
but if enabled litespeed cache object cache
then i get again Drop-in is invalid
We’ll look into this! Stay tuned.
We will improve this in a future version. In the meantime, go to Settings > Litespeed > Object Cache and set Object Cache to OFF.
and if i do on litespeed object cache = off
will my wordpress still work on redis?
After you disable it in LiteSpeed, you can re-enable Redis in Redis Object Cache under Settings > Redis.
but the question is if litespeed will recognize that redis is enabled, that is what i fear.
how fast can you fix the plugin to support litespeed being redis enabled as well?
Why does LiteSpeed need to know that Redis is enabled via Redis Object Cache?
So this is a ‘new’ behavior and I blame LSCache. New being, not sure when it came into being.
We noticed it on a testing server here. It did not appear in pre-production or in production because those environments have locked down file permissions, and LSCache couldn’t meddle with the Redis Object Cache file (wp-content/object-cache.php).
@saveatrain as mentioned by the author, I stick to Redis Object Cache and disable object cache in LSCache.
I actually included a fix for this in 2.4.2 that prevents from overwriting the drop-in.
thanks, so now i can enable redis on litespeed + your plugin will work without a problem?
