Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Contributor Marko Vasiljevic

    (@vmarko)

    Hello @sarahsas

    Thank you for reaching out and I am happy to help!
    It seems like there is a problem at some point with W3TC connecting with Redis. Have you tried restarting the Redis instance?

    You can also try using redis-cli and flush Redis:

    • FLUSHDB – Deletes all keys from the connection’s current database.
    • FLUSHALL – Deletes all keys from all databases on current host.

    Let me know if this helps!

    Thread Starter sarahsas

    (@sarahsas)

    Thanks @vmarko I’m concerned that won’t be a long term solution, as I have direct access to the hosting but the client does not, so if this flushing needs to happen every time, that won’t be feasible. Is connecting with Redis a requirement of your caching plugin?

    Plugin Contributor Marko Vasiljevic

    (@vmarko)

    Hey @sarahsas

    Sorry for the late reply.
    W3TC does not need to connect with Redis unless the Redis is selected as a caching method for any of the W3TC features like Object Caching.
    This being said, the problem may be that for some reason Redis needs to be restarted. or Flushed.

    Thanks!

    Thread Starter sarahsas

    (@sarahsas)

    @vmarko I have installed and configured an alternative caching plugin and the issue seems to be resolved. Thanks anyway!

Viewing 4 replies - 1 through 4 (of 4 total)

The topic ‘Conflict with security plugin?’ is closed to new replies.