Title: TENdlee's Replies | WordPress.org

---

# TENdlee

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

 *   [Profile](https://wordpress.org/support/users/tendlee/)
 *   [Topics Started](https://wordpress.org/support/users/tendlee/topics/)
 *   [Replies Created](https://wordpress.org/support/users/tendlee/replies/)
 *   [Reviews Written](https://wordpress.org/support/users/tendlee/reviews/)
 *   [Topics Replied To](https://wordpress.org/support/users/tendlee/replied-to/)
 *   [Engagements](https://wordpress.org/support/users/tendlee/engagements/)
 *   [Favorites](https://wordpress.org/support/users/tendlee/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: [[Memcached Object Cache] wp_cache_get() not supporting 4th parameter $found](https://wordpress.org/support/topic/wp_cache_get-not-supporting-4th-parameter-found/)
 *  [TENdlee](https://wordpress.org/support/users/tendlee/)
 * (@tendlee)
 * [10 years, 7 months ago](https://wordpress.org/support/topic/wp_cache_get-not-supporting-4th-parameter-found/#post-6174013)
 * Our team just discovered this issue too, specifically when using the advanced-
   custom-fields plugin.
 * `$found` is used when there is a possibility that your cache object stores boolean
   values, particularly `false`. If a cache hit from `wp_cache_get()` actually returns
   a value of `false` then you cannot reliably determine a cache hit/miss this way.`
   wp_cache_get()` would return `false` for both a cache hit and miss in this situation.
 * Instead of checking the value of `wp_cache_get()` to determine cache hit/miss,
   you can pass `$found` by reference to determine success. `$found` will return
   true/false for cache hit/miss I believe.
 * I haven’t tested this yet but this fork looks promising: [https://github.com/voceconnect/memcached](https://github.com/voceconnect/memcached).
   It appears to address the issue.

Viewing 1 replies (of 1 total)