• Resolved Bluemad

    (@bluemad)


    Today I have updated my WordPress sites to 5.1. When I try to enable radis cache (Today I migrated site to new VPS) through this app, now Worpress giving me following error. Once I clicked “Continue” it redirects to home page. (After that, everytime when I try to access a wp-admin area, it shows following error. Then I deleted /wp-content/object-cache.php” file, then that error gone away, again if I try to enable this plugin service it shows same error. Now I can’t enable this plugin service.

    "No Update Required"
    "Your WordPress database is already up-to-date!"

    Thank in advance.

    • This topic was modified 5 years, 9 months ago by Bluemad.
Viewing 12 replies - 1 through 12 (of 12 total)
  • Plugin Author Till Krüss

    (@tillkruess)

    You need to flush for Redid database.

    Hello

    I’m also having this issue. I tried flushing the cache directly through Redis CLI but the problem persisted.

    I can’t use the Flush DB button on Redis options, since I can’t access the admin section once I enable the Object Caching in the plugin.

    I have it disable it for now. A solution would be great, thanks in advance.

    • This reply was modified 5 years, 9 months ago by fearlex.
    Thread Starter Bluemad

    (@bluemad)

    Flush servers level Radis cache via SSH terminal. In my situation it fixed the issue.

    @bluemad

    Thanks for replying. That’s what I did, logged in via SSH, and use the CLI to flush the Object DB.

    redis-cli FLUSHALL

    Didn’t work for me. Still getting the Update Required. Your WordPress Database is Up-To-Date.

    Plugin Author Till Krüss

    (@tillkruess)

    If FLUSH ALL doesn’t work you’re either on the wrong Redis server or using a different object cache than this plugin provides.

    Trying running “wp cache flush”.

    Hi @tillkruess

    I’m on the right Redis server and using Predis 1.1.1. Been using the plugin for a while now and love it. No problems so far until WP 5.1.

    It is resolved now, I had to remove both drop-ins and then do a FLUSHALL

    It flushed the database and everything is working as expected now.

    Thanks for an amazing plugin and for the help.

    Plugin Author Till Krüss

    (@tillkruess)

    Aha, great!

    What do you mean by “both dropins”?

    So, when I reviewed the diagnostics view, it showed this:

    Status: Connected
    Client: PhpRedis (v4.1.1)
    Drop-in: Invalid
    Redis Extension: 4.1.1
    Predis Client: 1.1.1
    PHP Version: 7.2.15
    ……
    Dropins:
    – advanced-cache.php v by
    – Redis Object Cache Drop-In v1.4.1 by Till Krüss

    Notice the Drop-in says Invalid. So i removed both dropins (advanced-cache.php and object-cache.php) then tried the redis-cli FLUSHALL again through SSH.

    And it worked. It regenerated both dropins files and it shows this now:

    Status: Connected
    Client: PhpRedis (v4.1.1)
    Drop-in: Valid
    Ping: +PONG
    Redis Extension: 4.1.1
    Predis Client: 1.1.1
    PHP Version: 7.2.15
    Multisite: No
    Global Prefix: ……
    Blog Prefix: …..
    WP_CACHE_KEY_SALT: ……
    Global Groups: …….
    Dropins:
    – advanced-cache.php v by
    – Redis Object Cache Drop-In v1.4.1 by Till Krüss

    Again, thanks for an amazing plugin.

    Plugin Author Till Krüss

    (@tillkruess)

    Fantastic. Maybe you had a foreign object cache dropin and that’s why the flushing didn’t work.

    Most likely.

    Again, thanks for the help!

    Hi, happened with WP Rocket dropin but in my case everything went automatic.

    One difference, I am using PhpRedis (v4.2.0) which is compiled and much faster than Predis. If PHP configuration can be tuned up, this is a wanted module…

    I am having this problem all the time, each time WordPress updates i think.

    I have no other solution than go to my CLi and wp cache flush or flushdb on redis to have access to /wp-admin.

    Is this normal behavior since WP5?

    • This reply was modified 5 years, 7 months ago by ploopi.
Viewing 12 replies - 1 through 12 (of 12 total)
  • The topic ‘Update Required : Your WordPress database is already up-to-date!’ is closed to new replies.