Discover, trust, install: FAIR 1.0 is here

Redis Object Cache
Version: 2.7.0
Description
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.
Troubleshooting
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.
Configuration
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.
Installation
For detailed installation instructions, please read the extensive installation instructions.
Screenshots
Reviews
Awesome Plugin
By MDZ (mdesignfa) on September 27, 2025
recently I could config & install PhpRedis on my dedicated server and im using the Redis cache plugin with my wordpress setup
Nice work bro Thanks a lot ❤️
I also recommend using the Pro version (Object Cache Pro) with more options and better performance
objectcache[DOT]pro
Easy setup
By surviving404 on September 13, 2025
When I was getting to know about object cache and other things, I was worried about spending lots of time setting it up. But I rarely face any error and it was quick. 🙂
Great plugin
By an347 on August 18, 2025
Great plugin
Great plugin
By mikefury on August 1, 2025
Thank you.
Highly recommend for anyone needs solutions for your website
Awesome plugin with top-notch support!
By andypp on July 24, 2025
Redis Object Cache works great and really helps speed up my site. But what impressed me the most was the support: super responsive and helpful. Till fixed a compatibility issue almost immediately. Highly recommended!
Good but not good enough
By Vanderlindemedia (jvanderlinde) on June 7, 2025
Not recommended, when your REDIS instance on server blows out. This plugin will make your site crash when it's unable to connect. Litespeed build in Object cache storage on the other hand simply disables the Object caching but continues to run the website.
good
By toritran84 on March 30, 2025
my web speed than
"Error establishing a Redis connection" with dockerized WordPress 6.7.1
By cuktrshmls on December 8, 2024
Hello Till,
I’m reaching out regarding an issue we’ve encountered when using the Redis Object Cache plugin with a fresh installation of WordPress 6.7.1. Despite following the official setup guidelines, our WordPress site fails with the following error:
Error establishing a Redis connection
Connection refused
WordPress is unable to establish a connection to Redis. This means that the connection information in your
wp-config.php
file are incorrect, or that the Redis server is not reachable.
- Is the correct Redis host and port set?
- Is the Redis server running?
If you need help, please read the installation instructions.
To disable Redis, delete the
object-cache.php
file in the/wp-content/
directory.
Here are the details of our setup:
- WordPress Version: 6.7.1 (fresh installation)
- Redis Plugin Version: Redis Object Cache 2.5.4
- Server Environment:
- Dockerized Setup: Using
docker-compose
- Relevant Containers:
- WordPress (
wordpress:php8.0-fpm
)- Redis (
redis:alpine
)- WP-CLI (
custom-wordpress-cli
built on the official WP-CLI image)- Nginx (
nginx:alpine
) for frontend- MariaDB (
mariadb:latest
) for the database- Varnish (
varnish:stable
) for caching- Redis Configuration:
- Redis is running in the
my-redis
container and is reachable from other containers within the Docker bridge network (my_network
).- Redis configuration: Default Alpine Redis settings (
bind *
,protected-mode no
).wp-config.php
Constants for Redis
define("WP_REDIS_HOST", "my-redis");
define("WP_REDIS_PORT", 6379);
define("WP_REDIS_DATABASE", 0);
define("WP_REDIS_DEBUG", true);
define("WP_DEBUG", true);
define("WP_DEBUG_LOG", true);
define("WP_DEBUG_DISPLAY", false);
@ini_set("display_errors", 0);
define("WP_REDIS_TIMEOUT", 5);
define("WP_REDIS_READ_TIMEOUT", 5);
- Plugin Behavior:
- Activating the plugin creates the
object-cache.php
drop-in at/wp-content/
.- The Redis server is accessible (
PONG
response from Redis CLI within the WordPress container).- Enabling Object Cache via the plugin causes the "Error establishing a Redis connection" issue.
Steps we’ve tried:
- Verified network connectivity:
- Pinged
my-redis
from the WordPress container (ping my-redis
works).- Successfully executed
redis-cli -h my-redis ping
from the WordPress container (PONG
response).- Reviewed Redis logs:
- No errors in Redis logs, and
CONFIG GET
shows the expected settings (bind
,protected-mode
, etc.).- Tested Redis connectivity from WP-CLI:
- WP-CLI reports Redis as reachable, but enabling Object Cache causes the same error.
- Tried replacing the
object-cache.php
file:
- Replaced it with the latest version from the plugin's GitHub repository (branch:
develop
).- Reinstalled the plugin:
- Deactivated, uninstalled, and reinstalled the Redis Object Cache plugin. The error persisted.
- Checked for known compatibility issues:
- Verified that Redis Object Cache 2.5.4 supports Redis 7.4.1 and PHP 8.0.
Summary of issue
- Redis is reachable and functional, yet WordPress fails to connect when Object Cache is enabled.
- The error specifically points to
RedisException: Connection refused
in/wp-content/object-cache.php
.- We suspect a compatibility issue between Redis Object Cache and WordPress 6.7.1 but have not found evidence of this in community forums or issue trackers.
Questions:
- Are there known issues with the Redis Object Cache plugin and WordPress 6.7.1 or Redis 7.4.1?
- Could this be related to the
object-cache.php
drop-in, or should we consider alternative configurations for Redis?- Are there any additional debug steps or alternative plugin versions (e.g., pre-releases) we should test?
Drop in problem
By barbaroshh on November 22, 2024
Hello
Why does it give the error Drop in? I couldn't find a solution. Can you help?
Status: Drop-in is invalid Client: Drop-in: Invalid Disabled: No PhpRedis: 6.0.2 Relay: Not loaded Predis: 2.1.2 Credis: Not loaded PHP Version: 8.3.13 Plugin Version: 2.5.4 Redis Version: Unknown Multisite: No Metrics: Disabled Metrics recorded: 0 Filesystem: Writable WP_CACHE_KEY_SALT: "AR>)?)MC#Su Quv_=Z tpd=5.S*Y#`%n6n .(#h=H93-ek!2X%HnidD$Lz[^F$jf" WP_REDIS_PLUGIN_PATH: "/home/nep.com.uz/public_html/wp-content/plugins/redis-cache" Drop-ins: [ "atec APCu-Object-Cache v1.0.8 by Chris Ahrweiler" ]
Very disappointed with paid version
By jussipv on October 26, 2024
I used the free version on my site at first, managed to install it and seemed to work based on what Query Monitor plugin showed. Still wasn't happy with site performance though so I bought the paid version which is said to be "optimized for WooCommerce" and "Rewritten for raw performance".
Well, after paying a monthly fee of $95 (which is normally a yearly license fee for a plugin btw) and installing the pro version following step-by-step guide and the basic settings found from the Docs, Query Monitor showed again that the object cache is working.
The only issue now was that page load times which were 3-4 seconds before in my store became 8-14 seconds long and I started getting complaints from my customers about very slow store. I disabled the plugin and everything went back to normal (3-4 second load times). I was hoping to cut 1-2 seconds off from the 3-4 seconds but it actually tripled the load times...
My server resources never hit a peak above 70% (6 cpus, 16 GB RAM) so it's not having enough resources. It has to be something with the plugin setup.
I contacted "support" of the paid plugin which was a chatbot on their website. Tried asking for help in setting up the plugin because most likely there is something I could do to make it work better, or that's what I thought at least. But paying $95/month I expected to get some help from the developer like has always been the case with any paid WooCommerce plugin from WooCommerce.com. The chatbot said that they will be back "later today" to answer my message. This was October 18th which is 8 days ago. Still to this day I haven't gotten a response.
Well they say "All purchases come with a 14-day, no hassle, 100% money back guarantee." on their website and as I was very disappointed with the plugin and the support, I contacted them again. Through the chatbot because that seems to be the only easily available channel to contact them. I said "Refund" to the chatbot and it said "The team will get back to you on this. Object Cache Pro will be back later today." This is now 2 days ago.
I did find an email to their support from the initial order confirmation email so I sent an email on Thursday (2 days ago) with a high priority to them. No response to that either.
This is what reads on their website as a selling point: "Expert, hands-on help setting up your object cache, and receive a response in as little as 30 minutes from your dedicated engineer via email or Slack."
Here I am 8 days later waiting for that help. You're not waiting for that 14 days money-back guarantee to run out are you?
Anyway I'm taking this up with Stripe now and if they don't help I'll make a report to my bank and they'll make a chargeback which I believe will cost more to the company than just giving me the "hassle-free refund".
And no I am not interested in setting up the plugin anymore. By paying $95/month I expect a response within a week to my support request. I've said within the first 14 days of my purchase that I want a refund so I still expect to get it.
I didn't want to make this public but you kind of left me no choice.
Changelog
2.7.0
- Preserve key TTL when calling (in|de)crement methods
- Updated
wp_cache_*()
function signatures to match core - Removed deprecated HHVM support
- Removed deprecated
WP_REDIS_SERIALIZER
constant
2.6.5
- Fixed an issue with (in|de)crement cache values when using igbinary
2.6.4
- Prevent some deprecation notices
- Fixed an issue with (in|de)crement cache values
2.6.3
- Switch to
E_USER_DEPRECATED
instead of_doing_it_wrong()
in drop-in - Fixed error when using Credis (deprecated) as client
2.6.2
- Fixed more PHP 7.2 heredoc parsing errors
2.6.1
- Fixed PHP 7.2 heredoc parsing error
- Fixed call to undefined function
wp_rand()
2.6.0
- Added
Primary Branch
header - Added
id
to script/style tags - Upgraded Predis to v2.4.0
- Upgraded Credis to v1.17.0
- Mark as tested up to 6.8
- Adhere to Plugin Check (PCP)
- Fixed (in|de)crement not working with serializer
- Fixed rare replication mode issue
- Fixed rare fatal error in diganostics
2.5.4
- Respect
WP_REDIS_SCHEME
for Cluster connections - Fixed issue with Predis and
SentinelReplication
connection - Fixed double-slash in
admin.css
URL
2.5.3
- Added
WP_REDIS_DISABLE_GROUP_FLUSH
constant - Added
redis_cache_manager_capability
filter andWP_REDIS_MANAGER_CAPABILITY
constant - Added
WP_REDIS_SSL_CONTEXT
support for PhpRedis cluster connections - Fixed several issues with Predis and cluster/replicated connection
- Fixed another rare fatal error in
show_error_and_die()
2.5.2
- Respect
WP_REDIS_FLUSH_TIMEOUT
in Lua flush scripts - Improve
DISALLOW_FILE_MODS
support - Reverted behavioral change to
sanitize_key_part()
- Fixed rare fatal error in
show_error_and_die()
(again)
2.5.1
- Added timeouts to diagnostics
- Support rare PHP installations without
sockets
extension - Fixed rare fatal error in
show_error_and_die()
- Fixed deprecation notice warning in
sanitize_key_part()
2.5.0
- Require WordPress 4.6 or newer
- Load text-domain only when needed
- Added
WP_REDIS_DISABLE_DROPIN_CHECK
constant - Respect
file_mod_allowed
filter andDISALLOW_FILE_MODS
constant - Renamed
.redis-write-test.tmp
test file toobject-cache.tmp
- Call
redis_object_cache_error
action beforewp_die()
- Allow
WP_REDIS_PLUGIN_PATH
to be defined elsewhere - Added experimental flush timeout (defaults to
5
seconds) - Dropped unnecessary default ignored groups
2.4.4
- Improved handling of unexpected transaction results
2.4.3
- Fixed PHP
<=7.2
syntax error - Fixed loading error-page translations
2.4.2
- Made admin-bar script more robust
- Improved recovery instructions on
redis-error.php
- Improved CloudLinux detection
- Localization improvements
- Prevent W3 Total Cache and LiteSpeed Cache from overwriting drop-in
- Fixed ACL username support when using Predis and array syntax
2.4.1
- Fix PHP
<=7.2
syntax error
2.4.0
- 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, useWP_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
2.3.0
- 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
2.2.4
- 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
2.2.3
- Added
wp_cache_flush_group()
support - Updated Credis to v1.14.0
- Drop
$delay
parameter fromwp_cache_flush()
- Prevent rare error in diagnostics when reading connection errors
2.2.2
- Use
QM_Data_Cache
instead ofQM_Data
- Fixed
WP_Error
use statement non-compound name warning
2.2.1
- Added WordPress 6.1
wp_cache_supports()
function - Updated Predis to v2.0.3
- Avoid early
microtime()
calls inWP_Object_Cache::get()
- Support Query Monitor’s new
QM_Data
class - Throw exception of pipeline returns unexpected results
2.2.0
- 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 inget_multiple()
call - Fixed several warnings in the event of pipeline failures
2.1.6
- Fixed SVN discrepancies
2.1.5
- Fixed
is_predis()
call
2.1.4
- Added
is_predis()
helper
2.1.3
- Fixed bug in
wp_cache_add_multiple()
andwp_cache_set_multiple()
2.1.2
- Fixed and improved
wp_cache_*_multiple()
logic - Call
redis_object_cache_set
action inwp_cache_set_multiple()
- Call
redis_object_cache_delete
action inwp_cache_delete_multiple()
- Check if raw group name is ignored, not sanitized name
- Removed tracing
2.1.1
- Bumped PHP requirement to 7.2
- Renamed
WP_REDIS_DIR
toWP_REDIS_PLUGIN_DIR
- Fixed rare fatal error in diagnostics
- Allow Predis v1.1 Composer installs
- Support using
WP_REDIS_CLUSTER
string
2.1.0
- 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()
2.0.26
- Fixed a bug in
wp_cache_delete_multiple()
when using Predis - Fixed a bug in
wp_cache_add_multiple()
when cache addition is suspended
2.0.25
- Removed broken
wp_cache_add_multiple()
function
2.0.24
- 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
2.0.23
- Added support for Relay
- Minor UX fixes and improvements
- Fixed PHP 8.1 deprecation notice
- Updated ApexCharts to v3.31.0
2.0.22
- 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
2.0.21
- Added metrics diagnostics
- Added
WP_Object_Cache::decr()
alias - Moved
diagnostics.php
file
2.0.20
- Fix wp.org release
2.0.19
- Make metric identifier unique
- Set unique prefix for sites hosted on Cloudways
- Don’t print HTML debug comment when
WP_CLI
istrue
2.0.18
- Added
redis_object_cache_trace
action andWP_REDIS_TRACE
constant - Updated ApexCharts to v3.26.0
- Fixed and issue with
WP_REDIS_DISABLE_METRICS
2.0.17
- Code cleanup
- Fixed missing metrics
- Fixed filesystem test
2.0.16
- 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 ofWP_DEBUG
) constant to display debug information - Fixed rare error in
wp_cache_get_multiple()
- Removed
intval()
usage
2.0.15
- Reverted
build_key()
changes due to issues in multisite environments
2.0.14
- Made Object Cache Pro card translatable
- Added
WP_REDIS_SERIALIZER
to diagnostics - Improved speed of
build_key()
- Support settings
WP_REDIS_PREFIX
andWP_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()
2.0.13
- 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 ofwp_parse_url()
in drop-in - Fixed plugin instance variable name in
wp redis status
2.0.12
- Fixed bytes metrics calculation
- Fixed an issue with non-standard Predis configurations
- Improve WordPress Coding Standards
2.0.11
- Fixed an issue in
wp_cache_get_multiple()
when using Predis - Prevent undefined index notice in diagnostics
2.0.10
- Fixed unserializing values in
wp_cache_get_multiple()
2.0.9
- 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()
2.0.8
- Fixed tabs not working in 2.0.6 and 2.0.7 due to WP.org SVN issue
2.0.7
- Fixed issue with
wp_cache_get_multiple()
2.0.6
- 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 toredis_object_cache_get_multiple
2.0.5
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
2.0.4
- 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 theobject-cache.php
- Don’t encode bullets in password diagnostics
- Call
redis_object_cache_update_dropin
during dropin update
2.0.3
- 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
2.0.2
- Updated POT file and comments for translators
2.0.1
- 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
2.0.0
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
- Removed
CUSTOM_USER_TABLE
andCUSTOM_USER_META_TABLE
weirdness - 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
toWP_REDIS_PREFIX
for clarity - Replaced “slave” terminology with “replica”
- Only
SELECT
database when it’s not0
1.6.1
- Fixed issue with footer comment showing during AJAX requests
1.6.0
- 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
.
1.5.9
- Fixed missing
$info
variable assignment in constructor - Fixed MaxTTL warning condition
- Switched to using default button styles
1.5.8
- 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
1.5.7
- 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
1.5.6
- Added object cloning to in-memory cache
- Fixed PHP notice related to
read_timeout
parameter
1.5.5
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
1.5.4
- Removed metrics
1.5.3
- Fixed: Call to undefined function
get_plugin_data()
- Fixed: Call to undefined method
WP_Object_Cache::redis_version()
1.5.2
- Added Redis version to diagnostics
- Added
WP_REDIS_DISABLE_BANNERS
constant to disable promotions - Fixed an issue with
redis.replicate_commands()
1.5.1
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
1.5.0
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
1.4.3
- 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
isfalse
1.4.2
- Added graceful Redis failures and
WP_REDIS_GRACEFUL
constant - Improved cluster support
- Added
redis_cache_expiration
filter - Renamed
redis_object_cache_get
filter toredis_object_cache_get_value
1.4.1
- Fixed potential fatal error related to
wp_suspend_cache_addition()
1.4.0
- Added support for igbinary
- Added support for
wp_suspend_cache_addition()
1.3.9
- Fixed
WP_REDIS_SHARDS
not showing up in server list - Fixed
WP_REDIS_SHARDS
not working when using PECL extension - Removed
WP_REDIS_SCHEME
andWP_REDIS_PATH
leftovers
1.3.8
- Switched from single file Predis version to full library
1.3.7
- Revert back to single file Predis version
1.3.6
- Added support for Redis Sentinel
- Added support for sharing
- Switched to PHAR version of Predis
- Improved diagnostics
- Added
WP_REDIS_SELECTIVE_FLUSH
- Added
$fail_gracefully
parameter toWP_Object_Cache::__construct()
- Always enforce
WP_REDIS_MAXTTL
- Pass
$selective
and$salt
toredis_object_cache_flush
action - Don’t set
WP_CACHE_KEY_SALT
constant
1.3.5
- 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()
anddecrement()
methods - Prevent object cache from being instantiated more than once
- Always separate cache key
prefix
andgroup
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
1.3.4
- 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
1.3.3
- Updated Predis to
v1.1.1
- Added
redis_instance()
method - Added
incr()
method alias for Batcache compatibility - Added
WP_REDIS_GLOBAL_GROUPS
andWP_REDIS_IGNORED_GROUPS
constant - Added
redis_object_cache_delete
action - Use
WP_PLUGIN_DIR
withWP_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
1.3.2
- Make sure
$result
is notfalse
inWP_Object_Cache::get()
1.3.1
- Fixed connection issue
1.3
- New admin interface
- Added support for
wp_cache_get()
‘s$force
and$found
parameter - Added support for clustering and replication with Predis
1.2.3
- UI improvements
1.2.2
- 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
1.2.1
- 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
1.2
- Added Multisite support
- Moved admin menu under Settings menu
- Fixed PHP notice in
get_redis_client_name()
1.1.1
- Call
select()
and optionallyauth()
if HHVM extension is used
1.1
- 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()
anddelete()
methods - Improved admin screen styles
- Removed all internationalization/localization from drop-in
1.0.2
- 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
1.0.1
- Load plugin translations
- Hide global admin notices from non-admin users
- Prevent direct file access to
redis-cache.php
andadmin-page.php
- Colorize “Disable Object Cache” button
- Call
Predis\Client->connect()
to avoid potential uncaughtPredis\Connection\ConnectionException
1.0
- Initial release