Title: jamestd01's Replies | WordPress.org

---

# jamestd01

  [  ](https://wordpress.org/support/users/jamestd01/)

 *   [Profile](https://wordpress.org/support/users/jamestd01/)
 *   [Topics Started](https://wordpress.org/support/users/jamestd01/topics/)
 *   [Replies Created](https://wordpress.org/support/users/jamestd01/replies/)
 *   [Reviews Written](https://wordpress.org/support/users/jamestd01/reviews/)
 *   [Topics Replied To](https://wordpress.org/support/users/jamestd01/replied-to/)
 *   [Engagements](https://wordpress.org/support/users/jamestd01/engagements/)
 *   [Favorites](https://wordpress.org/support/users/jamestd01/favorites/)

 Search replies:

## Forum Replies Created

Viewing 1 replies (of 1 total)

 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[WP REST Cache] Cache key immediate expiration – redis conflict?](https://wordpress.org/support/topic/cache-key-immediate-expiration-redis-conflict/)
 *  Thread Starter [jamestd01](https://wordpress.org/support/users/jamestd01/)
 * (@jamestd01)
 * [5 years, 4 months ago](https://wordpress.org/support/topic/cache-key-immediate-expiration-redis-conflict/#post-13961245)
 * Hi [@rockfire](https://wordpress.org/support/users/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](https://wordpress.org/plugins/rest-api/)
   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](https://wordpress.org/plugins/wp-redis/).

Viewing 1 replies (of 1 total)