Plugin / WP Redis
Pantheon, Josh Koenig, Matthew Boynes, Daniel Bachhuber, Alley InteractiveChangelog
Changelog
0.7.1 (December 14, 2018)
- Better support in
wp_cache_init()for drop-ins like LudicrousDB [#231]. - Cleans up PHPCS issues.
0.7.0 (August 22, 2017)
- Adds filterable connection methods to permit use of Predis. See humanmade/wp-redis-predis-client for more details.
0.6.2 (June 5, 2017)
- Bug fix: Preserves null values in internal cache.
- Bug fix: Converts numeric values to their true type when getting.
0.6.1 (February 23, 2017)
- Bug fix: correctly passes an empty password to
redis-cli. - Variety of improvements to the test suite.
0.6.0 (September 21, 2016)
- Introduces three new WP-CLI commands:
wp redis debugto display cache hit/miss ratio for any URL;wp redis infoto display high-level Redis statistics;wp redis enableto create theobject-cache.phpsymlink. - Permits a Redis database to be defined with
$redis_server['database']. - Introduces
wp_cache_add_redis_hash_groups(), which permits registering specific groups to use Redis hashes, and is more precise than our existingWP_REDIS_USE_CACHE_GROUPSconstant.
0.5.0 (April 27, 2016)
- Performance boost! Removes redundant
existscall fromwp_cache_get(), which easily halves the number of Redis calls. - Uses
add_action()and$wpdbin a safer manner for compatibility with Batcache, which loads the object cache before aforementioned APIs are available. - For debugging purposes, tracks number of calls to Redis, and includes breakdown of call types.
- Adds a slew of more explicit test coverage against existing features.
- For consistency with the actual Redis call, calls
delinstead ofdelete. - Bug fix: If a group isn’t persistent, don’t ever make an
existscall against Redis.
0.4.0 (March 23, 2016)
- Introduces
wp redis-cli, a WP-CLI command to launch redis-cli with WordPress’ Redis credentials. - Bug fix: Ensures fail back mechanism works as expected on multisite, by writing to sitemeta table instead of the active site’s options table.
- Bug fix: Uses ‘default’ as the default cache group, mirroring WordPress core, such that
$wp_object_cache->add( 'foo', 'bar' )===wp_cache_add( 'foo', 'bar' ).
0.3.0 (February 11, 2016)
- Introduces opt-in support for Redis cache groups. Enable with
define( 'WP_REDIS_USE_CACHE_GROUPS', true );. When enabled, WP Redis persists cache groups in a structured manner, instead of hashing the cache key and group together. - Uses PHP_CodeSniffer and WordPress Coding Standards sniffs to ensure WP Redis adheres to WordPress coding standards.
- Bug fix: Permits use of a Unix socket in
$redis_server['host']by ensuring the supplied$portis null.
0.2.2 (November 24, 2015)
- Bug fix: use
INSERT IGNORE INTOinstead ofINSERT INTOto prevent SQL errors when two concurrent processes attempt to write failback flag at the same time. - Bug fix: use
E_USER_WARNINGwithtrigger_error(). - Bug fix: catch Exceptions thrown during authentication to permit failing back to internal object cache.
0.2.1 (November 17, 2015)
- Bug fix: prevent SQL error when
$wpdb->optionsisn’t yet initialized on multisite.
0.2.0 (November 17, 2015)
- Gracefully fails back to the WordPress object cache when Redis is unavailable or intermittent. Previously, WP Redis would hard fatal.
- Triggers a PHP error if Redis goes away mid-request, for you to monitor in your logs. Attempts one reconnect based on specific error messages.
- Forces a flushAll on Redis when Redis comes back after failing. This behavior can be disabled with the
WP_REDIS_DISABLE_FAILBACK_FLUSHconstant. - Show an admin notice when Redis is unavailable but is expected to be.
0.1
- Initial commit of working code for the benefit of all.
Ratings
Rating breakdown
Details Information
Version
First Released
Total Downloads
Wordpress Version
Tested up to:
Require PHP Version:
Tags
Contributors
Languages
The plugin hasn't been transalated in any language other than English.
DIRECTORY DISCLAIMER
The information provided in this THEME/PLUGIN DIRECTORY is made available for information purposes only, and intended to serve as a resource to enable visitors to select a relevant theme or plugin. wpSocket gives no warranty of any kind, express or implied with regard to the information, including without limitation any warranty that the particular theme or plugin that you select is qualified on your situation.
The information in the individual theme or plugin displayed in the Directory is provided by the owners and contributors themselves. wpSocket gives no warranty as to the accuracy of the information and will not be liable to you for any loss or damage suffered by you as a consequence of your reliance on the information.
Links to respective sites are offered to assist in accessing additional information. The links may be outdated or broken. Connect to outside sites at your own risk. The Theme/Plugin Directory does not endorse the content or accuracy of any listing or external website.
While information is made available, no guarantee is given that the details provided are correct, complete or up-to-date.
wpSocket is not related to the theme or plugin, and also not responsible and expressly disclaims all liability for, damages of any kind, arising out of the use, reference to, or reliance on, any information or business listed throughout our site.