• Resolved jamestd01

    (@jamestd01)


    We are using this plugin to cache our api requests but are finding that the cached queries show in the dashboard as being expired. This is despite the record in the database having the correct expiration date, being 1 year in the future.

    Our setup is also using redis for caching and think that we have isolated this as the cause of the issue. Disabling redis we get our api queries being served via the cache and the dashboard shows the correct expiration but without it it’s broken.

    Does anyone have any experience using redis with this plugin? Any help would be great!

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author Richard Korthuis

    (@rockfire)

    Hi @jamestd01

    Thank you for using our plugin!

    I am sorry to hear you are having issues with using our plugin in combination with Redis. To be able to investigate this, can you tell me which plugin you use to enable Redis in WordPress?

    Thread Starter jamestd01

    (@jamestd01)

    Hi @rockfire

    Thanks kindly for your response, we managed to resolve this issue eventually and it turned out to be caused by the WP REST API plugin being enabled in our project. After disabling that plugin we stopped seeing the cache entries expiring immediately while still being able to use the redis plugin. I imagine this was caused by that legacy plugin working somehow differently to how the WP core REST API does now?

    For anyone who experiences a similar issue the redis plugin we use was this one.

    Plugin Author Richard Korthuis

    (@rockfire)

    Hi @jamestd01

    It could very well be the case that the legacy plugin works differently to how the WP core REST APPI does now. That plugin was last updated 4 years ago. In the meantime a lot of extra development has been done on the REST API in core.

    Glad to hear your issue is solved!

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Cache key immediate expiration – redis conflict?’ is closed to new replies.