Viewing 15 replies - 1 through 15 (of 16 total)
  • Plugin Author Till Krüss

    (@tillkruess)

    Can you share more details about the exact issue you’re facing?

    Thread Starter saveatrain

    (@saveatrain)

    this is what i see

    Thread Starter saveatrain

    (@saveatrain)

    here is the object cache document i have now

    https://file.io/D3kDGSAzLs6e

    Plugin Author Till Krüss

    (@tillkruess)

    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?

    Thread Starter saveatrain

    (@saveatrain)

    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

    Plugin Author Till Krüss

    (@tillkruess)

    We’ll look into this! Stay tuned.

    Thread Starter saveatrain

    (@saveatrain)

    hey till, any update?

    Plugin Author Till Krüss

    (@tillkruess)

    We will improve this in a future version. In the meantime, go to Settings > Litespeed > Object Cache and set Object Cache to OFF.

    Thread Starter saveatrain

    (@saveatrain)

    and if i do on litespeed object cache = off

    will my wordpress still work on redis?

    Plugin Author Till Krüss

    (@tillkruess)

    After you disable it in LiteSpeed, you can re-enable Redis in Redis Object Cache under Settings > Redis.

    Thread Starter saveatrain

    (@saveatrain)

    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?

    Plugin Author Till Krüss

    (@tillkruess)

    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.

    Plugin Author Till Krüss

    (@tillkruess)

    I actually included a fix for this in 2.4.2 that prevents from overwriting the drop-in.

    Thread Starter saveatrain

    (@saveatrain)

    thanks, so now i can enable redis on litespeed + your plugin will work without a problem?

Viewing 15 replies - 1 through 15 (of 16 total)
  • The topic ‘Drop-in is invalid’ is closed to new replies.