-
Notifications
You must be signed in to change notification settings - Fork 685
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update/clarify the WordPress Object Cache Pro documentation #8822
Conversation
Update + clarify the WordPress Object Cache Pro documentation to explain that certain steps of the setup can only be performed on development or multidev environments. Additionally, add a warning about the health check notice that is expected to pop up
⚡ Deployed with Pantheon Decoupled This build was successfully deployed with Pantheon. You can track the build logs here. 👀 Preview: https://pr-8822-documentation.appa.pantheon.site |
⚡ Deployed with Pantheon Decoupled This build was successfully deployed with Pantheon. You can track the build logs here. 👀 Preview: https://pr-8822-documentation.appa.pantheon.site |
@rachelwhitton can you check with @scottbuscemi on whether this change is necessary? |
⚡ Deployed with Pantheon Decoupled This build was successfully deployed with Pantheon. You can track the build logs here. 👀 Preview: https://pr-8822-documentation.appa.pantheon.site |
⚡ Deployed with Pantheon Decoupled This build was successfully deployed with Pantheon. You can track the build logs here. 👀 Preview: https://pr-8822-documentation.appa.pantheon.site |
⚡ Deployed with Pantheon Decoupled This build was successfully deployed with Pantheon. You can track the build logs here. 👀 Preview: https://pr-8822-documentation.appa.pantheon.site |
Summary
Update + clarify the WordPress Object Cache Pro documentation to explain that certain steps of the setup can only be performed on development or multidev environments.
Additionally, add a warning about the health check notice that is expected to pop up
Release:
Post Launch
Do not remove - To be completed by the docs team upon merge:
Redirect/old-path/
=>/new-path/
(if applicable)Include/exclude pages ^ respectively within docs search service provider (if applicable)