Redis Object Cache


A persistent object cache backend powered by Redis®¹. Supports Predis, PhpRedis (PECL), Relay, replication, sentinels, clustering and WP-CLI.

To adjust the connection parameters, prefix cache keys or configure replication/clustering, see the configuration options.

Object Cache Pro

A business class Redis®¹ object cache backend. Truly reliable, highly optimized, fully customizable and with a dedicated engineer when you most need it.

  • Rewritten for raw performance
  • 100% WordPress API compliant
  • Faster serialization and compression
  • Easy debugging & logging
  • Cache prefetching and analytics
  • Fully unit tested (100% code coverage)
  • Secure connections with TLS
  • Health checks via WordPress & WP CLI
  • Optimized for WooCommerce, Jetpack & Yoast SEO

Learn more about Object Cache Pro.

¹ Redis is a registered trademark of Redis Ltd. Any rights therein are reserved to Redis Ltd. Any use by Redis Object Cache is for referential purposes only and does not indicate any sponsorship, endorsement or affiliation between Redis and Redis Object Cache.


Answers to common questions and troubleshooting of common errors can be found in the FAQ. Reading these is always faster than waiting for a response in the support forums.


The plugin comes with vast set of configuration options and connection examples. Advanced users may consult Scaling and replication

WP CLI commands

Redis Object Cache has various WP CLI commands, for more information run wp help redis after installing the plugin.


  • Plugin settings, connected to a single Redis server.
  • Plugin settings, displaying recent response time metrics.
  • Plugin settings, showing diagnostic information.
  • Dashboard widget, displaying recent response time metrics.


For detailed installation instructions, please read the extensive installation instructions.


12 de mayo de 2023 1 reply
I updated the plug in and it caused my site to go down. I can't even get into my dashboard. Have my host working on this behind the scenes and "hoping" that fixes the problem. Be EXTREMELY wary of this plug in. Once my site is back up, I'm permanently deleting it.
5 de mayo de 2023 1 reply
Nothing to say: this plugin works as expected. We saw improvement (TTFB & latency) with website and WP admin. Support is a litlle "rough" because most people do not read the docs. But, if you have (very) advanced questions, these guys are awesome!
26 de abril de 2023 1 reply
Redis Object Cache is a fantastic plugin that boosts your WordPress site's performance by utilizing Redis for in-memory data storage. This reduces database queries and significantly speeds up your site. Even for beginners, setting up this plugin is straightforward. Just follow these steps: Install the Redis server on your hosting environment (consult your hosting provider's documentation). Install a PHP Redis client like PhpRedis or Predis. Install and activate the Redis Object Cache plugin in your WordPress dashboard. Go to the plugin settings and enable object caching. Please note: It's essential to configure the Redis Object Cache plugin correctly to avoid caching issues or website errors.
25 de abril de 2023 1 reply
Warning! This plugin is not meant to be installed by beginners. It's not trivial to configure and relies on an external Redis server to do its magic. If you have never configured an application that relies on a Redis server, or never administered a Redis server yourself, this plugin is NOT for you!Instead, as a beginner, you should rely on one of the many, many other caching plugins out there, some of which are very easy to configure and will give you enough of a performance boost.That said, if you read this far, welcome, Advanced WordPress PowerUser™ :-)As a non-beginner, you should know that caching pages to improve performance only goes so far. WordPress-generated websites are far more dynamic than that (unless, of course, your website rarely changes over the years).Static page caching still gives a performance boost when your site has to serve a lot of requests in a short amount of time (i.e. several per second). Serving a static page directly through the webserver is the perfect choice for such scenarios: generate once, and the rest of the requests made in a short interval will never hit the database (nor even the PHP subsystem), but rather served directly from disk, or, even better, from memory.But what about dynamic page changes that occur all the time, in slightly larger intervals of time? Consider how a visitor browses your site: they might navigate via the menu… but also wading through the related posts widget. Which are generated on demand (or close to it), usually presenting a random selection of posts within the same category or tag (or possibly even with a more complex algorithm). 'Random' means that WordPress cannot serve that bit of the page statically — it has to be pre-generated before it gets delivered to the user. If the user goes back, it's reasonable to presume that a different selection is presented; in fact, site admins often want that behaviour by default.Or consider simple search queries. A 'search query', as the name implies is a database query. You can cache the results of the most popular keywords, but... in most scenarios, it will be quite hard to figure out how common a query will be (before it has been typed in) and for how long it should be cached (which also depends on how often the site gets updated).The same applies to things like sliders or image galleries. Sometimes, their order of appearance is fixed in advance (and thus potentially cacheable). But often it's not. It may be random. It may follow an unusual combination of attributes or preferences. Whatever the reason, one should assume that most dynamically-generated content cannot be effectively cached as a static page — not for more than a few seconds, at least.There are several (complex) solutions to address the shortcomings of static page caching and still 'protect' the database from freezing down under the sheer weight of queries to deal with dynamic content. The higher-end plugins usually implement a series of techniques, sometimes giving the WP admin the possibility to pick the preferred technique, and fine-tune it.WordPress, however, is quite helpful in that regard. One possibility, besides static page caching, is to cache a page object. These can loosely be defined as components of the overall page itself — they can be widgets or content injected by some kind of plugin (often automated by the plugin owner & maintainer); WP allows integrating plugins with what they call the object cache.The most advanced caching plugins out there (I'm not mentioning any names; if you are an Advanced WordPress PowerUser™, you know which they are!) have often the option to use the WP object cache as well (sometimes only on the paid version). These plugins, however, are all-in-one solutions; you cannot, generally speaking, cherry-pick the several layers of caching you can use, using different plugins for each. They also configure everything automatically according to the whims of the developer. This is usually a 'good thing' from the perspective of the technical support team — who, when asked why their configuration doesn't work well, will simply request that the user turns off all plugins except theirs. This might or might not be an option in several (most?) cases. Also, it's not guaranteed that the all-in-one solutions are the best in all cases; rather, they tend to excel on some features, while adding others merely as an afterthought. That is, at least, my own experience; your mileage may vary.Redis Object Cache, by contrast, does one thing, and it does it very well. As the name implies, it ties into the WP object cache mechanism. Instead of writing a pre-cached object to disk (or to the database), however, it saves to a Redis server — which can be orders of magnitude faster (since Redis is extremely efficient at storing data, mostly holding it in memory) than writing to disk (not to mention writing to a relational database!). As a bonus, Redis can be configured with distributed replicas, which is essential when scaling up a webserver to handle more traffic.While minimalist in its approach — Redis Object Cache just requires to know basic details to connect to Redis, the choice of database (Redis only has 16 available...), and an eventual key prefix to avoid conflicts with several WP installations on the same server. In fact, that option requires modifying wp-config.php and is not set by default (which drove me insane when installing Redis Object Cache on a second WP install on the same server!). Hopefully, the author will address this issue in a future release of the plugin, and, by default, chooses a reasonable prefix (such as the WP URL, for example, or, for shorter keys, a hashed version of the URL, or even a UUID generated on the spot when installing). To be honest, 'fixing' my mistake was as easy as to flush Redis (a quasi-instant operation) and configuring different prefixes for the keys; a simple operation, and a minute later, I had both sides happily storing their objects on Redis.This was probably the most catastrophic scenario that may happen with Redis Object Cache if you are an Advanced WordPress PowerUser™ 🙂 And the fix is simply to flush Redis. It won't matter much anyway, since, within seconds, Redis will quickly fill its memory with new objects.An added bonus is a nice graph that appears on the Dashboard, showing some rough statistics about the access to the Redis server — measured in single-digit milliseconds. That's right. When rendering a page from scratch, speed matters, and you cannot afford waiting more than a few milliseconds for data to arrive from the cache, readily processed. To the best of my knowledge, no other caching plugin can achieve that kind of speed. Except, of course, for the Pro version of Redis Object Cache, which does some extra magic and manages to cut by half the access time (!). How that feat is accomplish is beyond my ability to understand; but for those mission-critical websites out there, where sysadmins are constantly tweaking the infrastructure in order to shave off a few milliseconds here and there for each page access — well, Redis Object Cache Pro may very well be worth the few dollars charged for it.In my personal case, I don't require almost-sub-millisecond performance squeezed out of Redis, so I'm more than happy with the 'standard' version. Its 'limitations' — absent from the Pro version — are not really an issue. I love its bare-bones simplicity — once properly configured and installed, that is — and the consequent performance boost, which, unlike what may happen with a plain old page-caching system, will benefit every user, even on a WP website with almost zero visitors: Redis Object Cache will — by design — also cache the objects for the WP backoffice. Everything that is an object — and that means every component of WP, including all those on the backoffice — will be cached. This makes a lot of sense during the design (or redesign!) phase, where admins will be constantly going to and fro the many WP options, spread across themes and plugins, until the design is finished. These are repetitive tasks — querying for the same article to be edited, or the same page template to load, etc. — which Redis Object Cache handles admirably well.While I have deployed it on several websites on my (single) server — where Redis is locally installed and shared by a lot of other applications, including PHP itself (for session storage — another performance boost that is built-in into PHP if that option is configured), I'm well aware that my use-case scenario (mostly very low traffic websites) is perhaps over-engineered for the small demands placed on the overall system. Nevertheless, I was happy to see that the MariaDB behemoth — by far the most memory-consuming process that is constantly running, non-stop — was notoriously happy after I deployed Redis Object Cache: that seems to mean that the database is not being hit so aggressively as before. It's hard to get a grasp of how important Redis Object Cache has been in keeping the overall CPU + Memory consumption at relatively low levels; my server simply hasn't got enough traffic to be able to make a before-and-after comparison. However, I can see quite noticeable performance boots on the WP backoffice! In fact, on one website currently under development — which has around one thousand articles spread across more than a dozen categories — I have turned off all caching (to make sure that everybody always sees the 'latest version' under development) except for Redis Object Cache, which works so well and deals flawlessly with 'dirty' objects (i.e. those that have been changed through user intervention), unlike most page caches. The responsiveness has gone up 500% or more — but without a 'serious' test, using well-known benchmarking tools, I can only relay my visual experience, filtered through my perceptions; ultimately, I can only affirm that I perceive many things on the backoffice to be five times faster than before, but cannot guarantee that this will be the case for everybody.What I can — and will! — recommend is to do at least one external test to your Redis-supercharged site, from one of the popular websites calculating metrics. You might get a very positive surprise!In conclusion... for the low-traffic websites I manage (roughly two dozen), all running on the same server (which is quite decent, albeit being almost a decade old...), because I'm always fearing to be 'slashdotted' some day, this simple but effective plugin keeps my database server happy all the time — because it gets so little work to effectively do :)This is the kind of "must use" plugins that every WordPress installation should have as default. Everybody enjoys faster speed and giving the database server a break!
19 de abril de 2023
Hands down the best free Redis plugin available. Well maintained, updated regularly, and the developer is responsive to feedback. What's not to love? 😀
Leer todas las 132 reseñas

Colaboradores y desarrolladores

"Redis Object Cache" es un software de código abierto. Las siguientes personas han colaborado con este plugin.


"Redis Object Cache" ha sido traducido a 9 idiomas locales. Gracias a los traductores por sus contribuciones.

Traduce "Redis Object Cache" a tu idioma.

¿Interesado en el desarrollo?

Revisa el código , echa un vistazo al repositorio SVN o suscríbete al registro de desarrollo por RSS.

Registro de cambios


  • Fix PHP <=7.2 syntax error


  • Flush cache when toggling the object cache
  • Show a custom error message when Redis is unreachable
  • Don’t allow object cache to be enabled when Redis is unreachable
  • Deprecated risky WP_REDIS_SERIALIZER configuration constant, use WP_REDIS_IGBINARY instead
  • Support WP_REDIS_USERNAME when using Predis
  • Show cache hit ratio decimal points in Admin Bar node
  • Obscure secrets when displaying WP_REDIS_SERVERS
  • Improved CloudLinux’s Accelerate WP compatibility
  • Admin bar cache flush now uses AJAX


  • Show dashboard widget only to admins
  • Added Admin Bar node (disable using WP_REDIS_DISABLE_ADMINBAR)
  • Added WP_REDIS_SSL_CONTEXT configuration constant
  • Throw errors when connection error occurs
  • Added support for usernames when using Predis
  • Added support for loading Predis from WP_REDIS_PLUGIN_PATH
  • Made Predis unix socket connections stricter
  • Fixed rare group flushing bug
  • Fixed cluster ping when using Predis
  • Updated Predis to v2.1.2
  • Improved documentation


  • Register wp redis CLI command late
  • Don’t compete with Object Cache Pro for wp redis command
  • Prevent Perflab from overwriting the object cache drop-in
  • Updated Predis to v2.1.1
  • Avoid type error when transaction fails
  • Check for incompatible content type headers


  • Added wp_cache_flush_group() support
  • Updated Credis to v1.14.0
  • Drop $delay parameter from wp_cache_flush()
  • Prevent rare error in diagnostics when reading connection errors


  • Use QM_Data_Cache instead of QM_Data
  • Fixed WP_Error use statement non-compound name warning


  • Added WordPress 6.1 wp_cache_supports() function
  • Updated Predis to v2.0.3
  • Avoid early microtime() calls in WP_Object_Cache::get()
  • Support Query Monitor’s new QM_Data class
  • Throw exception of pipeline returns unexpected results


  • Added redis_cache_add_non_persistent_groups filter
  • Fixed wp_add_dashboard_widget parameters
  • Fixed WP_REDIS_SERVERS replication issue with Predis v2.0
  • Fixed WP_REDIS_CLUSTER string support
  • Fixed issue when MGET fails in get_multiple() call
  • Fixed several warnings in the event of pipeline failures


  • Fixed SVN discrepancies


  • Fixed is_predis() call


  • Added is_predis() helper


  • Fixed bug in wp_cache_add_multiple() and wp_cache_set_multiple()


  • Fixed and improved wp_cache_*_multiple() logic
  • Call redis_object_cache_set action in wp_cache_set_multiple()
  • Call redis_object_cache_delete action in wp_cache_delete_multiple()
  • Check if raw group name is ignored, not sanitized name
  • Removed tracing


  • Bumped PHP requirement to 7.2
  • Fixed rare fatal error in diagnostics
  • Allow Predis v1.1 Composer installs
  • Support using WP_REDIS_CLUSTER string


  • Bumped PHP requirement to 7.0
  • Deprecated Credis and HHVM clients
  • Updated Predis to v2.0.0
  • Updated Credis to v1.13.1
  • Improved cluster readability in diagnostics
  • Improved connecting to clusters
  • Fixed pinging clusters after connecting
  • Fixed several bugs in connect_using_credis()


  • Fixed a bug in wp_cache_delete_multiple() when using Predis
  • Fixed a bug in wp_cache_add_multiple() when cache addition is suspended


  • Removed broken wp_cache_add_multiple() function


  • Improve metrics label/tooltip formatting
  • Fix metrics chart not rendering
  • Updated Predis to v1.1.10
  • Updated Credis to v1.13.0
  • Support composer/installers v1 and v2
  • Link to settings page when foreign drop-in was found
  • Added wp_cache_flush_runtime() function
  • Added wp_cache_add_multiple() function
  • Added wp_cache_delete_multiple() function


  • Added support for Relay
  • Minor UX fixes and improvements
  • Fixed PHP 8.1 deprecation notice
  • Updated ApexCharts to v3.31.0


  • PHP 8.1 compatibility fixes
  • Upgraded to Predis v1.1.9
  • Added settings link to widget
  • Overhauled diagnostics pane
  • Updated ApexCharts to v3.30.0
  • Redirect to plugin settings after activation
  • Fixed wrong path to diagnostics.php file
  • Fixed chart overflow in settings tab
  • Fixed Predis cluster ping
  • Avoid warning when content folder is not writeable


  • Added metrics diagnostics
  • Added WP_Object_Cache::decr() alias
  • Moved diagnostics.php file


  • Fix release


  • Make metric identifier unique
  • Set unique prefix for sites hosted on Cloudways
  • Don’t print HTML debug comment when WP_CLI is true


  • Added redis_object_cache_trace action and WP_REDIS_TRACE constant
  • Updated ApexCharts to v3.26.0
  • Fixed and issue with WP_REDIS_DISABLE_METRICS


  • Code cleanup
  • Fixed missing metrics
  • Fixed filesystem test


  • Updated Credis to v1.11.4
  • Fixed drop-in notice styling
  • Moved metrics into dedicated class
  • Added redis_cache_validate_dropin filter
  • Use WP_DEBUG_DISPLAY (instead of WP_DEBUG) constant to display debug information
  • Fixed rare error in wp_cache_get_multiple()
  • Removed intval() usage


  • Reverted build_key() changes due to issues in multisite environments


  • Made Object Cache Pro card translatable
  • Added WP_REDIS_SERIALIZER to diagnostics
  • Improved speed of build_key()
  • Support settings WP_REDIS_PREFIX and WP_REDIS_SELECTIVE_FLUSH via environment variable
  • Added WP_REDIS_METRICS_MAX_TIME to adjust stored metrics timeframe
  • Delay loading of text domain and schedule until init hook
  • Upgraded bundled Predis library to v1.1.6
  • Prevent variable referencing issue in connect_using_credis()


  • Updated bundled Predis library to v1.1.4
  • Made redis-cache a global group for improved metrics on multisite
  • Switched to short array syntax
  • Added @since tags to all hooks
  • Use parse_url() instead of wp_parse_url() in drop-in
  • Fixed plugin instance variable name in wp redis status


  • Fixed bytes metrics calculation
  • Fixed an issue with non-standard Predis configurations
  • Improve WordPress Coding Standards


  • Fixed an issue in wp_cache_get_multiple() when using Predis
  • Prevent undefined index notice in diagnostics


  • Fixed unserializing values in wp_cache_get_multiple()


  • Highlight current metric type using color
  • Show "Metrics" tab when metrics are disabled
  • Refactored connection and Redis status logic
  • Updated Predis to v1.1.2
  • Remove Predis deprecation notice
  • Fixed fetching derived keys in wp_cache_get_multiple()


  • Fixed tabs not working in 2.0.6 and 2.0.7 due to SVN issue


  • Fixed issue with wp_cache_get_multiple()


  • Added experimental filesystem test to diagnostics
  • Refactored settings tab logic (fixed jumping, too)
  • Fixed issues with wp_cache_get_multiple()
  • Return boolean from wp_cache_delete()
  • Use redis-cache as JS event namespace
  • Hide Pro line in widget when banners are disabled
  • Renamed redis_object_cache_get_multi action to redis_object_cache_get_multiple


Version 2.0 is a significant rewrite of the plugin. Please read the v2.0.0 release notes.

  • Fixed multisite action buttons not working
  • Removed outdated PHP 5.4 warning
  • Added read_timeout support to Credis
  • Display connection parameters when using Credis
  • Added wiki link to Predis upgrade notice


  • Attempt to reliably update the dropin when it’s outdated
  • Show ACL username on settings screen
  • Show full diagnostics with wp redis status
  • Always set FS_CHMOD_FILE when copying the object-cache.php
  • Don’t encode bullets in password diagnostics
  • Call redis_object_cache_update_dropin during dropin update


  • Hide "Metrics" tab when metrics are disabled
  • Fixed admin.js not loading in multisite environments
  • Avoid fatal error when interacting with metrics but Redis went away
  • Added WP_Object_Cache::__get() for backwards compatibility


  • Updated POT file and comments for translators


  • Support older versions of Query Monitor
  • Made "Dropin" status more helpful
  • Hide Redis version in settings when it isn’t available
  • Collapsed dependency paths using composer-custom-directory-installer package
  • Prevent QM_Collector conflicts with other plugins
  • Prevent metric issues when cache is not available
  • Fixed "Settings" link in plugin list
  • Fixed WP_REDIS_DISABLED logic


Version 2.0 is a significant rewrite. The plugin now requires PHP 5.6, just like WordPress 5.2 does.

The GitHub and Composer repository was moved from tillkruss/redis-cache to rhubarbgroup/redis-cache.

On multisite networks, be sure to "Network Activate" the plugin after upgrading to v2.x.

  • Require PHP 5.6
  • Plugin is now "network-only"
  • Switch to WPCS for code standards
  • Overhauled the settings screen
  • Added object cache metrics (on dashboard widget and settings)
  • Added support for Query Monitor
  • Added Rhubarb\RedisCache namespace to all files
  • Added support for WP 5.5’s new wp_cache_get_multi() function
  • Added redis_object_cache() function to retrieve plugin instance
  • Added dropin warnings to network dashboard
  • Added support for setting Sentinel database numbers
  • Support Redis 6 ACL username and password authentication
  • Support overwriting existing dropin on setting screen
  • Use singleton pattern to instantiate plugin
  • Use Composer to install and load Predis
  • Update object cache dropin during plugin update
  • Use separate methods to connect with all clients
  • Added themes as ignored group
  • Changed default connection and read timeout to 1 second
  • Prevent race condition in add_or_replace()
  • Renamed WP_CACHE_KEY_SALT to WP_REDIS_PREFIX for clarity
  • Replaced "slave" terminology with "replica"
  • Only SELECT database when it’s not 0


  • Fixed issue with footer comment showing during AJAX requests


  • Improved group name sanitization (thanks @naxvog)
  • Prevent fatal error when replacing foreign dropin
  • Added HTML footer comment with optional debug information
  • Removed prefix suggestions

The HTML footer comment only prints debug information when WP_DEBUG is enabled. To disable the comment entirely, set the WP_REDIS_DISABLE_COMMENT constant to true.


  • Fixed missing $info variable assignment in constructor
  • Fixed MaxTTL warning condition
  • Switched to using default button styles


  • Added warning message about invalid MaxTTL
  • Added warning about unmaintained Predis library
  • Added suggestion about shorter, human-readable prefixes
  • Added Redis Cache Pro compatibility to settings
  • Fixed flushing the cache when the prefix contains special characters
  • Fixed calling Redis INFO when using clusters
  • Cleaned up the settings a little bit


  • Added support for PhpRedis TLS connections
  • Added support for timeout, read timeout and password when using PhpRedis cluster
  • Fixed issue with INFO command
  • Fixed object cloning when setting cache keys


  • Added object cloning to in-memory cache
  • Fixed PHP notice related to read_timeout parameter


Please flush the object cache after updating the drop to v1.5.5 to avoid dead keys filling up Redis memory.

  • Removed lowercasing keys
  • Remove scheduled metrics event
  • Fixed Redis version call when using replication


  • Removed metrics


  • Fixed: Call to undefined function get_plugin_data()
  • Fixed: Call to undefined method WP_Object_Cache::redis_version()


  • Added Redis version to diagnostics
  • Added WP_REDIS_DISABLE_BANNERS constant to disable promotions
  • Fixed an issue with redis.replicate_commands()


This plugin turned 5 years today (Nov 14th) and its only fitting to release the business edition today as well.
Object Cache Pro is a truly reliable, highly optimized and easy to debug rewrite of this plugin for SMBs.

  • Added execution times to actions
  • Added WP_REDIS_VERSION constant
  • Fixed PhpRedis v3 compatibility
  • Fixed an issue with selective flushing
  • Fixed an issue with mb_* functions not existing
  • Replaced Email Address Encoder card with Redis Cache Pro card
  • Gather version metrics for better decision making


Since Predis isn’t maintained any longer, it’s highly recommended to switch over to PhpRedis (the Redis PECL extension).

  • Improved Redis key name builder
  • Added support for PhpRedis serializers
  • Added redis_object_cache_error action
  • Added timeout, read-timeout and retry configuration
  • Added unflushable groups (defaults to ['userlogins'])
  • Fixed passwords not showing in server list


  • Require PHP 5.4 or newer
  • Use pretty print in diagnostics
  • Throw exception if Redis library is missing
  • Fixed cache not flushing for some users
  • Fixed admin issues when WP_REDIS_DISABLED is false


  • Added graceful Redis failures and WP_REDIS_GRACEFUL constant
  • Improved cluster support
  • Added redis_cache_expiration filter
  • Renamed redis_object_cache_get filter to redis_object_cache_get_value


  • Fixed potential fatal error related to wp_suspend_cache_addition()


  • Added support for igbinary
  • Added support for wp_suspend_cache_addition()


  • Fixed WP_REDIS_SHARDS not showing up in server list
  • Fixed WP_REDIS_SHARDS not working when using PECL extension
  • Removed WP_REDIS_SCHEME and WP_REDIS_PATH leftovers


  • Switched from single file Predis version to full library


  • Revert back to single file Predis version


  • Added support for Redis Sentinel
  • Added support for sharing
  • Switched to PHAR version of Predis
  • Improved diagnostics
  • Added $fail_gracefully parameter to WP_Object_Cache::__construct()
  • Always enforce WP_REDIS_MAXTTL
  • Pass $selective and $salt to redis_object_cache_flush action
  • Don’t set WP_CACHE_KEY_SALT constant


  • Added basic diagnostics to admin interface
  • Added WP_REDIS_DISABLED constant to disable cache at runtime
  • Prevent "Invalid plugin header" error
  • Return integer from increment() and decrement() methods
  • Prevent object cache from being instantiated more than once
  • Always separate cache key prefix and group by semicolon
  • Improved performance of build_key()
  • Only apply redis_object_cache_get filter if callbacks have been registered
  • Fixed add_or_replace() to only set cache key if it doesn’t exist
  • Added redis_object_cache_flush action
  • Added redis_object_cache_enable action
  • Added redis_object_cache_disable action
  • Added redis_object_cache_update_dropin action


  • Added WP-CLI support
  • Show host and port unless scheme is unix
  • Updated default global and ignored groups
  • Do a cache flush when activating, deactivating and uninstalling


  • Updated Predis to v1.1.1
  • Added redis_instance() method
  • Added incr() method alias for Batcache compatibility
  • Added redis_object_cache_delete action
  • Use WP_PLUGIN_DIR with WP_CONTENT_DIR as fallback
  • Set password when using a cluster or replication
  • Show Redis client in stats()
  • Change visibility of $cache to public
  • Use old array syntax, just in case


  • Make sure $result is not false in WP_Object_Cache::get()


  • Fixed connection issue


  • New admin interface
  • Added support for wp_cache_get()’s $force and $found parameter
  • Added support for clustering and replication with Predis


  • UI improvements


  • Added redis_object_cache_set action
  • Added redis_object_cache_get action and filter
  • Prevented duplicated admin status messages
  • Load bundled Predis library only if necessary
  • Load bundled Predis library using WP_CONTENT_DIR constant
  • Updated stats() method output to be uniform with WordPress


  • Added composer.json
  • Added deactivation and uninstall hooks to delete object-cache.php
  • Added local serialization functions for better advanced-cache.php support
  • Updated bundled Predis version to 1.0.3
  • Updated heading structure to be semantic


  • Added Multisite support
  • Moved admin menu under Settings menu
  • Fixed PHP notice in get_redis_client_name()


  • Call select() and optionally auth() if HHVM extension is used


  • Added support for HHVM’s Redis extension
  • Added support for PECL Redis extension
  • Added WP_REDIS_CLIENT constant, to set preferred Redis client
  • Added WP_REDIS_MAXTTL constant, to force expiration of cache keys
  • Improved add_or_replace(), get(), set() and delete() methods
  • Improved admin screen styles
  • Removed all internationalization/localization from drop-in


  • Added "Flush Cache" button
  • Added support for UNIX domain sockets
  • Improved cache object retrieval performance significantly
  • Updated bundled Predis library to version 1.0.1


  • Load plugin translations
  • Hide global admin notices from non-admin users
  • Prevent direct file access to redis-cache.php and admin-page.php
  • Colorize "Disable Object Cache" button
  • Call Predis\Client->connect() to avoid potential uncaught Predis\Connection\ConnectionException


  • Initial release