• Hi,

    This admin message used to go away after simply visiting the (linked) Redis admin page, but in this latest version 1.4.1 it does not anymore.

    Diagnostics says:

    Dropins:
    – Redis Object Cache Drop-In v1.4.0 by Till Krüss

    which seems to be the previous version. I’ll update manually, just thought I should mention the difference in behavior ??

    BTW This is on a multisite, if that’s related at all.

    Anyway, thanks for sharing your fantastic plugin ??

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

    (@tillkruess)

    @ravanh: Thanks! Was there an “update dropin” button or message at least?

    No, no button to update the dropin file and only the admin message about the need to update it, not on how to do that.

    However, deactivating the redis cache and reactivating it again did update the dropin just fine. No need to do it by FTP???

    Plugin Author Till Krüss

    (@tillkruess)

    @ravanh: Ok, thanks for the report.

    Hi Till

    I get the same issue. Should I pay attention to this and how to solve it? Thank you.

    Plugin Author Till Krüss

    (@tillkruess)

    Try re-activating the plugin as @ravanh did.

    Use the button Disable Object Cache on the Redis settings page. Then enable again. This will remove the old file and then place the new version back.

    @ravanh @till Thanks so much.

    Hi,

    I just updated to 1.4.3 on wp 5.2 and now I am getting this message:

    The Redis object cache drop-in is outdated. Please update it now.

    and when I click on the link (update it now) it takes me to a page which asks for ftp credentials. I did deactivate and reactivate again, but I am still getting this message which is what I expected because my php process doesn’t have write permission on the directory containing object-cache.php file. It would have been really good if there was a way that I could just download the new version of the file from somewhere instead of having to setup special environment so that this update could take place. In this side of the century, we ship code through git and there are CI/CD pipe lines that it has to go through. I can’t believe that ftping into a server is still the default and, most of the time, the only way of updating stuff in wordpress.

    Never the less, thanks for the plugin.

    Plugin Author Till Krüss

    (@tillkruess)

    @kaveh77

    It would have been really good if there was a way that I could just download the new version of the file from somewhere instead of having to setup special environment so that this update could take place.

    You can download the file from GitHub if you like.

    I can’t believe that ftping into a server is still the default and, most of the time, the only way of updating stuff in wordpress.

    I personally run wp redis enable during the build phase. Make sure you don’t include the object-cache.php file in your version control.

    Thanks for replying.

    I do download the plugin from github ( actually composer does it for me ). I meant if I could download the new or what would be the new object-cache.php file from my own instance. For example, it would be really good if the the same page that asks me for ftp credential would have also showed me what it is that it wants to ftp to the server (content of the object-cache.php). I’ll try to add “wp redis enable” to a composer event to see how it works.

    Thanks,

    Hi again,

    Sorry, I was under the impression that the object-cache.php gets “generated”. I found it in redis-cache/includes. All good.

    Thanks,

    Plugin Author Till Krüss

    (@tillkruess)

    On Heroku I run these scripts during the build:

    {
      "scripts": {
        "compile": [
          "wp redis enable",
          "wp cache flush"
        ]
      },
    }
Viewing 12 replies - 1 through 12 (of 12 total)
  • The topic ‘The Redis object cache drop-in is outdated. Please update it now.’ is closed to new replies.