docs(wordpress): document redis-cache plugin requirement#479
Merged
Conversation
Enabling redis.enabled/createConfig only injects WP_REDIS_* config into wp-config.php; the redis-cache plugin still has to be installed and activated via wordpress.plugins for the object cache to actually turn on, and nothing warns when it's missing (see #478). Also swap the redis-cli-based troubleshooting commands for a PHP fsockopen check, since redis-cli/wp-cli aren't present in the running wordpress container.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
redis.enabled/redis.createConfig(and Valkey) only injectWP_REDIS_*config intowp-config.php— theredis-cacheplugin still needs to be installed and activated viawordpress.plugins, otherwise the object cache silently stays inactivewordpress.pluginsentry to the "Minimal example (Redis)" snippetredis-cli— not installed in the runningwordpresscontainer — with a PHPfsockopenreachability check instead, and point to the plugin's own status page for hit/miss statsFixes the confusion reported in #478, where a user followed the README's minimal example exactly but Redis never became usable because the
redis-cacheplugin was never listed.Test plan